Skip to content

[Extension]: Add Product Forge #2967

@VaiYav

Description

@VaiYav

Submitted via gh against the Extension Submission template. This is a new extension (first catalog entry), not an update.

Extension ID

product-forge

Extension Name

Product Forge

Version

1.7.0

Description

Full product-lifecycle orchestrator for Spec Kit: research → product-spec → plan → tasks → implement → verify → test → release-readiness, across express/lite/standard/v-model modes with human-in-the-loop gates.

Author

Valentin Yakovlev

Repository URL

https://github.com/VaiYav/speckit-product-forge

Download URL

https://github.com/VaiYav/speckit-product-forge/archive/refs/tags/v1.7.0.zip

License

MIT

Homepage (optional)

https://github.com/VaiYav/speckit-product-forge

Documentation URL (optional)

https://github.com/VaiYav/speckit-product-forge/blob/main/docs/concept.md

Changelog URL (optional)

https://github.com/VaiYav/speckit-product-forge/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.1.0

Required Tools (optional)

  • node (>=22) — required, for the zero-dependency helper scripts (doctor, lint-docs, traceability/gate-risk/cost validators)
  • @axe-core/playwright — optional, only for the WCAG-AA accessibility gate (Phases 8A/8B)

Number of Commands

31

Number of Hooks (optional)

0

Tags

process, lifecycle, testing, sync-verify, release-readiness

Key Features

  • End-to-end lifecycle orchestrator (/speckit.product-forge.forge) spanning research → product-spec → plan → tasks → implement → verify → test → release-readiness, with a human gate at every phase transition.
  • Four feature modes — express / lite / standard / v-model — with a deterministic phase-execution map (single-sourced in docs/schema/phase-map.yml).
  • 10-layer sync-verify cross-artifact drift check (incl. FE↔BE contract drift, doc↔code, and a standing constitution↔code layer) plus an 11-layer verify-full final gate.
  • Living/delta spec with spec-merge into a canonical specs/ source of truth and a REQ→US→JRN→component→API→TEST→EVT traceability matrix.
  • Contract-first OpenAPI/AsyncAPI, structured journeys → Playwright E2E, risk-scored two-layer gate review (with optional cross-model review), and telemetry MCP wiring.
  • --dry-run preview (writes nothing real), --ci headless gating via a declarative gate-policy, status --cost token/tool-call rollups, and a learning loop that promotes recurring lessons to reusable skills.
  • Zero-dependency Node verification suite (doctor aggregates every script self-test + a doc-consistency linter) — the repo's own CI gate.

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 26.5.1, Node 22.

Release verification (v1.7.0):

  1. Tagged v1.7.0 and published a GitHub release.
  2. Downloaded the published archive at the Download URL above (HTTP 200) and confirmed it carries extension.version: "1.7.0" and .claude-plugin/plugin.json "version": "1.7.0" (the version-sync invariant).
  3. node scripts/doctor.js → 15 checks green (wraps every --selftest + the doc-consistency linter + a known-good fixture smoke + release-blocking invariants).
  4. claude plugin validate . → passed (the repo also ships as a Claude Code plugin from the same payload).

Self-tests: lib-paths 13, gate-risk 10, validate-traceability 23, lint-docs 23, check-links 7, cost-report 8 — all passing (84 assertions).

Example Usage

# Install as a Spec Kit extension
specify extension add product-forge --from https://github.com/VaiYav/speckit-product-forge/archive/refs/tags/v1.7.0.zip

# Run the full lifecycle (interactive, gated)
/speckit.product-forge.forge add a referral rewards page

# Or drive a single phase
/speckit.product-forge.research add a referral rewards page
/speckit.product-forge.sync-verify referral-rewards

Proposed Catalog Entry

{
  "product-forge": {
    "name": "Product Forge",
    "id": "product-forge",
    "description": "Full product-lifecycle orchestrator for Spec Kit: research → product-spec → plan → tasks → implement → verify → test → release-readiness, across express/lite/standard/v-model modes with human-in-the-loop gates.",
    "author": "Valentin Yakovlev",
    "version": "1.7.0",
    "download_url": "https://github.com/VaiYav/speckit-product-forge/archive/refs/tags/v1.7.0.zip",
    "repository": "https://github.com/VaiYav/speckit-product-forge",
    "homepage": "https://github.com/VaiYav/speckit-product-forge",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.1.0"
    },
    "provides": {
      "commands": 31
    },
    "tags": ["process", "lifecycle", "testing", "sync-verify", "release-readiness"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-06-13T00:00:00Z",
    "updated_at": "2026-06-13T00:00:00Z"
  }
}

Additional Context

Product Forge ships from one repo in two installable forms from the same payload (commands/, docs/, scripts/): a Spec Kit extension (extension.yml) and a Claude Code plugin (.claude-plugin/). It is a content/spec extension — 31 command prompt-skills + normative docs + zero-dependency Node helpers — with no runtime service. The CHANGELOG documents the full version history (current: v1.7.0 "Ivysaur").

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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