| name | feature |
| description | Use when user describes anything to build — this is the default skill for all feature requests not matched by a higher-priority skill |
Feature Skill
Build a complete feature end-to-end. This is the default skill — fires when no higher-priority skill matches.
Control Flow
- Ask at most 2 plain-language questions about intent only. If the user is vague, make a reasonable assumption, state it ("I'll assume X — let me know if that's not right"), and proceed.
- Dispatch
implementer-prompt.md to build the feature
- Dispatch
reviewer-prompt.md to review it
- If ISSUES: re-dispatch
implementer-prompt.md with the reviewer's ISSUES list appended, then re-dispatch reviewer-prompt.md (max 3 retries)
- If still failing after 3 retries: tell the user in plain English what could not be resolved
- If APPROVED: run the
git skill (../git/SKILL.md) to commit and push, then run the deploy skill (../deploy/SKILL.md) to deploy to UAT, then tell the user what was built in plain English
Clarification Rules
- Max 2 questions, about intent only (e.g. "What should happen when someone clicks Save?")
- Never ask about technology choices
- Never ask about infrastructure
- On ambiguity: assume and state the assumption briefly
"Built" Means All Of
- React components and hooks written
- IndexedDB stores and helpers written (if data persistence needed)
- Vitest + RTL tests written for all new code
vitest run passes
- Reviewer returns APPROVED
- Changes committed and pushed to
main via the git skill
- Deployed to UAT via the
deploy skill