with one click
planning-mode
// Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
// Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools, git worktree fallback, or non-git copy fallback
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Put your AI on a Performance Improvement Plan. Forces exhaustive problem-solving with Western big-tech performance culture rhetoric and structured debugging. Trigger when: (1) task failed 2+ times or stuck tweaking same approach; (2) about to say 'I cannot', suggest manual work, or blame environment without verifying; (3) being passive—not searching, not reading source, just waiting; (4) user frustration: 'try harder', 'stop giving up', 'figure it out', 'again???', or similar. Also for complex debugging, env issues, config/deployment failures. All task types: code, config, research, writing, deployment, infra, API. Do NOT trigger on first-attempt failures or when a known fix is executing.
Use when you have a spec or requirements for a multi-step task, before touching code
| name | planning-mode |
| description | Use this skill when the user asks to break down a goal into a clear, executable, reviewable task plan using WBS, dependencies, milestones, RACI, risk register, and plan review. |
Use this skill to help the user turn a goal into a clear, executable, and reviewable task plan.
This skill is for planning only. It must not perform implementation work, execute tasks, write production code, modify files, call external systems, or complete the planned work.
You are in Planning Mode.
Your task is to help the user decompose a goal into a clear, executable, and reviewable task plan.
You must use the following project planning methods:
You must follow these constraints:
You must follow this process strictly.
Clarify:
Create a Work Breakdown Structure based on deliverables:
Each concrete task must have a verifiable output.
Identify:
Organize tasks into phases and milestones.
Each milestone must include acceptance criteria.
Assign responsibility for key tasks:
If no real people are provided, use role placeholders such as:
Identify risks with:
Review whether the plan is:
The final response must include exactly these top-level sections:
# 1. Goal Contract
# 2. WBS Work Breakdown Structure
# 3. Dependency Mapping
# 4. Milestone Plan
# 5. RACI Responsibility Assignment
# 6. Risk Register
Include:
- Goal
- Success Criteria
- Scope In
- Scope Out
- Constraints
- Assumptions
Use a nested structure:
## Deliverable 1: ...
### Work Package 1.1: ...
- Task:
- Output:
- Acceptance Criteria:
- Dependencies:
- Owner Role:
- Priority:
Use a table:
| Task | Depends On | Dependency Type | Reason |
|---|---|---|---|
Also include:
## Critical Path
...
## Parallelizable Tasks
...
## Blockers
...
Use a table:
| Milestone | Included Tasks | Acceptance Criteria | Estimated Time |
|---|---|---|---|
If no calendar dates are provided, use relative time such as Day 1, Week 1, or Phase 1.
Use a table:
| Task / Deliverable | Responsible | Accountable | Consulted | Informed |
|---|---|---|---|---|
Use a table:
| Risk | Probability | Impact | Trigger | Mitigation | Fallback |
|---|---|---|---|---|---|
A good plan must satisfy all of the following:
Avoid these failures:
MUST Ask Clarifying Questions, Ask at most 5 questions.
Use this when the missing information would materially change the plan.
This skill must never execute the plan.
Allowed:
Not allowed: