[Extension]: Update Product Spec Extension to v2.1.0 #5107

Update to an existing catalog entry. The product entry in extensions/catalog.community.json is at 1.0.1 (from #3200). This request moves it to 2.1.0. Please keep the existing created_at, downloads, and stars.

Extension ID

product

Extension Name

Product Spec Extension

Version

2.1.0

Description

Generates PRFAQ, Lean PRD, stakeholder summaries, and technical designs from engineering specs.

Author

d0whc3r

Repository URL

https://github.com/d0whc3r/spec-kit-product

Download URL

https://github.com/d0whc3r/spec-kit-product/releases/download/v2.1.0/product-2.1.0.zip

License

MIT

Homepage (optional)

https://d0whc3r.github.io/spec-kit-product/

Documentation URL (optional)

https://github.com/d0whc3r/spec-kit-product/wiki

Changelog URL (optional)

https://github.com/d0whc3r/spec-kit-product/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.12.17

Required Tools (optional)

None. The extension is Markdown command and template text. It adds no tool or runtime dependency beyond Spec Kit.

Number of Commands

3

Number of Hooks (optional)

4

Tags

documentation, jtbd, lean-prd, planning, prd, prfaq, product, product-management, stakeholder, technical-design

Key Features

• /speckit.product.brief: Generate product/00-info.md and product/10-spec.md together from the current feature's spec.md, then update the shared quality checklist
• /speckit.product.plan: Generate a high-level, product-oriented plan from the current feature's plan.md
• /speckit.product.design: Generate a high-level technical design document from the current feature's plan.md and spec.md, aimed at tech leads and senior developers
• Four optional hooks: after_specify and after_clarify offer the brief; after_plan offers the plan, then the design.
• Each run validates its output against a shared product/checklist.md and lists the items that need manual review.

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on: macOS with Spec Kit 1.2.3 (specify init --integration claude).

Test scenarios:

1. Installed from the download URL above with specify extension add product --from <url>. The install registered the 3 commands as Claude skills and the 4 hooks in .specify/extensions.yml.
2. Checked that the archive SHA-256 matches the sha256 value in the proposed entry: 44d51c7b8791648fca5b426692837530a233e7ea0844d73edd0de3b7b9b13c32.
3. Ran the release checks: pnpm check validates extension.yml against catalog.json (version, command count, hook count) and lints the command and template content.

Test project: the worked examples in https://github.com/d0whc3r/spec-kit-product/tree/main/examples hold real Spec Kit inputs and the four documents the commands generated from them.

Example Usage

# Install the extension from the release archive
specify extension add product --from https://github.com/d0whc3r/spec-kit-product/releases/download/v2.1.0/product-2.1.0.zip

# Generate the product brief (stakeholder summary + product spec) from spec.md
/speckit.product.brief

# Generate the product plan and the technical design from plan.md
/speckit.product.plan
/speckit.product.design

# Skills agents such as Claude Code use hyphens: /speckit-product-brief

Proposed Catalog Entry

{
  "product": {
    "name": "Product Spec Extension",
    "id": "product",
    "description": "Generates PRFAQ, Lean PRD, stakeholder summaries, and technical designs from engineering specs.",
    "author": "d0whc3r",
    "version": "2.1.0",
    "download_url": "https://github.com/d0whc3r/spec-kit-product/releases/download/v2.1.0/product-2.1.0.zip",
    "sha256": "44d51c7b8791648fca5b426692837530a233e7ea0844d73edd0de3b7b9b13c32",
    "repository": "https://github.com/d0whc3r/spec-kit-product",
    "homepage": "https://d0whc3r.github.io/spec-kit-product/",
    "documentation": "https://github.com/d0whc3r/spec-kit-product/wiki",
    "changelog": "https://github.com/d0whc3r/spec-kit-product/blob/main/CHANGELOG.md",
    "license": "MIT",
    "category": "docs",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=0.12.17"
    },
    "provides": {
      "commands": 3,
      "hooks": 4
    },
    "tags": [
      "documentation",
      "jtbd",
      "lean-prd",
      "planning",
      "prd",
      "prfaq",
      "product",
      "product-management",
      "stakeholder",
      "technical-design"
    ],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-05-26T00:00:00Z",
    "updated_at": "2026-10-24T00:00:00Z"
  }
}

Additional Context

Changes since the catalog version (1.0.1), from the changelog:

• 2.0.0 (breaking): requires.speckit_version moves from >=0.2.0 to >=0.12.17. A new optional after_plan hook offers the design command, so provides.hooks moves from 3 to 4. Commands name other Spec Kit commands through __SPECKIT_COMMAND_<NAME>__ tokens, so each agent sees its own command form.
• 2.1.0: generated documents follow answer-first structure rules, and the checklist validates them.
• Tags: the list drops the generic design, requirements, spec, spec-kit, and spec-kit-extension, and keeps 10 tags (the catalog schema allows 2 to 10).
• Checksum: the entry now carries sha256. It matches the archive at the download URL.

Documentation: https://d0whc3r.github.io/spec-kit-product/ and https://github.com/d0whc3r/spec-kit-product/wiki.