Menu
<!-- ONE sentence: what the skill does AND when to trigger. See guide below. [REQUIRED] -->
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
When the user wants to add a new feature or capability. When the user says "I want to build" or "I'm thinking about". When requirements are unclear and need to be refined.
When the user says they are ready for review or wants to create a PR. When the user asks to check if code is ready for review. When the task or feature is complete and needs quality validation.
When the user approves a plan and wants to execute it. When the user says "execute the plan" or "let's go" or "start implementation". When a PLAN.md exists and is ready to be executed task-by-task.
When the user is implementing a new feature or fixing a bug. When the user wants to write tests first before writing code. When the user is refactoring and needs to verify behaviour is preserved.
When the user wants to create an implementation plan. When the user says "let's implement this" or "create a plan". When a design has been approved and is ready to be broken into tasks.
Systematic code review workflow — evaluate changes for correctness, style, security, and test coverage before merging. When the user asks to review code or a pull request. When the user says "check code quality" or "look over this diff". When the user requests feedback on changes before merging.
| name | <% tp.file.title | replace(" ", "-") | lower %> |
| description | <!-- ONE sentence: what the skill does AND when to trigger. See guide below. [REQUIRED] --> |
When PRG validates a SKILL.md and any rule fails, it prints the rule ID and the offending location. -->
leave placeholders.
Re-read each section against the rules in its (now-deleted) GUIDE comment.
Confirm: no <!-- GUIDE --> comments remain, every [REQUIRED] section is
non-empty, Acceptance Criteria has >=1 checkbox.
Write to specs/<feature-slug>-SPEC.md. Print the path and a one-paragraph
summary of what the spec covers.
STATUS: [REQUIRED] — must contain at least 3 numbered steps.
-->
