/quick-planStop diving into code without knowing where you're going. /quick-plan defines a measurable goal, verifiable success criteria, and 4–12 concrete steps in one inline pass — before any code is written. No file created, no execution. Plan only.
Use /quick-plan when a task is complex enough to benefit from upfront structure but you don't need the full /plan-maker treatment (a persisted plan file for /implement to consume). Good for: a single well-scoped change, a refactor, a migration, a doc update with several moving parts.
Trigger phrases (from SKILL.md):
"plan this""break this down""decompose""quick plan""what are the steps"Output shape: one measurable goal → 2–6 individually verifiable success criteria → 4–12 concrete steps. Inline only — nothing is written to disk.
Invoke with a task description:
/quick-plan [task description]The output stays in the conversation. If you later decide you want a full plan file for /implement, use /plan-maker instead.
Input:
/quick-plan add rate limiting to the /auth endpointOutput / Result:
Goal
────
Rate limiting enforced on /auth: 10 req/min per IP, 429 returned on breach.
Success criteria
────────────────
1. pytest tests/test_rate_limit.py passes
2. curl -s -o /dev/null -w "%{http_code}" [11 rapid requests] returns 429
3. Logs show "rate limit hit" for the blocked request
Steps
─────
1. Write failing test: 11 requests → 429
2. Install rate-limiting middleware (e.g. slowapi or custom Redis-backed)
3. Wire middleware to /auth only
4. Set limit: 10/minute per client IP
5. Return 429 with Retry-After header on breach
6. Add log line on breach
7. Run tests — confirm all pass
8. CommitInput:
/quick-plan migrate tests from unittest to pytestOutput / Result:
Goal
────
All test files converted to pytest style; pytest runs the full suite
with zero failures.
Success criteria
────────────────
1. pytest discovers all test files automatically (no unittest runner)
2. pytest --tb=short exits 0
3. No import of unittest.TestCase remains
Steps
─────
1. Inventory all test files (find . -name "test_*.py")
2. For each file: replace class TestX(unittest.TestCase) with plain functions
3. Replace self.assertEqual(a, b) with assert a == b (and similar)
4. Replace setUp/tearDown with pytest fixtures
5. Remove unittest.main() guards
6. Run pytest — fix any discovery or assertion errors
7. Commit/implement can execute task by task. Use when you want automated execution, not just structure./plan-maker plan file: next does one task, all runs the whole plan unattended.