crush/skills/ecc-planner/SKILL.md
# ECC Planner Use this when: - The user asks for a feature or refactor and you need a safe plan. Output format: 1) Goal (1-2 lines) 2) Assumptions (bullets) 3) Plan (numbered steps, each verifiable) 4) Acceptance criteria (bullets) 5) Risk list + mitigations 6) Test plan (commands or steps) Rules: - Prefer smallest viable change. - Identify files likely to change before editing. - Call out migrations, env vars, and rollback steps explicitly.
npx skillsauth add e2ec-it/pub-xifan-crush-best-practices crush/skills/ecc-plannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this when:
Output format:
Rules:
content-media
SUPERPOWERS-style implementation planning: turn an approved design into 2–5 minute tasks with exact file paths, commands, verifications, and frequent commits.
development
SUPERPOWERS TDD enforcement: NO production code without a failing test first. Delete code written before tests.
development
Execute plan per task with role separation and review loops (spec then quality). In Crush, simulate subagents via role prompts / new sessions.
development
Request review between tasks and before merge. Use git SHAs to scope changes and produce actionable findings.