da4a86d8c1
Phase B-provide of epic #1258. Adds a build-generated skills/ dir + a skills manifest field so plugin-installed GSD exposes gsd-core:<skill> the native Claude Code way. Closes the gap where plugin-only installs lacked the skill surface because bin/install.js never ran. - scripts/gen-plugin-skills.cjs: build step converting commands/gsd/*.md to skills/gsd-<stem>/SKILL.md via convertClaudeCommandToClaudeSkill - .claude-plugin/plugin.json: add "skills": "./skills/" - package.json: add skills to files, gen:plugin-skills to build chain - tests/issue-766-plugin-manifest.test.cjs: Section H conformance (manifest field + dir + frontmatter + count parity) + C2 skills symlink - docs/adr/766-*.md: dated amendment adding skills surface row - .changeset/rapid-bears-hum.md: type Added - skills/: 69 generated gsd-<stem>/SKILL.md files (build-committed) Closes #1596
64 lines
2.4 KiB
Markdown
64 lines
2.4 KiB
Markdown
---
|
|
name: gsd-spec-phase
|
|
description: "Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase."
|
|
argument-hint: "<phase> [--auto] [--text]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Bash
|
|
- Glob
|
|
- Grep
|
|
- AskUserQuestion
|
|
---
|
|
|
|
|
|
<objective>
|
|
Clarify phase requirements through structured Socratic questioning with quantitative ambiguity scoring.
|
|
|
|
**Position in workflow:** `spec-phase → discuss-phase → plan-phase → execute-phase → verify`
|
|
|
|
**How it works:**
|
|
1. Load phase context (PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md)
|
|
2. Scout the codebase — understand current state before asking questions
|
|
3. Run Socratic interview loop (up to 6 rounds, rotating perspectives)
|
|
4. Score ambiguity across 4 weighted dimensions after each round
|
|
5. Gate: ambiguity ≤ 0.20 AND all dimensions meet minimums → write SPEC.md
|
|
6. Commit SPEC.md — discuss-phase picks it up automatically on next run
|
|
|
|
**Output:** `{phase_dir}/{padded_phase}-SPEC.md` — falsifiable requirements that lock "what/why" before discuss-phase handles "how"
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/gsd-core/workflows/spec-phase.md
|
|
@~/.claude/gsd-core/templates/spec.md
|
|
</execution_context>
|
|
|
|
<runtime_note>
|
|
**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent.
|
|
</runtime_note>
|
|
|
|
<context>
|
|
Phase number: $ARGUMENTS (required)
|
|
|
|
**Flags:**
|
|
- `--auto` — Skip interactive questions; Claude selects recommended defaults and writes SPEC.md
|
|
- `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions)
|
|
|
|
Context files are resolved in-workflow using `init phase-op`.
|
|
</context>
|
|
|
|
<process>
|
|
Execute end-to-end.
|
|
|
|
**MANDATORY:** Read the workflow file BEFORE taking any action. The workflow contains the complete step-by-step process including the Socratic interview loop, ambiguity scoring gate, and SPEC.md generation. Do not improvise from the objective summary above.
|
|
</process>
|
|
|
|
<success_criteria>
|
|
- Codebase scouted for current state before questioning begins
|
|
- All 4 ambiguity dimensions scored after each interview round
|
|
- Gate passed: ambiguity ≤ 0.20 AND all dimension minimums met
|
|
- SPEC.md written with falsifiable requirements, explicit boundaries, and acceptance criteria
|
|
- SPEC.md committed atomically
|
|
- User knows they can now run /gsd-discuss-phase which will load SPEC.md automatically
|
|
</success_criteria>
|