Menu
Complete a feature — finalise documentation and move it to Completed
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Sync all documentation and feature tracking to reflect the current state of the in-progress feature
Design and plan a feature — move it to in progress and write its design and sub-task plan
Initialises the feature model for this project. Run this once to enable feature workflows.
Create a new feature and write its specification
Code review scoped to files changed in the current feature branch — runs simplicity, general, and nitty agents over the diff, auto-applies code-level findings until convergence, and escalates architectural findings for user confirmation
Code review scoped to a described component or area — resolves the description to files, then runs simplicity, general, and nitty agents; auto-applies code-level findings until convergence; escalates architectural findings for user confirmation
| name | feature-end |
| description | Complete a feature — finalise documentation and move it to Completed |
| argument-hint | ["feature name or slug"] |
Mark a feature as complete and bring all documentation up to date.
Before proceeding, check that CLAUDE.md contains a Feature Model section. If it doesn't, tell the user to run /feature-init first and stop.
The feature to end is: $ARGUMENTS (if blank, use whichever feature is currently in progress in features/CURRENT.md)
Steps:
Run a full checkpoint first (all steps from /feature-checkpoint): update the plan file sub-task statuses, add any outstanding NOTES.md entries, update CLAUDE.md current status.
Confirm all sub-tasks are complete — every sub-task marked ✓ and every one of its sign-off boxes [x] (a ticked sub-task with an unticked box is not done). If any sub-task is incomplete or any sign-off box remains unticked, do not close the feature: either complete the outstanding sign-off, or ask the user whether to defer or drop that sub-task, or keep the feature open.
Update the feature-list files (do this before the documentation review, so the review sees the feature in its final completed state rather than still in progress):
features/CURRENT.md.features/COMPLETED.md (below its header blurb) with the format:### <Feature title> [tags] — <YYYY-MM-DD>
<Two to four sentences summarising what was built, what data was committed, and any notable decisions. No tables, no sub-task lists.>
Call @docs-structure-reviewer to perform a full review that the structure of the documentation is still valid. Apply its feedback, then call it again to confirm. If each call does not have fewer issues than the previous one (i.e. you are converging) ask for user input.
The plan file (features/plans/<slug>.md) can be left as-is to serve as a record of how the feature unfolded.
Report a summary of what was completed and what feature is now next.