bigpowers 2.32.0 → 2.33.0

package/.pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.32.0",
+  "version": "2.33.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

@@ -204,6 +204,36 @@ If skip is chosen, add to handoff: "Adversarial review: skipped — review manua
 
 → verify: `test -f specs/archive/MIGRATION-AUDIT.md && echo "audit completed" || echo "audit skipped or not performed"`
 
+### Step 7 — Post-migration: Optional two-pass spec writing gate
+
+After Steps 1–6, offer the user an optional two-pass spec writing workflow (spec-kit learning):
+
+Prompt: "Use two-pass spec writing (user journeys first, then technical)? [yes / no]"
+
+If **yes**, initialize the gate in `specs/state.yaml`:
+
+```yaml
+two_pass_spec:
+  journey_pass: pending
+  technical_pass: pending
+  approved_at: null
+```
+
+The journey pass must be marked "complete" by the user (after stakeholder approval of user-journey specs) before the technical pass begins:
+
+```yaml
+two_pass_spec:
+  journey_pass: complete
+  approved_at: "2026-06-26T12:00:00Z"
+  technical_pass: pending
+```
+
+Inform the user: "Journey pass is pending. Run `elaborate-spec` for user journeys, get stakeholder approval, then update `two_pass_spec.journey_pass: complete` in state.yaml before proceeding to technical specs."
+
+If **no**, skip the two-pass gate. Proceed directly to plan-work.
+
+→ verify: `grep -q 'two_pass_spec:' specs/state.yaml && echo "two-pass gate initialized" || echo "two-pass gate not activated"`
+
 
 ## Artifact Mapping Summary
 
@@ -511,7 +541,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 
 ### From spec-kit
 
-- [ ] **Two-pass spec writing** — User-journey pass first, then technical-decisions pass.
+- [x] **Two-pass spec writing** — User-journey pass first, then technical-decisions pass. (adopted: optional post-migration gate)
 - [ ] **Explicit inter-phase gate** — "Approve to proceed?" at end of `elaborate-spec`.
 - [ ] **Epic task isolation** — Each task completable in isolation; `depends-on` explicit in epic YAML.
 
@@ -699,4 +729,9 @@ handoff:
     - specs/tech-architecture/TECH_STACK_LATEST.md
     - specs/release-plan.yaml
   next_skill: survey-context
+
+two_pass_spec:  # Optional: only if user activates two-pass spec writing gate
+  journey_pass: pending
+  technical_pass: pending
+  approved_at: null
 ```

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

@@ -206,6 +206,36 @@ If skip is chosen, add to handoff: "Adversarial review: skipped — review manua
 
 → verify: `test -f specs/archive/MIGRATION-AUDIT.md && echo "audit completed" || echo "audit skipped or not performed"`
 
+### Step 7 — Post-migration: Optional two-pass spec writing gate
+
+After Steps 1–6, offer the user an optional two-pass spec writing workflow (spec-kit learning):
+
+Prompt: "Use two-pass spec writing (user journeys first, then technical)? [yes / no]"
+
+If **yes**, initialize the gate in `specs/state.yaml`:
+
+```yaml
+two_pass_spec:
+  journey_pass: pending
+  technical_pass: pending
+  approved_at: null
+```
+
+The journey pass must be marked "complete" by the user (after stakeholder approval of user-journey specs) before the technical pass begins:
+
+```yaml
+two_pass_spec:
+  journey_pass: complete
+  approved_at: "2026-06-26T12:00:00Z"
+  technical_pass: pending
+```
+
+Inform the user: "Journey pass is pending. Run `elaborate-spec` for user journeys, get stakeholder approval, then update `two_pass_spec.journey_pass: complete` in state.yaml before proceeding to technical specs."
+
+If **no**, skip the two-pass gate. Proceed directly to plan-work.
+
+→ verify: `grep -q 'two_pass_spec:' specs/state.yaml && echo "two-pass gate initialized" || echo "two-pass gate not activated"`
+
 
 ## Artifact Mapping Summary
 
@@ -513,7 +543,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 
 ### From spec-kit
 
-- [ ] **Two-pass spec writing** — User-journey pass first, then technical-decisions pass.
+- [x] **Two-pass spec writing** — User-journey pass first, then technical-decisions pass. (adopted: optional post-migration gate)
 - [ ] **Explicit inter-phase gate** — "Approve to proceed?" at end of `elaborate-spec`.
 - [ ] **Epic task isolation** — Each task completable in isolation; `depends-on` explicit in epic YAML.
 
@@ -701,4 +731,9 @@ handoff:
     - specs/tech-architecture/TECH_STACK_LATEST.md
     - specs/release-plan.yaml
   next_skill: survey-context
+
+two_pass_spec:  # Optional: only if user activates two-pass spec writing gate
+  journey_pass: pending
+  technical_pass: pending
+  approved_at: null
 ```

package/CHANGELOG.md

@@ -1,3 +1,10 @@
+# [2.33.0](https://github.com/danielvm-git/bigpowers/compare/v2.32.0...v2.33.0) (2026-06-26)
+
+
+### Features
+
+* **migrate-spec:** add two-pass spec writing gate ([6d33173](https://github.com/danielvm-git/bigpowers/commit/6d331735554df2d29adab6fdf5ef72844821f5bd))
+
 # [2.32.0](https://github.com/danielvm-git/bigpowers/compare/v2.31.0...v2.32.0) (2026-06-26)
 
 

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:59:59Z
+**Generated:** 2026-06-26T23:02:01Z
 **Skills:** 70
 
 ---

package/migrate-spec/REFERENCE.md

@@ -138,7 +138,7 @@ Optional enhancements to offer the user after migration. Present as checkboxes.
 
 ### From spec-kit
 
-- [ ] **Two-pass spec writing** — User-journey pass first, then technical-decisions pass.
+- [x] **Two-pass spec writing** — User-journey pass first, then technical-decisions pass. (adopted: optional post-migration gate)
 - [ ] **Explicit inter-phase gate** — "Approve to proceed?" at end of `elaborate-spec`.
 - [ ] **Epic task isolation** — Each task completable in isolation; `depends-on` explicit in epic YAML.
 
@@ -326,4 +326,9 @@ handoff:
     - specs/tech-architecture/TECH_STACK_LATEST.md
     - specs/release-plan.yaml
   next_skill: survey-context
+
+two_pass_spec:  # Optional: only if user activates two-pass spec writing gate
+  journey_pass: pending
+  technical_pass: pending
+  approved_at: null
 ```

package/migrate-spec/SKILL.md

@@ -207,6 +207,36 @@ If skip is chosen, add to handoff: "Adversarial review: skipped — review manua
 
 → verify: `test -f specs/archive/MIGRATION-AUDIT.md && echo "audit completed" || echo "audit skipped or not performed"`
 
+### Step 7 — Post-migration: Optional two-pass spec writing gate
+
+After Steps 1–6, offer the user an optional two-pass spec writing workflow (spec-kit learning):
+
+Prompt: "Use two-pass spec writing (user journeys first, then technical)? [yes / no]"
+
+If **yes**, initialize the gate in `specs/state.yaml`:
+
+```yaml
+two_pass_spec:
+  journey_pass: pending
+  technical_pass: pending
+  approved_at: null
+```
+
+The journey pass must be marked "complete" by the user (after stakeholder approval of user-journey specs) before the technical pass begins:
+
+```yaml
+two_pass_spec:
+  journey_pass: complete
+  approved_at: "2026-06-26T12:00:00Z"
+  technical_pass: pending
+```
+
+Inform the user: "Journey pass is pending. Run `elaborate-spec` for user journeys, get stakeholder approval, then update `two_pass_spec.journey_pass: complete` in state.yaml before proceeding to technical specs."
+
+If **no**, skip the two-pass gate. Proceed directly to plan-work.
+
+→ verify: `grep -q 'two_pass_spec:' specs/state.yaml && echo "two-pass gate initialized" || echo "two-pass gate not activated"`
+
 ---
 
 ## Artifact Mapping Summary

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.32.0",
+  "version": "2.33.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": "353a127597cead4d",
+      "sha256": "93c8cd03a33b7c10",
       "path": "migrate-spec/SKILL.md"
     },
     "model-domain": {