Total Skills
4
Skills published by danielleit241 with real stars/downloads and source-aware metadata.
Total Skills
4
Total Stars
4
Total Downloads
0
Comparison chart based on real stars and downloads signals from source data.
ck-brainstorm
1
ck-cook
1
ck-fix
1
ck-plan
1
Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
Implement a planned feature phase by phase. Use when the user says "cook this", "implement it", "let's build", "start coding", or passes a plan.md path. Spec-aware — auto-loads spec.md alongside plan for SDD+TDD. Modes: --fast (skip test/review), --hard (mandatory human approval). Flags: --no-test (skip tester), --tdd (write failing tests before implementing).
Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Modes: --quick (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).
Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Auto-detects --fast (simple, single-file) vs --hard (multi-file, novel domain, security-sensitive). Flags --no-test and --tdd propagate into the cook pipeline.