VaiYav

VaiYav/speckit-product-forge

Plugin Claude Code

Plugins by Valentin Yakovlev (VaiYav) — SpecKit Product Forge and related developer workflow tooling.

VaiYav/speckit-product-forge

Plugin Claude Code

Full product lifecycle orchestrator for SpecKit: research → product-spec → plan → tasks → implement → verify → test → release-readiness, across express/lite/standard/v-model modes with human-in-the-loop gates, cross-artifact sync-verify, a living/delta spec with a REQ→…→TEST→EVT traceability matrix, and brown-field…

VaiYav/speckit-product-forge

Instructions file

Instructions for VaiYav/speckit-product-forge, covering claude.md, what this repo is, layout, version sync rule (do not break) and command files.

VaiYav/speckit-product-forge

Command

Generates OpenAPI 3.1 spec and Postman collection from plan.md API contracts. Auto-detects existing API framework (NestJS, Express, FastAPI, etc.), validates consistency between spec and implementation, and outputs ready-to-publish docs. Use after implement: "generate API docs", "/speckit.product-forge.api-docs".

VaiYav/speckit-product-forge

Command

Brown-field entry point: reverse-engineer a Product Forge feature folder from existing code. Reads a target module/directory, synthesises retro product-spec, plan, and simplified tasks, then writes .forge-status.yml with all phases marked completed and backfilled: true. Produces a gaps-report.md listing what a modern…

VaiYav/speckit-product-forge

Command

Phase 4: Converts approved product-spec artifacts into a SpecKit-compatible spec.md, enriched with full research and product context. Then launches SpecKit in classic (plan → tasks → implement) or V-Model mode based on user choice. Use with: "bridge to speckit", "create spec", "/speckit.product-forge.bridge".

VaiYav/speckit-product-forge

Command

Cross-cutting scope change management. When requirements change mid-lifecycle, captures the change formally, analyzes impact across all artifacts, estimates effort delta, and propagates approved changes. Runs sync-verify after application. Use: "change request", "scope change", "add requirement"…

VaiYav/speckit-product-forge

Command

Phase 6B: Structured multi-agent code review after implementation, before verification. Checks code quality (SOLID, DRY), security (OWASP surface scan), pattern consistency (vs codebase-analysis.md), and test coverage (vs spec.md requirements). Enriched with Product Forge context — not a generic code review. Use…

VaiYav/speckit-product-forge

Command

Phase 2 helper: discover the project's EXISTING design system (component library, design tokens, Storybook, Tailwind/CSS config) and emit a read-only manifest that grounds mockups, component decomposition, and verification in real code. The design system stays in code as the single source of truth; this command…

VaiYav/speckit-product-forge

Command

Optional Phase 9B: design a rigorous A/B experiment plan before shipping a feature behind a flag. Produces hypothesis, primary/secondary/guardrail metrics, minimum detectable effect, sample size calculation, exposure rules, and pre-registered decision thresholds. Wraps the installed feature-flag-ab-testing skill (or…

VaiYav/speckit-product-forge

Command

Cross-cutting stale-flag audit. Scans every flags/registry.yml produced by release-readiness across all features, cross-checks against the actual codebase, and produces a cleanup plan for flags whose cleanupafter date has passed. Wraps the installed feature-flag-manager skill. Safe to run on any schedule; read-only by…

VaiYav/speckit-product-forge

Command

Full lifecycle orchestrator for Product Forge v1.6.0. Drives a feature from idea to shipped, measured code through the phase map selected by featuremode (express / lite / standard / v-model) with human-in-the-loop gates, cross-artifact sync-verify between transitions, and a complete gate audit trail. Standard phases…

VaiYav/speckit-product-forge

Command

Optional post-bridge step: extract every user-facing string from wireframes, product-spec, and (if available) UI prototypes, generate locale key stubs namespaced by the feature slug, and create TODO entries in every configured locale file. Wraps the project's i18n-workflow skill where available. Runs at Phase 4.5 …

VaiYav/speckit-product-forge

Command

Phase 6: Execute implementation from tasks.md with progressive verification. Delegates to SpecKit implement, monitors task completion, runs mini-verify every N tasks, surfaces product-spec context to implementation agents. Standalone — run after pre-impl-review (or after any custom step inserted before coding). Use…

VaiYav/speckit-product-forge

Command

Optional pre-implement phase: when plan.md introduces data-model changes, generate a zero-downtime migration plan with forward + rollback scripts, validation queries, backfill job outline, and risk matrix. Wraps the installed db-migration-manager and mongodb-ops skills. Runs at Phase 5.5 — after Phase 5B (Tasks) and…

VaiYav/speckit-product-forge

Command

Phase 9.5 (optional): produce real monitoring artifacts for a feature — a dashboard, alert rules, and SLI/SLO definitions derived from plan NFRs and tracking-plan events. Targets the configured backend (telemetry.dashboards: PostHog / Sentry; NewRelic optional via the newrelic-dashboard-builder skill). When the…

VaiYav/speckit-product-forge

Command

Phase 5: Generate technical plan from spec.md with cross-validation against product-spec. Ensures plan covers all Must Have user stories and aligns with codebase analysis. Standalone — run independently, before tasks or implement. Use: "create plan", "technical plan", "/speckit.product-forge.plan".

VaiYav/speckit-product-forge

Command

Cross-cutting portfolio view over every feature managed by Product Forge. Reads every feature's .forge-status.yml (via the Path-Resolution Contract's enumerate(), so flat and domain-nested layouts both work) plus optional tasks.md, and produces a consolidated report covering feature status, file/module conflicts…

VaiYav/speckit-product-forge

Command

Phase 5C: Combined design review, architecture review, and risk assessment gate before writing any code. Loads wireframes, UX patterns, plan architecture, and codebase analysis to produce a structured review with risk register. Optional for features with <=5 tasks and no UI. Use: "pre-impl review", "review before…

VaiYav/speckit-product-forge

Command

Phase 0: Validates the problem before any research begins. Runs JTBD analysis, generates an interview script, builds a Problem Statement Canvas, and outputs a scored confidence report. Prevents investing in features that solve the wrong problem. Use before research: "discover the problem"…

VaiYav/speckit-product-forge

Command

Phase 2: Interactive product specification creation. Asks detailed questions about desired level of detail and document decomposition. Creates product-spec.md, structured journeys (journeys/journeys.yml as the E2E source of truth), wireframes, metrics.md, and design-system-grounded clickable mockups with a component…

VaiYav/speckit-product-forge

Command

Phase 9: Pre-ship readiness checklist. Covers feature flags, rollout strategy, rollback plan, documentation, monitoring, analytics, and deployment dependencies. Consolidates api-docs, tracking-plan, and security-check status into one gate. Optional for internal/backend-only features. Use: "release readiness", "ready…

VaiYav/speckit-product-forge

Command

Phase 1: Adaptive multi-dimensional feature research. Assesses input richness and auto-adjusts interview depth — minimal input triggers full 7-question interview, rich input skips to confirmation. Mandatory: competitors, UX/UI, codebase. Optional: tech stack, metrics/ROI. Saves to features/ /research/. Use with…

VaiYav/speckit-product-forge

Command

Post-launch retrospective comparing predicted metrics from research/metrics-roi.md against real data pulled from connected MCPs (PostHog / Amplitude product analytics, Sentry error tracking, NewRelic APM) or manual input. Closes the loop on the full product lifecycle. Run 2+ weeks after shipping. Use: "retrospective"…