extension.yml

schema_version: "1.0"

extension:
  id: "product-forge"
  name: "Product Forge"
  version: "1.7.0"
  description: "Full product lifecycle orchestrator with research, spec, plan, implement, verify, test, and release-readiness phases. v1.7 adds normative --dry-run preview, cross-model code review, intra-phase parallel implementation, a constitution↔code drift layer (10-layer sync-verify), lessons→skills promotion, status --cost token rollups, and a phase-map single-source. Builds on v1.6 express mode, design-system-harvest, structured journeys → Playwright E2E, a living/delta spec with spec-merge and a REQ→…→TEST→EVT traceability matrix, FE↔BE contract-first OpenAPI/AsyncAPI, telemetry MCP wiring (PostHog/Sentry/Amplitude), a two-layer risk-scored gate review, and a WCAG-AA accessibility gate. See README for the complete feature list."
  author: "Valentin Yakovlev"
  repository: "https://github.com/VaiYav/speckit-product-forge"
  license: "MIT"
  homepage: "https://github.com/VaiYav/speckit-product-forge"

requires:
  speckit_version: ">=0.1.0"

# Optional extensions. These are NOT hard dependencies — the plugin works
# without them. Each entry tells the user which sibling extension unlocks
# which feature set, how to install it, and when Product Forge expects it.
#
# At runtime, commands that need an optional extension first detect its
# presence (by checking for one of its commands). If missing, they either
# (a) fall back gracefully with an advisory message or (b) instruct the
# user to install it when the feature is mandatory.
optional_extensions:
  - id: "v-model"
    name: "V-Model Extension Pack"
    version: ">=0.5.0"
    repository: "https://github.com/leocamello/spec-kit-v-model"
    install: |
      specify extension add v-model \
        --from https://github.com/leocamello/spec-kit-v-model/archive/refs/tags/v0.5.0.zip
    purpose: >
      Enables `feature_mode: v-model`. Provides the formal V-Model
      artifact progression (IEEE 29148 requirements, IEEE 1016 system
      design, IEEE 42010 / Kruchten 4+1 architecture, DO-178C / ISO 26262
      module design) plus ISO 29119 test plans at every level and a
      regulatory-grade traceability matrix. Required for regulated
      domains (medical IEC 62304, automotive ISO 26262, avionics DO-178C).
    detection_command: "speckit.v-model.requirements"
    triggered_by: "feature_mode: v-model"
    fallback: >
      When the plugin is not installed and the user selects v-model mode,
      Product Forge aborts with the install command above. It does NOT
      silently fall back to standard mode — safety-critical work must not
      proceed without the formal artifacts.

provides:
  commands:
    - name: "speckit.product-forge.forge"
      file: "commands/forge.md"
      description: "Full lifecycle orchestrator: research → product-spec → revalidation → SpecKit → pre-impl-review → implement → code-review → verify → test → release-readiness"

    - name: "speckit.product-forge.research"
      file: "commands/research.md"
      description: "Phase 1: Parallel multi-dimensional feature research (competitors, UX, codebase, tech, metrics)"

    - name: "speckit.product-forge.product-spec"
      file: "commands/product-spec.md"
      description: "Phase 2: Interactive product specification with configurable detail levels and auto-decomposition"

    - name: "speckit.product-forge.design-system-harvest"
      file: "commands/design-system-harvest.md"
      description: "Phase 2 helper: harvest a read-only manifest of the project's in-code design system (components, tokens, Storybook) to ground mockups, component decomposition, and UI verification"

    - name: "speckit.product-forge.revalidate"
      file: "commands/revalidate.md"
      description: "Phase 3: Iterative revalidation and correction cycle until user approval"

    - name: "speckit.product-forge.bridge"
      file: "commands/bridge.md"
      description: "Phase 4: Convert product-spec artifacts to SpecKit spec.md and launch planning"

    - name: "speckit.product-forge.plan"
      file: "commands/plan.md"
      description: "Phase 5: Generate technical plan from spec.md with cross-validation against product-spec. Standalone command — exits after plan approval"

    - name: "speckit.product-forge.tasks"
      file: "commands/tasks.md"
      description: "Phase 5B: Generate task breakdown from plan.md with cross-validation against product-spec. Standalone command — exits after tasks approval"

    - name: "speckit.product-forge.implement"
      file: "commands/implement.md"
      description: "Phase 6: Execute implementation from tasks.md. Standalone — run after tasks or after any custom step inserted before coding"

    - name: "speckit.product-forge.verify-full"
      file: "commands/verify-full.md"
      description: "Phase 7: Full traceability verification: code ↔ tasks ↔ plan ↔ spec ↔ product-spec ↔ research"

    - name: "speckit.product-forge.test-plan"
      file: "commands/test-plan.md"
      description: "Phase 8A: Auto-detect test setup, generate test cases and Playwright specs from user stories"

    - name: "speckit.product-forge.test-run"
      file: "commands/test-run.md"
      description: "Phase 8B: Execute tests, track bugs in BUG-NNN.md, auto-fix P0/P1, loop until exit criteria met"

    - name: "speckit.product-forge.status"
      file: "commands/status.md"
      description: "Show current feature lifecycle status across all phases and recommend next action"

    - name: "speckit.product-forge.problem-discovery"
      file: "commands/problem-discovery.md"
      description: "Phase 0: Validate the problem before research. JTBD analysis, interview script, Problem Statement Canvas, Go/No-go decision"

    - name: "speckit.product-forge.api-docs"
      file: "commands/api-docs.md"
      description: "Generate OpenAPI 3.1 spec and Postman collection from plan.md API contracts. Consistency check vs implementation"

    - name: "speckit.product-forge.security-check"
      file: "commands/security-check.md"
      description: "Feature-specific OWASP security audit. Scans only relevant attack surfaces detected from plan.md (auth, input, payments, files)"

    - name: "speckit.product-forge.tracking-plan"
      file: "commands/tracking-plan.md"
      description: "Generate analytics tracking plan from user journeys: event taxonomy, property schemas, funnel definitions, SDK code snippets"

    - name: "speckit.product-forge.pre-impl-review"
      file: "commands/pre-impl-review.md"
      description: "Phase 5C: Combined design review, architecture review, and risk assessment before implementation"

    - name: "speckit.product-forge.code-review"
      file: "commands/code-review.md"
      description: "Phase 6B: Multi-agent code review — quality, security, patterns, test coverage — enriched with Product Forge context"

    - name: "speckit.product-forge.release-readiness"
      file: "commands/release-readiness.md"
      description: "Phase 9: Pre-ship readiness checklist — feature flags, rollout, documentation, monitoring, analytics, dependencies"

    - name: "speckit.product-forge.sync-verify"
      file: "commands/sync-verify.md"
      description: "Cross-cutting: 9-layer artifact consistency checker (incl. FE↔BE contract drift + doc↔code). Detects forward and backward drift across all lifecycle artifacts"

    - name: "speckit.product-forge.change-request"
      file: "commands/change-request.md"
      description: "Cross-cutting: Formal scope change management with impact analysis, effort delta, and artifact propagation"

    - name: "speckit.product-forge.spec-merge"
      file: "commands/spec-merge.md"
      description: "Cross-cutting (living spec): merge a feature's delta specs (ADDED/MODIFIED/REMOVED) into canonical specs/ and archive the change with audit history (spec-anchored source of truth)"

    - name: "speckit.product-forge.portfolio"
      file: "commands/portfolio.md"
      description: "Cross-cutting: Portfolio view across all features. Feature table, file-conflict matrix, dependency graph, suggested merge order. Read-only scan."

    - name: "speckit.product-forge.backfill"
      file: "commands/backfill.md"
      description: "Brown-field entry: reverse-engineers a Product Forge feature folder from existing code. Generates retro product-spec, plan, tasks, status file with backfilled: true, and a gaps-report of missing artifacts."

    - name: "speckit.product-forge.monitoring-setup"
      file: "commands/monitoring-setup.md"
      description: "Phase 9.5 (opt): builds real monitoring artifacts for the configured backend (PostHog/Sentry MCP; NewRelic optional) — dashboards, alerts.yml, SLO doc — from plan NFRs and tracking-plan."

    - name: "speckit.product-forge.migration-plan"
      file: "commands/migration-plan.md"
      description: "Phase 5.5 (opt, conditional): zero-downtime migration plan with forward.sql, rollback.sql, validation.sql, backfill plan, and risk matrix when plan.md introduces schema changes. Wraps db-migration-manager / mongodb-ops."

    - name: "speckit.product-forge.i18n-harvest"
      file: "commands/i18n-harvest.md"
      description: "Opt-in post-bridge step: extracts user-facing strings from wireframes/spec, generates namespaced locale keys, and stubs TODO entries in every configured locale. Wraps i18n-workflow."

    - name: "speckit.product-forge.experiment-design"
      file: "commands/experiment-design.md"
      description: "Phase 9B (opt): pre-registered A/B plan — hypothesis, MDE, sample size, exposure rules, guardrails, decision rule — before shipping a flag-gated feature. Wraps feature-flag-ab-testing."

    - name: "speckit.product-forge.feature-flag-cleanup"
      file: "commands/feature-flag-cleanup.md"
      description: "Cross-cutting stale-flag audit. Scans every flags/registry.yml, cross-checks codebase, produces removal recipes for flags past cleanup_after. Read-only; wraps feature-flag-manager."

    - name: "speckit.product-forge.retrospective"
      file: "commands/retrospective.md"
      description: "Post-launch retrospective: predicted vs actual metrics, data from connected analytics/error MCPs (PostHog/Amplitude, Sentry; NewRelic optional), research accuracy audit, lessons learned appended to .product-forge/lessons.md"

tags:
  - "process"
  - "research"
  - "product-spec"
  - "lifecycle"
  - "testing"
  - "analytics"
  - "security"
  - "api-docs"
  - "jtbd"
  - "sync-verify"
  - "code-review"
  - "release-readiness"
  - "change-management"
  - "portfolio"
  - "backfill"
  - "lite-mode"
  - "monitoring"
  - "migration"
  - "i18n"
  - "experiment"
  - "flag-cleanup"
  - "learning-loop"
  - "state-lock"
  - "digest"
  - "drift-budget"
  - "monorepo"
  - "v-model-integration"
  - "design-system"
  - "structured-journeys"
  - "playwright-e2e"
  - "interaction-convention"
  - "living-spec"
  - "delta-specs"
  - "traceability-matrix"
  - "unit-testing"
  - "integration-testing"
  - "testing-strategy"
  - "workspace-aware"
  - "optional-extensions"

# Project configuration
#
# The authoritative config reference lives in config-template.yml and
# docs/config.md — they document every key (project context, features_dir,
# flow_mode, e2e_runner, default_feature_mode, default_speckit_mode,
# require_skip_reason / require_code_review / require_testing /
# require_pre_impl_review, progressive_verify_interval, telemetry, …).
#
# To configure a project: copy config-template.yml to
# .product-forge/config.yml in your project root and edit it there.
config:
  reference: "config-template.yml"
  docs: "docs/config.md"