Menu
Quick task without full workflow. Use for "quick", "just add", "small change", "simple fix".
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
Executes all tasks in a specific phase using wave-based parallel execution (max 4 agents per wave). Spawns small-coder and high-coder agents based on progress.json complexity. Updates progress.json after EACH wave so completed tasks immediately unblock dependents. Accepts phase number as argument (/execute-phase 3) or asks via AskUserQuestion. Triggers on: execute phase, run phase, build phase, develop phase, start phase.
Generates Vitest test files from test-plan.md using the qa-specialist agent. Reads the test plan and vitest best practices, then spawns qa-specialist agents to produce .test.ts files in the root tests/ directory for features, shared tests, and Supabase integration tests. Tests verify behavior via database operations and RLS policies — no UI testing. Triggers on: generate test, generate tests, create tests, write tests, test generation.
Orchestrates sequential project planning. First validates user intent via AskUserQuestion (MANDATORY), then spawns ui-ux-specialist to create ui-ux-plan.md, then tech-lead-specialist to create dev-plan.md from ui-ux-plan.md, then spawns frontend-specialist and backend-specialist in parallel to create their detailed plans from dev-plan.md, then spawns qa-specialist to create test-plan.md from dev-plan.md and backend-plan.md. Triggers on: plan, create plan, plan project, project plan, full plan, prd to plan.
Runs ALL Vitest tests across /features, /tests, and /supabase directories. Executes tests via npx vitest run, collects results, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures and provide actionable feedback. Triggers on: run test all, run all tests, test all, vitest all, run tests.
Runs Vitest tests for a specific phase chosen by the user. Reads test-plan.md to identify phases, asks user which phase to run via AskUserQuestion, executes only those test files, and generates test.result.json (replaced on every run). Uses qa-specialist to analyze failures. Triggers on: run test phase, test phase, run phase test, test specific phase.
Verifies and updates tests after code changes. Detects what changed (git diff, changes.json), compares against test-plan.md, then spawns qa-specialist agents to update test-plan.md and edit/create test files in /features, /tests, /supabase. Use after /developer or manual changes to keep tests in sync. Triggers on: verify test, verify tests, sync tests, update tests, check tests, test verify.
| name | quick |
| description | Quick task without full workflow. Use for "quick", "just add", "small change", "simple fix". |
| argument-hint | [task description] |
| disable-model-invocation | true |
| user-invocable | true |
For small tasks that don't need PRD/checkpoints.
✅ Use /quick for:
❌ Don't use for:
/quick "add logout button to header"
↓
Complexity check
↓
Implement (auto-apply UI rules if needed)
↓
Build + Lint + Test
↓
Show diff → Human approval → Commit
Quick task: "add logout button to header"
Checking complexity...
- Estimated files: 1-2
- Complexity: Low ✅
If too complex:
⚠️ This seems larger than a quick task:
- May need new API endpoint
- Touches 5+ files estimated
Recommend: /init-project or /checkpoint
Continue anyway? [y/n]
If task involves UI files:
🎨 UI task detected. Applying rules:
- No gradients
- No animations
- Use shadcn/ui
Do the work. Follow rules from .claude/rules/.
bun run build
bun run lint
bun run test --passWithNoTests 2>/dev/null || true
## Verification
| Check | Status |
|-------|--------|
| Build | ✅ |
| Lint | ✅ |
| Tests | ✅ |
Auto-fix lint if needed.
git diff --stat
## Changes
**Files**: 1 changed (+15/-2)
| File | Changes |
|------|---------|
| components/header.tsx | +15 / -2 |
### What Changed
- Added SignOutButton to header nav
- Imported from @/components/auth
## Ready to Commit
Task: Add logout button to header
Files: 1 changed (+15/-2)
Commit message:
"feat(ui): add logout button to header"
Approve?
Options:
git add -A
git commit -m "feat(ui): add logout button to header
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"
✅ Done!
Commit: abc1234
Task: Add logout button to header
Files: 1 (+15/-2)