bmottin/claude_mac
1
0
Fork 0
forked from bchanot/claude
Code Pull Requests Activity

fix(init-project): remove speculative GSD auto-bootstrap (BLK-011)

Browse Source 
STEP 12 ran `gsd init` AFTER FINISH, creating ROADMAP.md + .gsd/ in the working
tree once the merge had already integrated committed history only — so the
artifacts stranded outside the merge/PR (BLK-011, 3rd post-FINISH artifact after
memory + docs).

Resolved by REMOVAL, not by plumbing a commit: STEP 12 speculatively bootstrapped
a heavy multi-session engine (state machine / crash recovery / cost tracking /
parallel workers) that is opt-in and rarely used. Deleting the producer means the
orphan is never created — a negative diff beats building a gsd-commit helper for an
artifact nobody commits to using.

Deliberate GSD use is untouched: initializable on-demand (`/onboard add gsd`, or
`gsd init` in a terminal), still recommended by plugin-advisor, still read by
/status. init-project is now an 11-step pipeline.

Coherence sweep (the "test" for a removal): zero dangling STEP-12 refs — header
12->11-step, the STEP 10c note, and 4 USAGE.md worked-example references all updated
to on-demand init.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01C6bUdvHnajCNzgVQefZowj
This commit is contained in:
Bastien Chanot
2026-06-29 18:27:34 +02:00
co-authored by Claude Opus 4.8
parent 0f0bd7fe63
commit a131f45f00
3 changed files with 14 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/init-project/SKILL.md
+3 -16
View File
@@ -15,10 +15,10 @@ $ARGUMENTS
## PROGRESS PROTOCOL
Every STEP must announce itself with a header BEFORE its work block, so the
user always sees where they are in the 12-step pipeline:
user always sees where they are in the 11-step pipeline:
```
━━━ STEP <N>/12 — <TITLE> ━━━ (~<estimated minutes>)
━━━ STEP <N>/11 — <TITLE> ━━━ (~<estimated minutes>)
why: <one sentence — what's at risk if this step is skipped>
```
@@ -248,8 +248,7 @@ patched. Report per its rc table — rc 4 = a LOUD upstream BDR-022 anomaly, not
> **Scaffold commit owner = STEP 5f `gitflow init`** (root commit embeds scaffold + README +
> `.gitignore` socle + hook, tree clean — BLK-010 closed). This doc-sync commit lands the
> patched docs on the MVP feature branch so they reach the merge. GSD STEP 12 still creates
> ROADMAP.md post-FINISH (BLK-011) — separate.
> patched docs on the MVP feature branch so they reach the merge.
## STEP 11 — FINISH
Tests pass, build clean, no placeholders. Integrate the MVP feature into develop
@@ -258,18 +257,6 @@ Tests pass, build clean, no placeholders. Integrate the MVP feature into develop
bash "$HOME/.claude/lib/gitflow.sh" finish # feature/mvp → develop
```
## STEP 12 — GSD v2 INIT (optional)
If `multi-session` signal was detected in STEP 0 OR the project has >3 planned milestones:
Ask: "Initialize GSD v2 for multi-session management? (yes / skip)"
- `yes` →
1. First check: `command -v gsd` — if not found:
Print: "⚠️ GSD v2 not installed. Run `npm install -g gsd-pi` then re-run `/onboard add gsd` or `/ship-feature` to initialize later."
Do NOT attempt `gsd init`. Skip to RULES.
2. If `gsd` is in PATH: run `gsd init` in the project directory to create `.gsd/` and `ROADMAP.md`.
Populate ROADMAP.md with milestones from BRIEF (v1 features + any beyond-v1 items).
Print: "✅ GSD v2 initialized — run `gsd` in terminal then `/gsd auto` to work autonomously."
- `skip` → print: "GSD v2 skipped — use `/ship-feature` for individual features."
---
## RULES