Claude Code skills tagged Planning
Skills for stress-testing plans and decisions before any code is written.
Highest-leverage starting points: grill-me to stress-test an idea before any plan exists, then writing-plans to turn it into an executable spec. spec-driven-development forces hidden assumptions to surface before code does, and grill-with-docs sharpens terminology against your project vocabulary. Once execution starts, dispatching-parallel-agents fans out independent work and agents-orchestrator runs the full spec-to-ship pipeline with QA gates between tasks. consciousness-council is the wildcard — six thinking styles arguing a hard call when you cannot decide alone.
13 skills
-
agents-orchestrator
Run a full spec-to-ship pipeline with task-level QA gates instead of one big agent call
-
ce-strategy
Write the one-page product strategy that grounds every downstream planning and ideation session
-
codebase-onboarding-engineer
Get a fast, fact-only mental model of a new repo without inferred-from-vibes summaries
-
consciousness-council
Get six thinking styles to argue your problem out
-
context-engineering
Curate what the agent sees so output stops drifting from project conventions
-
dispatching-parallel-agents
Fan out independent work across parallel subagents instead of working serially
-
grill-me
Stress-test a plan before you commit
-
grill-with-docs
Stress-test a plan against your project's existing vocabulary
-
spec-driven-development
Force assumptions to surface before code gets written, not after
-
to-issues
Convert a plan into vertical-slice GitHub issues
-
triage
Triage incoming issues through a state-machine of roles
-
using-git-worktrees
Start isolated feature work without polluting the main checkout
-
writing-plans
Turn a feature into an executable, no-handwaving implementation plan