Skip to content

v1.2.0 — 5 new commands: Problem Discovery, API Docs, Security Check, Tracking Plan, Retrospective

Choose a tag to compare

View all tags
@VaiYav VaiYav released this 30 Mar 19:07
· 34 commits to main since this release
v1.2.0
ee373ea

What's new in v1.2.0

Product Forge now covers the full product lifecycle — from validating the problem exists, to measuring real impact after launch. 5 new commands added.

/speckit.product-forge.problem-discovery — Phase 0 (new)

Validate the problem before committing to research:

  • JTBD analysis (functional / emotional / social job layers)
  • Competing Forces model — Push + Pull vs Inertia + Anxiety
  • Problem Statement Canvas → problem-discovery/problem-statement.md
  • User interview script with scoring rubric
  • Go / Investigate further / No-go decision
  • Outputs hypotheses H1–HN that focus Phase 1 research agents

/speckit.product-forge.api-docs — post-implement (new)

Generate production-ready API documentation from plan.md contracts:

  • OpenAPI 3.1 openapi.yml — import into Swagger UI, Redoc, Stoplight
  • postman-collection.json — with auto-token-save login flow
  • Consistency check: plan.md vs actual implementation drift report
  • Auto-detects framework (NestJS / Express / FastAPI) and auth scheme

/speckit.product-forge.security-check — post-implement (new)

Feature-scoped OWASP audit — checks only what this feature actually does:

  • Builds threat model from plan.md (auth, input, payments, files, webhooks)
  • Covers OWASP A01–A08 for detected surfaces only
  • Scans for hardcoded secrets, missing ownership checks, mass assignment, missing rate limiting
  • Findings: Critical / High / Medium / Low with code evidence + fix patterns
  • Ship-readiness verdict: ✅ Ready / ⚠️ Fix critical first / 🔴 Not ready

/speckit.product-forge.tracking-plan — post-spec (new)

Analytics tracking plan generated directly from user journeys:

  • Auto-detects SDK (Mixpanel, Amplitude, PostHog, Firebase, Segment)
  • Event taxonomy with property schemas, required/optional flags, examples
  • Conversion funnels + abandonment funnels mapped to success metrics
  • Ready-to-paste typed SDK snippets for the detected framework
  • Coverage matrix: each user story → key event → success metric

/speckit.product-forge.retrospective — post-launch (new)

Close the loop — run ≥14 days after shipping:

  • Loads predicted KPIs from research/metrics-roi.md
  • Queries NewRelic (via MCP) for real performance data since launch
  • Predicted vs actual: adoption, completion rate, latency, error rate
  • Research accuracy audit: were Phase 1 predictions correct?
  • Lessons learned for the next feature

Full lifecycle: 15 commands

Phase 0   problem-discovery   → validate the problem (JTBD, Go/No-go)
Phase 1   research            → competitors, UX, codebase, tech, metrics
Phase 2   product-spec        → user journeys, wireframes, mockups
Phase 3   revalidate          → approval loop
Phase 4   bridge              → spec.md (Classic or V-Model)
Phase 5-6 implement           → plan + tasks + code
Phase 7   verify-full         → traceability audit
Phase 8A  test-plan           → test cases + .spec.ts files
Phase 8B  test-run            → playwright-cli execution + bug fix loop
Post-impl api-docs            → OpenAPI 3.1 + Postman collection
Post-impl security-check      → OWASP audit scoped to this feature
Post-spec tracking-plan       → analytics events + SDK snippets
Post-ship retrospective       → predicted vs actual metrics
Any time  status              → lifecycle progress view

Install / Update

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

Full changelog

See CHANGELOG.md

Assets 2
Loading