1.4 KiB
1.4 KiB
name, description, argument-hint, model
| name | description | argument-hint | model | |
|---|---|---|---|---|
| specification-sign-off | Get user approval on implementation plan |
|
claude-haiku-4-5 |
Specification Sign-Off Command
Purpose
Get sign-off on the specification for the increment to be implemented. These instructions are read and followed as part of a larger workflow. You MUST follow all workflow steps below, not skipping any step and doing all steps in order.
Workflow Steps
-
Read State Management File:
- Read the state management file (path in $1)
- Locate the specification file path
- Present the Implementation Plan section to the user for review
-
Get User Feedback:
-
Ask the user to read and provide feedback on the Implementation Plan
-
If user has feedback: a. Use the specification-writer subagent to revise specification:
State management file: $1 User feedback to address: [user's feedback verbatim]b. The subagent will detect the feedback and revise accordingly c. Return to step 1 for re-review
-
If user provides explicit sign-off, proceed to step 3
-
-
Add Issue Comment:
- Did you get explicit approval on the specification? If not, go back to step 2.
- Read the state management file to get the issue key
- Use the SlashCommand tool to execute
/create-comment [issue-key] "[specification details and assumptions]"