Menu
Write feature specifications before implementation with structured templates
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Close a GitHub issue with discipline — resolved, superseded, or duplicate. Pre-flights body + comments, migrates substance before destroying context, cross-links both directions.
File a new GitHub issue with duplicate search, scope decision, label discovery, and preview before posting. Prevents fragmented or silently-filed issues.
Restructure the topology of GitHub issues — split one into many focused replacements, or merge multiple into one keeper. Migrates substance and cross-links before closing anything.
Update an existing GitHub issue — edit body, post a comment, retag, or reopen. Pre-flights body + comments; acknowledges stale framing instead of silently rewriting.
Review and address PR feedback using 6-dimensional code review
Structured code review using 6 dimensions. Works with or without the code-reviewer agent.
| name | feature-spec |
| description | Write feature specifications before implementation with structured templates |
| allowed-tools | Read, Grep, Glob, Bash(gh issue*) |
Document feature requirements before implementation to prevent scope creep and align development with goals.
Write feature specs before coding to align on requirements and prevent scope creep.
Use this template:
# Feature: [Name]
## Problem Statement
[1-2 sentences: What user problem does this solve? Why now?]
## User Story
As a [role], I want to [goal] so that [outcome].
## Acceptance Criteria
1. [ ] [Testable criterion]
2. [ ] [Testable criterion]
## Out of Scope
- [Explicit exclusion]
## Technical Notes
- **Affected files/tables:** [list]
- **Required roles:** [list]
- **Dependencies:** [list]
## Related Issues
- Closes #N
- Depends on #M