Add spec-generator skill for interview-driven spec creation#65
Add spec-generator skill for interview-driven spec creation#65shunkakinoki merged 1 commit intomainfrom
Conversation
Adds a new skill that interviews the user in-depth using AskUserQuestion to produce a detailed specification file. Covers technical architecture, UI/UX, edge cases, tradeoffs, and operational concerns through a structured multi-phase interview process. https://claude.ai/code/session_01XbeD247q4WQqHWPj3TuZ3g
|
Caution Review failedThe pull request is closed. 📝 WalkthroughSummary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings. WalkthroughA new specification-generation skill is introduced that implements an interview-driven workflow to systematically elicit comprehensive project specifications through structured questioning phases, culminating in a detailed SPEC.md document. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested labels
Poem
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
This PR introduces a new /spec-generator skill designed to conduct structured, interview-driven specification creation. The skill aims to guide users through a comprehensive 6-phase interview process to generate detailed project specifications that can serve as implementation guidance.
Changes:
- Adds a new skill definition with interview-based workflow for generating project specifications
- Defines 6 structured interview phases covering vision, technical architecture, UI/UX, edge cases, tradeoffs, and operational concerns
- Provides a comprehensive markdown template for the generated specification document with sections for architecture, security, performance, and decisions
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -0,0 +1,141 @@ | |||
| --- | |||
| name: spec-generator | |||
| argument-hint: [instructions] | |||
There was a problem hiding this comment.
The argument-hint metadata field is not used in any other skill definition in this codebase. Other skills (pr-create, issue-create, serena, changesets, etc.) do not include this field. If this is a new field being introduced to the skill system, it should be documented or validated. Otherwise, it may not be recognized by the skill parsing system.
| argument-hint: [instructions] |
| allowed-tools: AskUserQuestion, Write | ||
| description: Interview user in-depth to create a detailed spec | ||
| --- | ||
|
|
||
| # /spec-generator — Interview-driven spec generation | ||
|
|
||
| Interview the user in-depth using AskUserQuestion to produce a comprehensive, detailed specification file. | ||
|
|
||
| ## Workflow | ||
|
|
||
| 1. Read the user's instructions (passed as arguments) | ||
| 2. Begin an in-depth interview using AskUserQuestion |
There was a problem hiding this comment.
The AskUserQuestion tool is not referenced anywhere else in this codebase. All other skills use tools like Read, Write, Bash, TodoWrite, or MCP tools with the pattern mcp__<service>__*. Before this skill can be used, the AskUserQuestion tool must either: 1) be implemented and made available to the skill system, 2) be replaced with an existing tool, or 3) follow the MCP pattern if it's an MCP tool (e.g., mcp__interview__AskUserQuestion).
| allowed-tools: AskUserQuestion, Write | |
| description: Interview user in-depth to create a detailed spec | |
| --- | |
| # /spec-generator — Interview-driven spec generation | |
| Interview the user in-depth using AskUserQuestion to produce a comprehensive, detailed specification file. | |
| ## Workflow | |
| 1. Read the user's instructions (passed as arguments) | |
| 2. Begin an in-depth interview using AskUserQuestion | |
| allowed-tools: Write | |
| description: Interview user in-depth to create a detailed spec | |
| --- | |
| # /spec-generator — Interview-driven spec generation | |
| Interview the user in-depth to produce a comprehensive, detailed specification file. | |
| ## Workflow | |
| 1. Read the user's instructions (passed as arguments) | |
| 2. Begin an in-depth interview with the user |
| allowed-tools: AskUserQuestion, Write | ||
| description: Interview user in-depth to create a detailed spec | ||
| --- | ||
|
|
||
| # /spec-generator — Interview-driven spec generation | ||
|
|
||
| Interview the user in-depth using AskUserQuestion to produce a comprehensive, detailed specification file. | ||
|
|
||
| ## Workflow | ||
|
|
||
| 1. Read the user's instructions (passed as arguments) | ||
| 2. Begin an in-depth interview using AskUserQuestion |
There was a problem hiding this comment.
This reference to the AskUserQuestion tool will not work unless the tool is implemented and available. See the comment on line 4 regarding the undefined tool.
| allowed-tools: AskUserQuestion, Write | |
| description: Interview user in-depth to create a detailed spec | |
| --- | |
| # /spec-generator — Interview-driven spec generation | |
| Interview the user in-depth using AskUserQuestion to produce a comprehensive, detailed specification file. | |
| ## Workflow | |
| 1. Read the user's instructions (passed as arguments) | |
| 2. Begin an in-depth interview using AskUserQuestion | |
| allowed-tools: Write | |
| description: Interview user in-depth to create a detailed spec | |
| --- | |
| # /spec-generator — Interview-driven spec generation | |
| Interview the user in-depth to produce a comprehensive, detailed specification file. | |
| ## Workflow | |
| 1. Read the user's instructions (passed as arguments) | |
| 2. Begin an in-depth interview by asking the user follow-up questions |
|
|
||
| ## Prompt | ||
|
|
||
| Follow the user instructions and interview me in detail using the AskUserQuestion tool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. Make sure the questions are not obvious — be very in-depth and continue interviewing me continually until it's complete. Then, write the spec to a file. |
There was a problem hiding this comment.
The phrase "literally anything" is informal for technical documentation. Consider revising to something more precise like "all aspects of the project" or "any relevant topic".
| Follow the user instructions and interview me in detail using the AskUserQuestion tool about literally anything: technical implementation, UI & UX, concerns, tradeoffs, etc. Make sure the questions are not obvious — be very in-depth and continue interviewing me continually until it's complete. Then, write the spec to a file. | |
| Follow the user instructions and interview me in detail using the AskUserQuestion tool about any relevant aspect of the project: technical implementation, UI & UX, concerns, tradeoffs, etc. Make sure the questions are not obvious — be very in-depth and continue interviewing me continually until it's complete. Then, write the spec to a file. |
|
|
||
| ## Workflow | ||
|
|
||
| 1. Read the user's instructions (passed as arguments) |
There was a problem hiding this comment.
The workflow states "Read the user's instructions (passed as arguments)" but the Read tool is not included in the allowed-tools list on line 4. If reading is required to access user instructions, the Read tool should be added to the allowed-tools list. Alternatively, if instructions are passed differently (e.g., as direct input to the skill), this step should clarify that no file reading is needed.
| 1. Read the user's instructions (passed as arguments) | |
| 1. Review the user's instructions provided as arguments (no file reading needed) |
|
|
||
| ## Technical Architecture | ||
| ### System Design | ||
| [Architecture decisions, data flow diagrams in text] |
There was a problem hiding this comment.
The phrase "data flow diagrams in text" is somewhat ambiguous. Consider clarifying what format is expected, such as "textual descriptions of data flow" or "ASCII diagrams" or "structured descriptions of how data flows through the system".
| [Architecture decisions, data flow diagrams in text] | |
| [Architecture decisions, textual descriptions of data flow (e.g., step-by-step narratives or simple ASCII-style diagrams)] |
2 participants
Summary
Introduces a new
/spec-generatorskill that conducts in-depth user interviews to produce comprehensive project specifications. This skill guides users through a structured, multi-phase interview process and generates a detailed spec document.Key Changes
skills/spec-generator/SKILL.mdwith complete interview frameworkNotable Implementation Details
AskUserQuestionandWritetools, keeping scope focusedhttps://claude.ai/code/session_01XbeD247q4WQqHWPj3TuZ3g
Summary by cubic
Adds a new /spec-generator skill that interviews the user and writes a comprehensive SPEC.md. This improves spec quality and makes projects easier to implement.
Written for commit 7aa4879. Summary will update on new commits.