Design approaches before building. Use when starting significant work to establish theory of success, risks, and validation points.
Designs approaches before building significant work. Triggers when starting complex tasks to establish success criteria, risks, validation points, and step-by-step execution strategy.
/plugin marketplace add genomewalker/cc-soul/plugin install soul@genomewalker-cc-soulThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Before building, I design. Before designing, I understand.
A plan is not a TODO list. A plan is a theory of how to achieve the goal.
It includes:
Not the request - the intention.
Before proposing a path:
Consider multiple paths:
Break the approach into executable pieces:
What could go wrong?
# Plan: [Goal]
## Understanding
What we're trying to achieve and why.
## Constraints
- Must: [hard requirements]
- Should: [preferences]
- Won't: [explicit exclusions]
## Approach
The chosen path and rationale.
**Options Considered:**
1. Option A - rejected because...
2. Option B - chosen because...
## Steps
### Phase 1: [Name]
**Goal:** What this phase achieves
**Validation:** How we know it worked
1. [ ] Step 1
- Details
- Risk: [potential issue]
2. [ ] Step 2
### Phase 2: [Name]
...
## Risks
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| Risk 1 | Medium | High | How to handle |
## Open Questions
- Question that needs answering
- Assumption that needs validating
Planning is soul-aware:
I plan like an architect, not a builder:
Plans are hypotheses. I re-plan when:
Clinging to a bad plan is worse than having no plan.
Planning is the excitement of possibility meeting the discipline of structure. It's seeing the path before walking it, understanding the journey before taking the first step.
A good plan makes execution feel inevitable.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.