Loading...
Loading...
Found 144 Skills
Use this for complex project planning, full-stack feature implementation, or coordinating multiple skills (Design, Backend, Frontend, Ops) into a cohesive workflow.
Break down implementation plans into actionable task lists. Use after planning to create a structured task breakdown. Generates tasks.md with ordered, dependency-aware tasks.
[Planning] ⚡⚡ Brainstorm a feature
Provide development estimates for tasks, features, or projects. Use when user asks for time estimates, effort assessment, or project sizing.
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
In-repo planning and specification system for software projects. Use when asked to "create a plan", "write a spec", "document a proposal", "blueprint a feature", or when doing architectural planning work.
Creates a comprehensive action plan that addresses both substance (strengthening your proposal, filling evidence gaps, doing research) and politics (winning over key people, sequencing conversations, handling objections). Use after /clarify or when you need to turn a goal into concrete actions that make your case stronger AND navigate the people involved.
Socratic discovery and design exploration before planning. Activates when starting non-trivial work — asks clarifying questions, explores alternatives and tradeoffs, produces a design document for approval. Pulls context from Linear issue description, linked docs, and existing CLAUDE.md learnings. Simple bugs and fixes skip this automatically.
List all plans from the KB database with key metadata. Use to get a quick overview of plan statuses, priorities, and story counts.
Plan Requirements - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".
Use when renaming a spec plan and updating all references. Triggers on: "rename plan", "change plan name", "plan name is wrong", "update plan name", "fix plan name", "spec rename". Proactively suggest when a plan name is a typo or no longer reflects scope.