[Extension]: Add PatchWarden Evidence Pack v1.0.1

[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 (optional)

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

Documentation URL (optional)

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

Changelog URL (optional)

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

Required Spec Kit Version

=0.1.0

Required Tools (optional)

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

Number of Commands

2

Number of Hooks (optional)

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.
• The released package was tested in an isolated Spec Kit project.

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 release installed as PatchWarden Evidence Pack v1.0.1 with 2 commands, 2 hooks, and enabled status. The installed manifest and command files were read back from the test project. The released manifest defines priority 20 for both optional hooks.

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-14T00:00:00Z",
    "updated_at": "2026-07-14T00:00:00Z"
  }
}

Additional Context

This fresh submission was explicitly requested by @mnriem in #3464 after the v1.0.0 catalog PR #3488 was closed as superseded by the corrected release.

The v1.0.1 source fix was merged in jiezeng2004-design/spec-kit-patchwarden#1. It removes the vague normal-workflow step, documents the exact per-command tool boundaries, and keeps implementation, lineage creation, verification, and evidence export as separate operations.

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

[github-actions]

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

[github-actions]

Pull request created: #3514

Generated by Add Community Extension from Issue Submission · 286.9 AIC · ⌖ 14.9 AIC · ⊞ 32.9K

[mnriem]

Thank you!