[Extension]: Add PatchWarden Evidence Pack

[jiezeng2004-design]

Extension ID

patchwarden-evidence

Extension Name

PatchWarden Evidence Pack

Version

1.0.1

Description

Optional Spec Kit hooks and agent commands that map approved Spec Kit tasks into a guarded PatchWarden Goal and export a bounded, traceable Evidence Pack for an accepted implementation.

Author

Zengjie

Repository URL

https://github.com/jiezeng2004-design/spec-kit-patchwarden

Download URL

https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.1.zip

License

MIT

Homepage

https://github.com/jiezeng2004-design/spec-kit-patchwarden

Documentation URL

https://github.com/jiezeng2004-design/spec-kit-patchwarden/blob/main/README.md

Changelog URL

https://github.com/jiezeng2004-design/spec-kit-patchwarden/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools

• PatchWarden (>=1.5.1) - required as an already configured MCP server for the target workspace.

Number of Commands

2

Number of Hooks

2

Tags

verification, evidence, traceability, security

Key Features

• Optional before_implement hook creates a guarded PatchWarden Goal and imports approved Spec Kit tasks as subgoals.
• The prepare command is limited to create_goal and import_speckit_tasks; it does not execute implementation work or create a lineage.
• Optional after_implement hook exports bounded evidence for an accepted lineage.
• The export command is limited to get_task_lineage and export_task_evidence_pack.
• Safety boundaries prohibit secret retrieval, raw logs, full diffs, publishing, pushing, tagging, merging, deployment, and out-of-workspace actions.

Testing Checklist

• Extension installs successfully via the v1.0.1 release download URL.
• All command files validate and register without error.
• Documentation describes the exact per-command MCP tool scope.
• No executable dependencies or shell helpers are included.
• No security vulnerabilities identified in the declarative extension package.

Submission Requirements

• Valid extension.yml manifest included.
• README.md with installation and usage instructions.
• MIT LICENSE file included.
• GitHub release created with tag v1.0.1.
• All command files exist and are properly formatted.
• Extension ID follows the lowercase-with-hyphens convention.

Testing Details

Spec Kit CLI: upstream specify-cli 0.12.15.dev0, installed in an isolated Python virtual environment from the current github/spec-kit source.

Release install:

specify extension add patchwarden-evidence --from https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.1.zip

The CLI installed PatchWarden Evidence Pack (v1.0.1) successfully and reported 2 commands, 2 hooks, priority 10, and enabled status. The installed manifest and command files were read back from the test project.

Runtime scope:

• Prepare: create_goal and import_speckit_tasks only. This creates bounded Goal/Subgoal metadata and does not start tasks, create a lineage, or claim verification.
• Export: get_task_lineage and export_task_evidence_pack only. This checks accepted bounded lineage state and writes the local Evidence Pack.
• The extension contains declarative Markdown commands and no executable scripts or package dependencies.

Example Usage

specify extension add patchwarden-evidence --from https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.1.zip
/speckit.patchwarden-evidence.prepare-evidence
/speckit.patchwarden-evidence.export-evidence <lineage_id>

Proposed Catalog Entry

{
  "patchwarden-evidence": {
    "name": "PatchWarden Evidence Pack",
    "id": "patchwarden-evidence",
    "description": "Map Spec Kit tasks into a guarded PatchWarden Goal and export bounded, traceable evidence for an accepted lineage.",
    "author": "Zengjie",
    "version": "1.0.1",
    "download_url": "https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.1.zip",
    "repository": "https://github.com/jiezeng2004-design/spec-kit-patchwarden",
    "homepage": "https://github.com/jiezeng2004-design/spec-kit-patchwarden",
    "documentation": "https://github.com/jiezeng2004-design/spec-kit-patchwarden/blob/main/README.md",
    "changelog": "https://github.com/jiezeng2004-design/spec-kit-patchwarden/blob/main/CHANGELOG.md",
    "license": "MIT",
    "category": "process",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=0.1.0",
      "tools": [{"name": "patchwarden", "version": ">=1.5.1", "required": true}]
    },
    "provides": {"commands": 2, "hooks": 2},
    "tags": ["verification", "evidence", "traceability", "security"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-07-13T00:00:00Z",
    "updated_at": "2026-07-14T00:00:00Z"
  }
}

Additional Context

This is the requested follow-up to closed PR #3442. The v1.0.1 release resolves the runtime-scope inconsistency identified in the review of PR #3488. The extension is independently maintained and does not claim to be a first-party Spec Kit feature.

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Pull request created: #3488

Generated by Add Community Extension from Issue Submission · 297.2 AIC · ⌖ 15 AIC · ⊞ 32.9K

[mnriem]

@jiezeng2004-design Can you please tell me the context of #3488 (review) and how we can resolve this? Thanks!

[jiezeng2004-design]

@mnriem Thank you for flagging this. The review is correct: the v1.0.0 submission text incorrectly said that both commands used only get_task_lineage and export_task_evidence_pack, while prepare-evidence.md also called import_speckit_tasks and referred to an unspecified normal PatchWarden workflow.

I resolved the mismatch in a new v1.0.1 release rather than changing the old tag:

• Prepare is now explicitly limited to create_goal and import_speckit_tasks. It creates bounded Goal/Subgoal metadata only and does not execute implementation work, create a lineage, or claim verification.
• Export remains limited to get_task_lineage and export_task_evidence_pack.
• The vague normal-workflow step was removed.
• README, manifest, changelog, release version, and this submission were updated together.

Source fix: jiezeng2004-design/spec-kit-patchwarden#1

Release: https://github.com/jiezeng2004-design/spec-kit-patchwarden/releases/tag/v1.0.1

Download URL: https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.1.zip

I also tested the release ZIP with the current upstream specify-cli 0.12.15.dev0 in an isolated environment. It installs as PatchWarden Evidence Pack v1.0.1 with 2 commands, 2 hooks, and enabled status, and the installed command files reflect the scoped tool boundaries above.

For PR #3488, the catalog entry should be updated from v1.0.0 to v1.0.1, use the v1.0.1 download URL, and use the revised description from this issue. I cannot push to the workflow-owned upstream branch, so a maintainer or the catalog automation will need to apply that small catalog update. I have not resolved the review thread.

Posted on behalf of @jiezeng2004-design by OpenAI Codex (GPT-5, autonomous).

[mnriem]

Can you file a new Extension submission for the update? Thanks!

[jiezeng2004-design]

Filed the fresh v1.0.1 Extension submission as requested: #3512. It includes the corrected per-command PatchWarden tool scope, the v1.0.1 release/download URLs, updated testing details, and links back to #3464 and closed PR #3488. It is ready for the extension-submission label and catalog triage. Thank you!