v1.2.1 — plan / tasks / implement split into independent commands

Breaking change: implement split into 3 standalone commands

speckit.product-forge.implement was a monolith that bundled plan + tasks + implementation into one command. Starting from v1.2.1 it is split into three independent, standalone commands:

Command	Phase	Does
/speckit.product-forge.plan	5	Generates plan.md from spec.md, cross-validates vs product-spec, exits after approval
/speckit.product-forge.tasks	5B	Generates tasks.md from plan.md, validates all story/FR coverage, exits after approval
/speckit.product-forge.implement	6	Executes implementation from tasks.md only, exits when all tasks are [x]

Why this matters for community extensions

Each boundary between these commands is now an explicit extension point. You can insert your own commands between any two phases:

/speckit.product-forge.plan
    ↓  ← insert: architecture-review, cost-estimation, ADR creation, ...
/speckit.product-forge.tasks
    ↓  ← insert: sprint-planning, capacity-check, stakeholder-approval, ...
/speckit.product-forge.implement
    ↓  ← insert: pr-creation, code-review-gate, manual-qa, ...
/speckit.product-forge.verify-full

The forge orchestrator (forge.md) respects .forge-status.yml — it always resumes from the last completed phase, so custom steps just need to update the status file before handing back.

Migration

If you call speckit.product-forge.implement directly and expect it to run plan + tasks too:

# Before (v1.2.0)
/speckit.product-forge.implement

# After (v1.2.1)
/speckit.product-forge.plan
/speckit.product-forge.tasks
/speckit.product-forge.implement

Or just use /speckit.product-forge.forge — the orchestrator handles the full sequence automatically.

Install / Update

specify extension add product-forge --from https://github.com/VaiYav/speckit-product-forge/archive/refs/tags/v1.2.1.zip

Full changelog

See CHANGELOG.md