bigpowers 2.29.0 → 2.31.0

package/.pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.29.0",
+  "version": "2.31.0",
   "description": "70 skills — 61 agent skills for spec-driven, test-first software development by solo developers",
   "keywords": [
     "pi-package"

package/.pi/prompts/migrate-spec.md

@@ -93,6 +93,31 @@ in_scope:
 
 See [REFERENCE.md — in_scope format with ID tracking](./REFERENCE.md#in_scope-format-with-id-tracking) for examples.
 
+#### Traceability Output (FR-XX, UJ-XX)
+
+When source has FR-XX or UJ-XX IDs, emit `specs/product/REQUIREMENTS_TRACE.yaml` for end-to-end requirement traceability:
+
+```yaml
+trace:
+  - id: FR-001
+    type: functional_requirement
+    description: "User can register with email/password"
+    epic: e02-auth-ui
+    story: e02s01
+    verify: "grep -q 'FR-001' specs/product/SCOPE_LATEST.yaml && echo OK"
+  - id: UJ-001
+    type: user_journey
+    description: "New user completes registration flow"
+    epic: e02-auth-ui
+    story: e02s01
+```
+
+**Existing trace file:** If `REQUIREMENTS_TRACE.yaml` already exists, prompt: "REQUIREMENTS_TRACE.yaml exists. [overwrite / merge / skip]"
+
+**No FR-XX/UJ-XX found:** Skip trace file; add note to state.yaml handoff: "No FR-XX/UJ-XX IDs found — traceability file skipped".
+
+See [REFERENCE.md — REQUIREMENTS_TRACE.yaml format](./REFERENCE.md#requirements_traceyaml-format) for the complete schema.
+
 > **HARD GATE** — Never overwrite an existing `specs/` file without explicit user confirmation. Merge into it if it exists; don't clobber.
 >
 > → verify: `git diff --name-only HEAD -- specs/ 2>/dev/null | head -20`
@@ -101,19 +126,38 @@ See [REFERENCE.md — in_scope format with ID tracking](./REFERENCE.md#in_scope-
 
 ### Step 4 — Generate state.yaml
 
-Always regenerate `specs/state.yaml` from scratch in bigpowers format (see REFERENCE.md for template):
+Always regenerate `specs/state.yaml` from scratch in bigpowers YAML format (see REFERENCE.md for template). The **handoff block is mandatory** and must include all four fields:
 
-```markdown
-# Session State: <project name>
-## Current Milestone
-Migrated from <framework> on <date>. Next: review generated specs and run plan-work.
-## Pending Releases
-- [ ] Review migrated specs
-- [ ] Run elaborate-spec to validate scope
-- [ ] Run plan-work to produce first release plan
+```yaml
+active_flow: null
+active_epic_id: null
+active_story_id: null
+
+# ... other state fields ...
+
+handoff:
+  last_step_completed: "Migrated from <framework> on <date>"
+  open_decisions:
+    - "decision text here"
+  required_reading:
+    - specs/product/VISION_LATEST.yaml
+    - specs/product/SCOPE_LATEST.yaml
+    - specs/tech-architecture/TECH_STACK_LATEST.md
+    - specs/release-plan.yaml
+  next_skill: survey-context
 ```
 
-→ verify: `[ -f specs/state.yaml ] && echo "ok" || echo "MISSING: specs/state.yaml not created"`
+If no open decisions were found during migration, the `open_decisions` list may be empty with an explanatory comment:
+
+```yaml
+handoff:
+  last_step_completed: "..."
+  open_decisions: []  # None — all decisions resolved during migration
+  required_reading: [...]
+  next_skill: survey-context
+```
+
+→ verify: `grep -q 'handoff:' specs/state.yaml && grep -q 'last_step_completed' specs/state.yaml && echo "ok" || echo "MISSING or INCOMPLETE: handoff block"`
 
 ### Step 5 — Surface learnings (optional)
 
@@ -425,7 +469,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 ### From GSD
 
 - [ ] **`specs/tech-architecture/METHODOLOGY_LATEST.md`** — Standing analytical lenses. Agents read before planning.
-- [ ] **`handoff` block in state.yaml** — Last skill, last step, required reading for next session.
+- [x] **`handoff` block in state.yaml** — Last skill, last step, required reading for next session. (adopted: mandatory in Step 4 output)
 - [x] **ID tracking in SCOPE_LATEST.yaml** — FR/UJ IDs for spec → plan → verification traceability. (adopted in Step 3 transform)
 
 ### From spec-kit
@@ -436,7 +480,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 
 ### From BMAD
 
-- [ ] **FR-XX + UJ-XX in SCOPE_LATEST.yaml** — Rigorous traceability.
+- [x] **FR-XX + UJ-XX in SCOPE_LATEST.yaml** — Rigorous traceability. (adopted: REQUIREMENTS_TRACE.yaml emitted on migration)
 - [ ] **`specs/DECISION-LOG.md`** — Lightweight decisions below ADR threshold.
 - [ ] **Adversarial review pass** — Critique epic shard before `develop-tdd`.
 
@@ -497,29 +541,86 @@ in_scope:
 
 **When source has mixed IDs:** Entries with source IDs get `id:` fields; entries without IDs receive auto-generated IDs. A comment block at the top of `in_scope` documents which IDs were auto-generated.
 
-### `specs/state.yaml` template format
-
-Generated during Step 4 of migration. Regenerate from scratch in bigpowers format:
-
-```markdown
-# Session State: <project name>
+### REQUIREMENTS_TRACE.yaml format
 
-## Current Milestone
+Emitted when source has FR-XX (functional requirement) or UJ-XX (user journey) IDs. Maps source requirements to bigpowers epic/story structure and verification commands:
 
-Migrated from <framework> on <date>. Next: review generated specs and run plan-work.
+```yaml
+trace:
+  # Functional Requirements
+  - id: FR-001
+    type: functional_requirement
+    description: "User can register with email/password"
+    source_artifact: "prd.md"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'FR-001' specs/product/SCOPE_LATEST.yaml && echo OK"
+
+  # User Journeys
+  - id: UJ-001
+    type: user_journey
+    description: "New user completes registration flow"
+    source_artifact: "epic-auth-ui.md"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'UJ-001' specs/epics/e02-auth-ui/epic.yaml && echo OK"
+
+metadata:
+  source_framework: "BMAD"
+  migrated_at: "2026-06-26T12:00:00Z"
+  total_requirements: 2
+  coverage: "All FR-XX and UJ-XX IDs from source mapped"
+```
 
-## Git Metadata
+**When source has no FR-XX/UJ-XX:** Skip REQUIREMENTS_TRACE.yaml. Add note to `state.yaml` handoff: "No FR-XX/UJ-XX IDs found — traceability file skipped".
 
-- **Branch**: <current branch>
-- **Hash**: <git rev-parse HEAD>
+**Existing trace file:** If REQUIREMENTS_TRACE.yaml exists, prompt user: "Overwrite? [yes / merge / skip]". Merge appends new entries; skip leaves existing file intact.
 
-## Completed Releases
+### `specs/state.yaml` template format
 
-(none — migration starting point)
+Generated during Step 4 of migration. Regenerate from scratch in bigpowers YAML format. The **handoff block is mandatory**:
 
-## Pending Releases
+```yaml
+active_flow: null
+active_epic_id: null
+active_story_id: null
+completed_epic: false
+
+epic_cycle:
+  current_step: null
+  next_skill: null
+  story_bcps: null
+  completed_steps: []
+  audit_result: null
+
+bug_cycle:
+  current_step: null
+  completed_steps: []
+
+release:
+  target_version: null
+  last_tag: null
+  last_publish: null
+  ci_verified: false
+
+metrics:
+  story_start: null
+  story_end: null
+  cycle_minutes: null
+  bcp_per_hour: null
+
+git:
+  branch: <current branch>
+  hash: <git rev-parse HEAD>
+  pushed: false
 
-- [ ] Review migrated specs
-- [ ] Run elaborate-spec to validate scope
-- [ ] Run plan-work to produce first release plan
+handoff:
+  last_step_completed: "Migrated from <framework> on <date>"
+  open_decisions: []  # Empty if all decisions resolved during migration
+  required_reading:
+    - specs/product/VISION_LATEST.yaml
+    - specs/product/SCOPE_LATEST.yaml
+    - specs/tech-architecture/TECH_STACK_LATEST.md
+    - specs/release-plan.yaml
+  next_skill: survey-context
 ```

package/.pi/skills/migrate-spec/SKILL.md

@@ -95,6 +95,31 @@ in_scope:
 
 See [REFERENCE.md — in_scope format with ID tracking](./REFERENCE.md#in_scope-format-with-id-tracking) for examples.
 
+#### Traceability Output (FR-XX, UJ-XX)
+
+When source has FR-XX or UJ-XX IDs, emit `specs/product/REQUIREMENTS_TRACE.yaml` for end-to-end requirement traceability:
+
+```yaml
+trace:
+  - id: FR-001
+    type: functional_requirement
+    description: "User can register with email/password"
+    epic: e02-auth-ui
+    story: e02s01
+    verify: "grep -q 'FR-001' specs/product/SCOPE_LATEST.yaml && echo OK"
+  - id: UJ-001
+    type: user_journey
+    description: "New user completes registration flow"
+    epic: e02-auth-ui
+    story: e02s01
+```
+
+**Existing trace file:** If `REQUIREMENTS_TRACE.yaml` already exists, prompt: "REQUIREMENTS_TRACE.yaml exists. [overwrite / merge / skip]"
+
+**No FR-XX/UJ-XX found:** Skip trace file; add note to state.yaml handoff: "No FR-XX/UJ-XX IDs found — traceability file skipped".
+
+See [REFERENCE.md — REQUIREMENTS_TRACE.yaml format](./REFERENCE.md#requirements_traceyaml-format) for the complete schema.
+
 > **HARD GATE** — Never overwrite an existing `specs/` file without explicit user confirmation. Merge into it if it exists; don't clobber.
 >
 > → verify: `git diff --name-only HEAD -- specs/ 2>/dev/null | head -20`
@@ -103,19 +128,38 @@ See [REFERENCE.md — in_scope format with ID tracking](./REFERENCE.md#in_scope-
 
 ### Step 4 — Generate state.yaml
 
-Always regenerate `specs/state.yaml` from scratch in bigpowers format (see REFERENCE.md for template):
+Always regenerate `specs/state.yaml` from scratch in bigpowers YAML format (see REFERENCE.md for template). The **handoff block is mandatory** and must include all four fields:
 
-```markdown
-# Session State: <project name>
-## Current Milestone
-Migrated from <framework> on <date>. Next: review generated specs and run plan-work.
-## Pending Releases
-- [ ] Review migrated specs
-- [ ] Run elaborate-spec to validate scope
-- [ ] Run plan-work to produce first release plan
+```yaml
+active_flow: null
+active_epic_id: null
+active_story_id: null
+
+# ... other state fields ...
+
+handoff:
+  last_step_completed: "Migrated from <framework> on <date>"
+  open_decisions:
+    - "decision text here"
+  required_reading:
+    - specs/product/VISION_LATEST.yaml
+    - specs/product/SCOPE_LATEST.yaml
+    - specs/tech-architecture/TECH_STACK_LATEST.md
+    - specs/release-plan.yaml
+  next_skill: survey-context
 ```
 
-→ verify: `[ -f specs/state.yaml ] && echo "ok" || echo "MISSING: specs/state.yaml not created"`
+If no open decisions were found during migration, the `open_decisions` list may be empty with an explanatory comment:
+
+```yaml
+handoff:
+  last_step_completed: "..."
+  open_decisions: []  # None — all decisions resolved during migration
+  required_reading: [...]
+  next_skill: survey-context
+```
+
+→ verify: `grep -q 'handoff:' specs/state.yaml && grep -q 'last_step_completed' specs/state.yaml && echo "ok" || echo "MISSING or INCOMPLETE: handoff block"`
 
 ### Step 5 — Surface learnings (optional)
 
@@ -427,7 +471,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 ### From GSD
 
 - [ ] **`specs/tech-architecture/METHODOLOGY_LATEST.md`** — Standing analytical lenses. Agents read before planning.
-- [ ] **`handoff` block in state.yaml** — Last skill, last step, required reading for next session.
+- [x] **`handoff` block in state.yaml** — Last skill, last step, required reading for next session. (adopted: mandatory in Step 4 output)
 - [x] **ID tracking in SCOPE_LATEST.yaml** — FR/UJ IDs for spec → plan → verification traceability. (adopted in Step 3 transform)
 
 ### From spec-kit
@@ -438,7 +482,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 
 ### From BMAD
 
-- [ ] **FR-XX + UJ-XX in SCOPE_LATEST.yaml** — Rigorous traceability.
+- [x] **FR-XX + UJ-XX in SCOPE_LATEST.yaml** — Rigorous traceability. (adopted: REQUIREMENTS_TRACE.yaml emitted on migration)
 - [ ] **`specs/DECISION-LOG.md`** — Lightweight decisions below ADR threshold.
 - [ ] **Adversarial review pass** — Critique epic shard before `develop-tdd`.
 
@@ -499,29 +543,86 @@ in_scope:
 
 **When source has mixed IDs:** Entries with source IDs get `id:` fields; entries without IDs receive auto-generated IDs. A comment block at the top of `in_scope` documents which IDs were auto-generated.
 
-### `specs/state.yaml` template format
-
-Generated during Step 4 of migration. Regenerate from scratch in bigpowers format:
-
-```markdown
-# Session State: <project name>
+### REQUIREMENTS_TRACE.yaml format
 
-## Current Milestone
+Emitted when source has FR-XX (functional requirement) or UJ-XX (user journey) IDs. Maps source requirements to bigpowers epic/story structure and verification commands:
 
-Migrated from <framework> on <date>. Next: review generated specs and run plan-work.
+```yaml
+trace:
+  # Functional Requirements
+  - id: FR-001
+    type: functional_requirement
+    description: "User can register with email/password"
+    source_artifact: "prd.md"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'FR-001' specs/product/SCOPE_LATEST.yaml && echo OK"
+
+  # User Journeys
+  - id: UJ-001
+    type: user_journey
+    description: "New user completes registration flow"
+    source_artifact: "epic-auth-ui.md"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'UJ-001' specs/epics/e02-auth-ui/epic.yaml && echo OK"
+
+metadata:
+  source_framework: "BMAD"
+  migrated_at: "2026-06-26T12:00:00Z"
+  total_requirements: 2
+  coverage: "All FR-XX and UJ-XX IDs from source mapped"
+```
 
-## Git Metadata
+**When source has no FR-XX/UJ-XX:** Skip REQUIREMENTS_TRACE.yaml. Add note to `state.yaml` handoff: "No FR-XX/UJ-XX IDs found — traceability file skipped".
 
-- **Branch**: <current branch>
-- **Hash**: <git rev-parse HEAD>
+**Existing trace file:** If REQUIREMENTS_TRACE.yaml exists, prompt user: "Overwrite? [yes / merge / skip]". Merge appends new entries; skip leaves existing file intact.
 
-## Completed Releases
+### `specs/state.yaml` template format
 
-(none — migration starting point)
+Generated during Step 4 of migration. Regenerate from scratch in bigpowers YAML format. The **handoff block is mandatory**:
 
-## Pending Releases
+```yaml
+active_flow: null
+active_epic_id: null
+active_story_id: null
+completed_epic: false
+
+epic_cycle:
+  current_step: null
+  next_skill: null
+  story_bcps: null
+  completed_steps: []
+  audit_result: null
+
+bug_cycle:
+  current_step: null
+  completed_steps: []
+
+release:
+  target_version: null
+  last_tag: null
+  last_publish: null
+  ci_verified: false
+
+metrics:
+  story_start: null
+  story_end: null
+  cycle_minutes: null
+  bcp_per_hour: null
+
+git:
+  branch: <current branch>
+  hash: <git rev-parse HEAD>
+  pushed: false
 
-- [ ] Review migrated specs
-- [ ] Run elaborate-spec to validate scope
-- [ ] Run plan-work to produce first release plan
+handoff:
+  last_step_completed: "Migrated from <framework> on <date>"
+  open_decisions: []  # Empty if all decisions resolved during migration
+  required_reading:
+    - specs/product/VISION_LATEST.yaml
+    - specs/product/SCOPE_LATEST.yaml
+    - specs/tech-architecture/TECH_STACK_LATEST.md
+    - specs/release-plan.yaml
+  next_skill: survey-context
 ```

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+# [2.31.0](https://github.com/danielvm-git/bigpowers/compare/v2.30.0...v2.31.0) (2026-06-26)
+
+
+### Features
+
+* **migrate-spec:** make handoff block mandatory in Step 4 output ([1f05663](https://github.com/danielvm-git/bigpowers/commit/1f0566320356d8de4d3c2775ddebc3b17cf27fe6))
+
+# [2.30.0](https://github.com/danielvm-git/bigpowers/compare/v2.29.0...v2.30.0) (2026-06-26)
+
+
+### Features
+
+* **migrate-spec:** emit REQUIREMENTS_TRACE.yaml for FR-XX/UJ-XX IDs ([955a1fd](https://github.com/danielvm-git/bigpowers/commit/955a1fd37b898ec70a86895d8772f0ec6fb8a0fa))
+
 # [2.29.0](https://github.com/danielvm-git/bigpowers/compare/v2.28.0...v2.29.0) (2026-06-26)
 
 

package/COMMIT-MESSAGE.md

@@ -0,0 +1,34 @@
+# Proposed Commit Message
+
+## Type and Scope
+`feat(migrate-spec)` — Minor version bump
+
+## Title
+```
+feat(migrate-spec): make handoff block mandatory in Step 4 output
+```
+
+## Body
+```
+The handoff block (last_step_completed, open_decisions, required_reading,
+next_skill) is now a mandatory part of state.yaml generation, not optional.
+
+During real migrations, the handoff block proved immediately useful — the next
+agent reads it first to understand context, decisions, and required reading.
+Promoting it from optional to mandatory ensures every migration output includes
+this metadata.
+
+Changes:
+- SKILL.md Step 4: updated to mandate handoff block with YAML format example
+- REFERENCE.md: added complete state.yaml YAML template with handoff structure
+- Learnings table: marked handoff as adopted (from GSD learning set)
+```
+
+## Release Impact
+- **Bump Type:** `minor` (X.Y.z)
+- **Rationale:** New mandatory output structure in migrate-spec skill
+
+## Notes
+- Documentation-only change (no code changes)
+- All verify commands pass
+- Audit gate: PASS (10/10 items)

package/SKILL-INDEX.md

@@ -3,7 +3,7 @@
 > **DO NOT EDIT** — This file is auto-generated by `scripts/generate-skill-index.sh`.
 > Edit `SKILL.md` source files or `skills-lock.json` instead. Run `bash scripts/sync-skills.sh` to regenerate.
 
-**Generated:** 2026-06-26T22:20:53Z
+**Generated:** 2026-06-26T22:57:50Z
 **Skills:** 70
 
 ---

package/migrate-spec/REFERENCE.md

@@ -133,7 +133,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 ### From GSD
 
 - [ ] **`specs/tech-architecture/METHODOLOGY_LATEST.md`** — Standing analytical lenses. Agents read before planning.
-- [ ] **`handoff` block in state.yaml** — Last skill, last step, required reading for next session.
+- [x] **`handoff` block in state.yaml** — Last skill, last step, required reading for next session. (adopted: mandatory in Step 4 output)
 - [x] **ID tracking in SCOPE_LATEST.yaml** — FR/UJ IDs for spec → plan → verification traceability. (adopted in Step 3 transform)
 
 ### From spec-kit
@@ -144,7 +144,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 
 ### From BMAD
 
-- [ ] **FR-XX + UJ-XX in SCOPE_LATEST.yaml** — Rigorous traceability.
+- [x] **FR-XX + UJ-XX in SCOPE_LATEST.yaml** — Rigorous traceability. (adopted: REQUIREMENTS_TRACE.yaml emitted on migration)
 - [ ] **`specs/DECISION-LOG.md`** — Lightweight decisions below ADR threshold.
 - [ ] **Adversarial review pass** — Critique epic shard before `develop-tdd`.
 
@@ -205,29 +205,86 @@ in_scope:
 
 **When source has mixed IDs:** Entries with source IDs get `id:` fields; entries without IDs receive auto-generated IDs. A comment block at the top of `in_scope` documents which IDs were auto-generated.
 
-### `specs/state.yaml` template format
-
-Generated during Step 4 of migration. Regenerate from scratch in bigpowers format:
-
-```markdown
-# Session State: <project name>
-
-## Current Milestone
+### REQUIREMENTS_TRACE.yaml format
 
-Migrated from <framework> on <date>. Next: review generated specs and run plan-work.
+Emitted when source has FR-XX (functional requirement) or UJ-XX (user journey) IDs. Maps source requirements to bigpowers epic/story structure and verification commands:
 
-## Git Metadata
+```yaml
+trace:
+  # Functional Requirements
+  - id: FR-001
+    type: functional_requirement
+    description: "User can register with email/password"
+    source_artifact: "prd.md"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'FR-001' specs/product/SCOPE_LATEST.yaml && echo OK"
+
+  # User Journeys
+  - id: UJ-001
+    type: user_journey
+    description: "New user completes registration flow"
+    source_artifact: "epic-auth-ui.md"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'UJ-001' specs/epics/e02-auth-ui/epic.yaml && echo OK"
+
+metadata:
+  source_framework: "BMAD"
+  migrated_at: "2026-06-26T12:00:00Z"
+  total_requirements: 2
+  coverage: "All FR-XX and UJ-XX IDs from source mapped"
+```
 
-- **Branch**: <current branch>
-- **Hash**: <git rev-parse HEAD>
+**When source has no FR-XX/UJ-XX:** Skip REQUIREMENTS_TRACE.yaml. Add note to `state.yaml` handoff: "No FR-XX/UJ-XX IDs found — traceability file skipped".
 
-## Completed Releases
+**Existing trace file:** If REQUIREMENTS_TRACE.yaml exists, prompt user: "Overwrite? [yes / merge / skip]". Merge appends new entries; skip leaves existing file intact.
 
-(none — migration starting point)
+### `specs/state.yaml` template format
 
-## Pending Releases
+Generated during Step 4 of migration. Regenerate from scratch in bigpowers YAML format. The **handoff block is mandatory**:
 
-- [ ] Review migrated specs
-- [ ] Run elaborate-spec to validate scope
-- [ ] Run plan-work to produce first release plan
+```yaml
+active_flow: null
+active_epic_id: null
+active_story_id: null
+completed_epic: false
+
+epic_cycle:
+  current_step: null
+  next_skill: null
+  story_bcps: null
+  completed_steps: []
+  audit_result: null
+
+bug_cycle:
+  current_step: null
+  completed_steps: []
+
+release:
+  target_version: null
+  last_tag: null
+  last_publish: null
+  ci_verified: false
+
+metrics:
+  story_start: null
+  story_end: null
+  cycle_minutes: null
+  bcp_per_hour: null
+
+git:
+  branch: <current branch>
+  hash: <git rev-parse HEAD>
+  pushed: false
+
+handoff:
+  last_step_completed: "Migrated from <framework> on <date>"
+  open_decisions: []  # Empty if all decisions resolved during migration
+  required_reading:
+    - specs/product/VISION_LATEST.yaml
+    - specs/product/SCOPE_LATEST.yaml
+    - specs/tech-architecture/TECH_STACK_LATEST.md
+    - specs/release-plan.yaml
+  next_skill: survey-context
 ```

package/migrate-spec/SKILL.md

@@ -96,6 +96,31 @@ in_scope:
 
 See [REFERENCE.md — in_scope format with ID tracking](./REFERENCE.md#in_scope-format-with-id-tracking) for examples.
 
+#### Traceability Output (FR-XX, UJ-XX)
+
+When source has FR-XX or UJ-XX IDs, emit `specs/product/REQUIREMENTS_TRACE.yaml` for end-to-end requirement traceability:
+
+```yaml
+trace:
+  - id: FR-001
+    type: functional_requirement
+    description: "User can register with email/password"
+    epic: e02-auth-ui
+    story: e02s01
+    verify: "grep -q 'FR-001' specs/product/SCOPE_LATEST.yaml && echo OK"
+  - id: UJ-001
+    type: user_journey
+    description: "New user completes registration flow"
+    epic: e02-auth-ui
+    story: e02s01
+```
+
+**Existing trace file:** If `REQUIREMENTS_TRACE.yaml` already exists, prompt: "REQUIREMENTS_TRACE.yaml exists. [overwrite / merge / skip]"
+
+**No FR-XX/UJ-XX found:** Skip trace file; add note to state.yaml handoff: "No FR-XX/UJ-XX IDs found — traceability file skipped".
+
+See [REFERENCE.md — REQUIREMENTS_TRACE.yaml format](./REFERENCE.md#requirements_traceyaml-format) for the complete schema.
+
 > **HARD GATE** — Never overwrite an existing `specs/` file without explicit user confirmation. Merge into it if it exists; don't clobber.
 >
 > → verify: `git diff --name-only HEAD -- specs/ 2>/dev/null | head -20`
@@ -104,19 +129,38 @@ See [REFERENCE.md — in_scope format with ID tracking](./REFERENCE.md#in_scope-
 
 ### Step 4 — Generate state.yaml
 
-Always regenerate `specs/state.yaml` from scratch in bigpowers format (see REFERENCE.md for template):
+Always regenerate `specs/state.yaml` from scratch in bigpowers YAML format (see REFERENCE.md for template). The **handoff block is mandatory** and must include all four fields:
 
-```markdown
-# Session State: <project name>
-## Current Milestone
-Migrated from <framework> on <date>. Next: review generated specs and run plan-work.
-## Pending Releases
-- [ ] Review migrated specs
-- [ ] Run elaborate-spec to validate scope
-- [ ] Run plan-work to produce first release plan
+```yaml
+active_flow: null
+active_epic_id: null
+active_story_id: null
+
+# ... other state fields ...
+
+handoff:
+  last_step_completed: "Migrated from <framework> on <date>"
+  open_decisions:
+    - "decision text here"
+  required_reading:
+    - specs/product/VISION_LATEST.yaml
+    - specs/product/SCOPE_LATEST.yaml
+    - specs/tech-architecture/TECH_STACK_LATEST.md
+    - specs/release-plan.yaml
+  next_skill: survey-context
+```
+
+If no open decisions were found during migration, the `open_decisions` list may be empty with an explanatory comment:
+
+```yaml
+handoff:
+  last_step_completed: "..."
+  open_decisions: []  # None — all decisions resolved during migration
+  required_reading: [...]
+  next_skill: survey-context
 ```
 
-→ verify: `[ -f specs/state.yaml ] && echo "ok" || echo "MISSING: specs/state.yaml not created"`
+→ verify: `grep -q 'handoff:' specs/state.yaml && grep -q 'last_step_completed' specs/state.yaml && echo "ok" || echo "MISSING or INCOMPLETE: handoff block"`
 
 ### Step 5 — Surface learnings (optional)
 

package/migrate-spec/templates/REQUIREMENTS_TRACE.yaml

@@ -0,0 +1,28 @@
+# Auto-generated from {{source_framework}} FR-XX / UJ-XX IDs during migration
+# Maps source requirements to bigpowers epic/story structure and verification commands.
+
+trace:
+  # Functional Requirements (FR-XX)
+  - id: FR-001
+    type: functional_requirement
+    description: "User can register with email/password"
+    source_artifact: "{{source_file}}"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'FR-001' specs/product/SCOPE_LATEST.yaml && echo OK || echo FAIL"
+
+  # User Journeys (UJ-XX)
+  - id: UJ-001
+    type: user_journey
+    description: "New user completes registration flow"
+    source_artifact: "{{source_file}}"
+    epic: "e02-auth-ui"
+    story: "e02s01"
+    verify: "grep -q 'UJ-001' specs/epics/e02-auth-ui/epic.yaml && echo OK || echo FAIL"
+
+# Metadata
+metadata:
+  source_framework: "{{source_framework}}"  # e.g., BMAD, GSD, spec-kit
+  migrated_at: "{{timestamp}}"
+  total_requirements: "{{count}}"
+  coverage: "All FR-XX and UJ-XX IDs from source mapped to bigpowers artifacts"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.29.0",
+  "version": "2.31.0",
   "description": "61 agent skills for spec-driven, test-first software development by solo developers",
   "main": "index.js",
   "scripts": {

package/skills-lock.json

@@ -163,7 +163,7 @@
     },
     "migrate-spec": {
       "description": "Detect GSD, spec-kit, or BMAD spec artifacts and transform them into bigpowers YAML layout (state.yaml, release-plan.yaml, epics/, requirements/, plans/, ADRs). Use when migrating foreign spec docs.",
-      "sha256": "3570ec13243de9b8",
+      "sha256": "897baa6f0f37ea68",
       "path": "migrate-spec/SKILL.md"
     },
     "model-domain": {