B. User Prompting
When the workflow needs user input, prompt the user conversationally:
- Present options as a numbered list in your response text
- Ask the user to reply with their choice
- For multi-select, ask for comma-separated numbers
C. Tool Usage
Use these Augment tools when executing GSD workflows:
launch-process for running commands (terminal operations)str-replace-editor for editing existing filesview for reading files and listing directoriessave-file for creating new filesgrep for searching code (or use MCP servers for advanced search)web-search, web-fetch for web queriesadd_tasks, view_tasklist, update_tasks for task management
D. Subagent Spawning
When the workflow needs to spawn a subagent:
- Use the built-in subagent spawning capability
- Define agent prompts in
.augment/agents/ directory
- Net-new bootstrap (
--mode new, default when .planning/ is absent): produces PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md from synthesized doc content, delegating final generation to gsd-roadmapper.
- Merge into existing (
--mode merge, default when .planning/ is present): appends phases and requirements derived from the ingested docs; hard-blocks any contradiction with existing locked decisions.
Auto-synthesizes most conflicts using the precedence rule ADR > SPEC > PRD > DOC (overridable via manifest). Surfaces unresolved cases in .planning/INGEST-CONFLICTS.md with three buckets: auto-resolved, competing-variants, unresolved-blockers. The BLOCKER gate from the shared conflict engine prevents any destination file from being written when unresolved contradictions exist.
Inputs: directory-convention discovery (docs/adr/, docs/prd/, docs/specs/, docs/rfc/, root-level {ADR,PRD,SPEC,RFC}-*.md), or an explicit --manifest <file> YAML listing {path, type, precedence?} per doc.
v1 constraints: hard cap of 50 docs per invocation; --resolve interactive is reserved for a future release.
1---2name: gsd-ingest-docs-33description: Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.4---56<augment_skill_adapter>7## A. Skill Invocation8- This skill is invoked when the user mentions `gsd-ingest-docs` or describes a task matching this skill.9- Treat all user text after the skill mention as `{{GSD_ARGS}}`.10- If no arguments are present, treat `{{GSD_ARGS}}` as empty.1112## B. User Prompting13When the workflow needs user input, prompt the user conversationally:14- Present options as a numbered list in your response text15- Ask the user to reply with their choice16- For multi-select, ask for comma-separated numbers1718## C. Tool Usage19Use these Augment tools when executing GSD workflows:20- `launch-process` for running commands (terminal operations)21- `str-replace-editor` for editing existing files22- `view` for reading files and listing directories23- `save-file` for creating new files24- `grep` for searching code (or use MCP servers for advanced search)25- `web-search`, `web-fetch` for web queries26- `add_tasks`, `view_tasklist`, `update_tasks` for task management2728## D. Subagent Spawning29When the workflow needs to spawn a subagent:30- Use the built-in subagent spawning capability31- Define agent prompts in `.augment/agents/` directory32</augment_skill_adapter>3334<objective>35Build the full `.planning/` setup (or merge into an existing one) from multiple pre-existing planning documents — ADRs, PRDs, SPECs, DOCs — in one pass.3637- **Net-new bootstrap** (`--mode new`, default when `.planning/` is absent): produces PROJECT.md + REQUIREMENTS.md + ROADMAP.md + STATE.md from synthesized doc content, delegating final generation to `gsd-roadmapper`.38- **Merge into existing** (`--mode merge`, default when `.planning/` is present): appends phases and requirements derived from the ingested docs; hard-blocks any contradiction with existing locked decisions.3940Auto-synthesizes most conflicts using the precedence rule `ADR > SPEC > PRD > DOC` (overridable via manifest). Surfaces unresolved cases in `.planning/INGEST-CONFLICTS.md` with three buckets: auto-resolved, competing-variants, unresolved-blockers. The BLOCKER gate from the shared conflict engine prevents any destination file from being written when unresolved contradictions exist.4142**Inputs:** directory-convention discovery (`docs/adr/`, `docs/prd/`, `docs/specs/`, `docs/rfc/`, root-level `{ADR,PRD,SPEC,RFC}-*.md`), or an explicit `--manifest <file>` YAML listing `{path, type, precedence?}` per doc.4344**v1 constraints:** hard cap of 50 docs per invocation; `--resolve interactive` is reserved for a future release.45</objective>4647<execution_context>48@/home/delorenj/code/bhappy/.augment/get-shit-done/workflows/ingest-docs.md49@/home/delorenj/code/bhappy/.augment/get-shit-done/references/ui-brand.md50@/home/delorenj/code/bhappy/.augment/get-shit-done/references/gate-prompts.md51@/home/delorenj/code/bhappy/.augment/get-shit-done/references/doc-conflict-engine.md52</execution_context>5354<context>55{{GSD_ARGS}}56</context>5758<process>59Execute the ingest-docs workflow end-to-end. Preserve all approval gates (discovery, conflict report, routing) and the BLOCKER safety rule.60</process>
delorenj