Repository navigation
v1.5.0 — Lifecycle Expansion + Hardening Pass
[1.5.0] — 2026-04-19
Minor release (additive). Expansion of the lifecycle with portfolio view,
brown-field entry, lite mode, full monorepo support, optional V-Model
integration, unit + integration test phases, and operational readiness
artifacts. Schema v3 for.forge-status.ymlis additive over v2 — no
breaking change to existing features; a lazy migration stamps
schema_version: 3on first write.
Added — 7 new commands
speckit.product-forge.portfolio— Cross-cutting portfolio view. Scans
everyfeatures/*/.forge-status.yml, produces feature table, file-conflict
matrix, dependency graph (Mermaid), and suggested merge order. Read-only.speckit.product-forge.backfill— Brown-field entry. Reverse-engineers
a feature folder from existing code: retro product-spec, plan, simplified
tasks,.forge-status.ymlwithbackfilled: true, and a gaps-report of
missing artifacts.speckit.product-forge.monitoring-setup(Phase 9.5, opt) — Produces
real NewRelic-compatible dashboard JSON, alert rules, and SLI/SLO doc
from plan NFRs and tracking-plan events. Wrapsnewrelic-dashboard-builder.speckit.product-forge.migration-plan(Phase 5.5, opt, conditional) —
Generates zero-downtime migration plan withforward.sql,rollback.sql,
validation.sql, backfill plan, and risk matrix when plan.md introduces
schema changes. Wrapsdb-migration-manager/mongodb-ops.speckit.product-forge.i18n-harvest(post-bridge, opt) — Extracts
user-facing strings from wireframes/spec, generates feature-namespaced
locale keys, stubs TODO entries in every configured locale. Wraps
i18n-workflow.speckit.product-forge.experiment-design(Phase 9B, opt) — Forces a
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.speckit.product-forge.feature-flag-cleanup— Cross-cutting stale-flag
audit. Scans everyflags/registry.yml, cross-checks codebase, produces
removal recipes for flags pastcleanup_after. Read-only; wraps
feature-flag-manager.
Added — Monorepo support (first-class)
codebase.pathsblock in project config, withworkspace_type
(pnpm | yarn | npm | turbo | nx | rush | lerna | none) driving test-
runner resolution. Legacycodebase_pathstill supported.scope.paths,scope.cross_workspace,scope.primaryon
.forge-status.yml— names which workspaces a feature touches.- Workspace-prefixed paths in
tasks.mdandtask_log[].paths(e.g.
backend:src/users.ts). - Per-workspace conflict matrix in
/portfoliowith grouped "By
workspace" section. - Affected-only test execution in implement + test-run when running
under nx / turbo / pnpm workspaces. - Cross-workspace change propagation — scope widens automatically
when a change request touches code outside the original scope;
recorded as gate condition. - Documented in runtime.md §9,
config.md Paths.
Added — V-Model integration (optional extension)
optional_extensionsblock inextension.ymldeclaring
leocamello/spec-kit-v-model
(≥0.5.0) as an opt-in dependency.feature_mode: v-modelis now a real mode, not a stub. When
selected,forge.mddetects the V-Model extension and delegates the
middle of the lifecycle (V1–V13) to its 14 commands: requirements,
acceptance, system / architecture / module design paired with system /
integration / unit test plans, trace, peer-review, test-results
ingestion, audit report.- No silent fallback: if V-Model plugin is absent, v-model mode
aborts with the install command. Regulated work must not degrade. - Domain selection via
v-model-config.yml
(iec_62304 | iso_26262 | do_178c | generic). - New docs/v-model-integration.md covers
the full phase map, detection, fallback rules, status-file additions.
Added — Testing strategy (universal)
- New docs/testing-strategy.md — universal
(framework-agnostic) pyramid, when unit vs integration vs contract vs
E2E, per-layer coverage criteria, anti-patterns, flaky-test handling,
test-data management, monorepo-aware execution. test-plan.md§5E Unit Tests (TC-UNIT-NNN) — derived from module
boundaries + behavioural acceptance criteria. Framework-agnostic.test-plan.md§5F Integration Tests (TC-INT-NNN) — beyond endpoint
contracts: service↔DB, service↔cache, event emitter↔listener,
middleware stacks, cross-workspace integration.test-run.md§4E Unit and §4F Integration — non-browser
execution with the same auto-fix loop; §4F handles testcontainers /
docker-compose / in-memory / shared-DB isolation strategies.
Added — Structural capabilities
.forge-status.ymlschema v3 — Additive over v2. New fields:
feature_mode,backfilled,v2_native, phasestarted_at/completed_at/tokens_in
/tokens_out/tool_calls/digest_path/skipped/skip_reason,task_log[]
(renamed from early-drafttasks[]to avoid collision withphases.tasks)
withsize(XS/S/M/L/XL),paths, andcommit_sha,gates[].approvals,
gates[].skip_reason,dependencies.depends_on/
depended_on_by,role_approvals.solo_mode/
required_roles_per_phase. Newstatusenum valuenot_applicablefor
out-of-mode and backfilled phases. Full spec in
docs/schema/forge-status-v3.schema.yml.
Migration rules indocs/schema/migration-v2-to-v3.md.
Optional helper scriptscripts/migrate-status-v2-to-v3.ts.- State-lock protocol —
.forge-status.yml.lockfile-based lock with
TTL-based takeover. Prevents concurrent-writer corruption between the
orchestrator and sub-skills. Documented in
docs/runtime.md §2. - Per-phase digests — Every major phase (
research,product_spec,
plan,tasks,implement,verify) now writes<phase>/digest.md.
Runtime refuses to mark a phase completed without a digest. Downstream
phases (verify-full, portfolio, retrospective) read digests first to keep
context budgets small. Template:
docs/templates/phase-digest.md. - Lite mode — New
feature_modefield selects a 5-phase map
(problem-discoveryopt →product-spec→plan→implement→verify)
for small features. Escalation to standard is append-only. Details in
docs/policy.md §4. - Skip-reason policy — Skipping an optional phase now requires a
free-text reason whenrequire_skip_reason: true(default). Reason is
persisted on both the phase and the gate entry. Enforced by all skippable
commands. Details indocs/policy.md §3. - Learning loop —
.product-forge/lessons.mdappend-only log. Written
byretrospectiveat launch close, read byresearchas a new dimension
("Prior lessons that apply") scored by tag overlap. Format in
docs/lessons-format.md. - Drift budget —
sync-verifynow categorizes drift asstructural
(always human-in-the-loop) orcosmetic(whitespace, ordering, stale
dates). Opt-insync_verify.auto_resolve.cosmeticauto-fixes whitelisted
drift only; structural drift never auto-resolves. Budget warns when
cosmetic count exceeds threshold. - Release-readiness becomes an artifact producer — Step 1D now invokes
feature-flag-managerto produceflags/registry.yml; Step 3D invokes
newrelic-dashboard-builderto producemonitoring/dashboard.json,
alerts.yml,slo.md. Graceful fallback when provider skills are missing.
Changed
commands/forge.mdrefactored. Operating rules moved to
docs/policy.md; runtime flow (config, state lock,
detection, resume, pre-flight, sync, gate audit, digest enforcement,
context budget) moved todocs/runtime.md; status
schema narrative moved todocs/schema.md. The
orchestrator file now focuses on phase delegation and the mode-
resolution entry. No behavioral change; cross-references only.config-template.yml— New keys:default_feature_mode,
require_skip_reason,sync_verify.drift_budget.{cosmetic, structural},
sync_verify.auto_resolve.cosmetic.research.mdStep 2.5 — Consults.product-forge/lessons.mdfor
matching prior lessons and surfaces them inresearch/README.md.retrospective.mdStep 5 — Drafts lesson blocks, confirms with user,
appends tolessons.md, records count inphases.retrospective.lessons_added.
Release-prep hardening
Surfaced by the plugin test plan dry-run and closed before release:
- Broken historical refs removed from
CHANGELOG.md,README.md,
anddocs/how-it-works-v2.md— pointed to archive directories that
are not in this tree. - Policy.md §3 tightened — empty skip reasons under
require_skip_reason: truenow explicitly reject the gate and
re-prompt; noskippedgate entry is written until a non-empty
reason is supplied. - Enum validation added to
commands/forge.mdMode Resolution and
docs/runtime.md §4pre-flight — invalidfeature_mode,
phases.<name>.status, orgates[].decisionvalues abort with a
clear message instead of falling through silently. tasks.mdStep 4.1 — hard structural checks for task-ID
uniqueness and monorepo workspace-prefix validation. Duplicates and
unknown workspace names now abort the phase with a pointer to the
offending line instead of propagating intotask_log[].- Test-plan self-references — smoke and Layer B criteria updated
to excludedocs/qa/plugin-test-plan.md(which legitimately names
the patterns being searched for).
Migration notes
- No action required. Existing features continue to work. First time a
v1.5.0-aware skill writes to a feature's.forge-status.yml, it stamps
schema_version: 3and may populate new optional fields as it runs. - Optional: run
scripts/migrate-status-v2-to-v3.tsonce to stamp
every feature at once. - Monorepo support (GitHub issue #1) remains unchanged in this release.
Schema v3 fields reserve room for it (dependencies,backfilled) but
the codebase-path configuration remains single-path. Tracked for a
follow-up release.