Skip to content

[Extension]: Add PatchWarden Evidence Pack #3464

Description

@jiezeng2004-design

Extension ID

patchwarden-evidence

Extension Name

PatchWarden Evidence Pack

Version

1.0.0

Description

Optional Spec Kit hooks and agent commands that prepare a PatchWarden lineage 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.0.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 prepares a PatchWarden lineage linked to the current Spec Kit scope.
  • Optional after_implement hook guides bounded Evidence Pack export for an accepted lineage.
  • Manual commands are available for prepare and export workflows.
  • 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 release download URL.
  • All command files validate and register without error. The two commands are declarative agent instructions with no shell helpers; their PatchWarden MCP calls require an already configured MCP connection.
  • Documentation is complete and accurate.
  • No security vulnerabilities identified: the extension has no executable dependencies and documents strict bounded-evidence and no-secret rules.
  • Tested on a real PatchWarden project checkout.

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.0.
  • 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.12.dev0, installed in an isolated 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.0.zip

The CLI installed PatchWarden Evidence Pack (v1.0.0) successfully and reported 2 commands, 2 hooks, and enabled status.

Real-project install: repeated the same release-archive installation in a fresh clone of jiezeng2004-design/PatchWarden; the installed manifest reports version 1.0.0 and enabled: true.

The commands intentionally contain no shell scripts. At runtime they require the user to have configured the PatchWarden MCP server and then use only get_task_lineage and export_task_evidence_pack for bounded evidence export.

Example Usage

specify extension add patchwarden-evidence --from https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.0.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": "Create bounded, traceable PatchWarden evidence packs for Spec Kit implementations.",
    "author": "Zengjie",
    "version": "1.0.0",
    "download_url": "https://github.com/jiezeng2004-design/spec-kit-patchwarden/archive/refs/tags/v1.0.0.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": "testing",
    "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-11T00:00:00Z",
    "updated_at": "2026-07-11T00:00:00Z"
  }
}

Additional Context

This is the requested follow-up to closed PR #3442. Maintainer @mnriem advised packaging the evidence-pack supervisor as a community extension, cutting a release, confirming specify extension add works, and then filing this Extension Submission. The extension is independently maintained; it does not claim to be a first-party Spec Kit feature.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions