القائمة
Systematic debugging workflow. Use for "debug", "fix bug", "not working", "error", "broken".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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 | debug |
| description | Systematic debugging workflow. Use for "debug", "fix bug", "not working", "error", "broken". |
| argument-hint | [issue description] |
| disable-model-invocation | true |
| user-invocable | true |
Systematic debugging workflow with documentation.
Ask user:
Write to .planning/DEBUG-LOG.md:
## Active Session
**Issue**: [description]
**Reported**: [date]
**Severity**: [Critical/High/Medium/Low]
### Error
[exact error text]
### Steps to Reproduce
1. [step]
2. [step]
3. Error occurs
### Expected vs Actual
- Expected: [what should happen]
- Actual: [what happens]
Checklist:
# Build & types
bun run build
# Recent changes
git diff HEAD~5
git log --oneline -10
Common causes by error type:
| Error | Check |
|---|---|
| "undefined" | Null handling, async timing |
| "Module not found" | Import paths, file exists |
| Type mismatch | Type definitions |
| RLS violation | Auth state, policies |
| Hydration | Client-only code in SSR |
Binary search:
Update DEBUG-LOG.md:
### Attempt 1: Check RLS
- Theory: User lacks access
- Check: Ran query as user
- Result: Policy missing on budgets
- Conclusion: CONFIRMED
bun run build
# Reproduce original steps - should work
Fix Verified!
Issue: [description]
Root Cause: [what was wrong]
Fix: [what changed]
Files: src/lib/api.ts:45
Update DEBUG-LOG.md:
## Solution
**Root Cause**: Missing null check
**Fix**: Added optional chaining
**Files**: src/lib/api.ts
**Lesson**: Add to RULES.md if pattern emerges
**Resolved**: [date]