golem15/msd-core
4
0
Fork 0
Code Issues 1 Pull Requests Actions 2 Packages Projects Releases Wiki Activity

feat(workflow): scan planted seeds during new-milestone step 2.5 (#2177)

Browse Source 
Closes #2169

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Tibsfox
2026-04-12 14:56:00 -07:00
committed by GitHub
parent 990b87abd4
commit b2febdec2f
2 changed files with 112 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
get-shit-done/workflows/new-milestone.md
View File

@@ -46,6 +46,55 @@ If the flag is absent, keep the current behavior of continuing phase numbering f
- Wait for their response, then use AskUserQuestion to probe specifics
- If user selects "Other" at any point to provide freeform input, ask follow-up as plain text — not another AskUserQuestion
## 2.5. Scan Planted Seeds
Check `.planning/seeds/` for seed files that match the milestone goals gathered in step 2.
```bash
ls .planning/seeds/SEED-*.md 2>/dev/null
```
**If no seed files exist:** Skip this step silently — do not print any message or prompt.
**If seed files exist:** Read each `SEED-*.md` file and extract from its frontmatter and body:
- **Idea** — the seed title (heading after frontmatter, e.g. `# SEED-001: <idea>`)
- **Trigger conditions** — the `trigger_when` frontmatter field and the "When to Surface" section's bullet list
- **Planted during** — the `planted_during` frontmatter field (for context)
Compare each seed's trigger conditions against the milestone goals from step 2. A seed matches when its trigger conditions are relevant to any of the milestone's target features or goals.
**If no seeds match:** Skip silently — do not prompt the user.
**If matching seeds found:**
**`--auto` mode:** Auto-select ALL matching seeds. Log: `[auto] Selected N matching seed(s): [list seed names]`
**Text mode (`TEXT_MODE=true`):** Present matching seeds as a plain-text numbered list:
```
Seeds that match your milestone goals:
1. SEED-001: <idea> (trigger: <trigger_when>)
2. SEED-003: <idea> (trigger: <trigger_when>)
Enter numbers to include (comma-separated), or "none" to skip:
```
**Normal mode:** Present via AskUserQuestion:
```
AskUserQuestion(
header: "Seeds",
question: "These planted seeds match your milestone goals. Include any in this milestone's scope?",
multiSelect: true,
options: [
{ label: "SEED-001: <idea>", description: "Trigger: <trigger_when> | Planted during: <planted_during>" },
...
]
)
```
**After selection:**
- Selected seeds become additional context for requirement definition in step 9. Store them in an accumulator (e.g. `$SELECTED_SEEDS`) so step 9 can reference the ideas and their "Why This Matters" sections when defining requirements.
- Unselected seeds remain untouched in `.planning/seeds/` — never delete or modify seed files during this workflow.
## 3. Determine Milestone Version
- Parse last version from MILESTONES.md
@@ -300,6 +349,8 @@ Display key findings from SUMMARY.md:
Read PROJECT.md: core value, current milestone goals, validated requirements (what exists).
**If `$SELECTED_SEEDS` is non-empty (from step 2.5):** Include selected seed ideas and their "Why This Matters" sections as additional input when defining requirements. Seeds provide user-validated feature ideas that should be incorporated into the requirement categories alongside research findings or conversation-gathered features.
**If research exists:** Read FEATURES.md, extract feature categories.
Present features by category:
@@ -492,3 +543,4 @@ Also: `/gsd-plan-phase [N] ${GSD_WS}` — skip discussion, plan directly
**Atomic commits:** Each phase commits its artifacts immediately.
</success_criteria>
</output>