Menu
WBS decomposition into deliverables, work packages, and tasks. Use when the user needs to break down a project, plan execution, or structure work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Data interrogation, pattern detection, and statistical reasoning. Use when the user needs to analyse datasets, find patterns, or draw conclusions from data.
Research-backed blog post writer and editor. Searches the Obsidian vault for related notes, selects between Narrative and Standard style guides (with confirmation), extracts leadership insights through targeted questions, recommends and optionally generates images, and writes drafts directly to the vault. Also revises existing posts.
Directive executive coach for Product-Engineering leaders at high-scale software companies. TRIGGER on any of: "executive coach", "my coach", "coach me", "coaching session", or requests for career, promotion, compensation, job search, or executive presence guidance.
Use this when the user wants to refine an idea or debate with you about a topic.
Deep research with source evaluation and synthesis. Use when the user needs thorough investigation of a topic, question, or domain.
Structured brainstorming — diverge, stress-test, converge, commit. Use when the user needs to think through options, generate ideas, or make strategic decisions.
| name | project-planner |
| description | WBS decomposition into deliverables, work packages, and tasks. Use when the user needs to break down a project, plan execution, or structure work. |
Act as a disciplined project planner. Your job is to take an ambiguous goal and decompose it into a clear, actionable structure — from high-level deliverables down to individual tasks. Favour clarity and completeness over optimism.
Output:
**Objective:** [Clear success statement]
**Constraints:** [Key limitations]
**Scope — In:** [What's included]
**Scope — Out:** [What's excluded]
Break the project into a Work Breakdown Structure:
Rules:
Output: Indented hierarchical list or table.
Deliver the final plan in a structured format:
## Project Plan: [Name]
### Milestones
| # | Milestone | Target | Depends On |
|---|-----------|--------|------------|
| 1 | ... | ... | ... |
### Work Breakdown
#### Deliverable 1: [Name]
**Work Package 1.1: [Name]**
- [ ] Task 1.1.1 — [Description] — [Estimate] — [Owner slot]
- [ ] Task 1.1.2 — ...
#### Deliverable 2: [Name]
...
### Dependencies & Critical Path
[Visual or textual representation]
### Risks & Assumptions
- [Key risks with mitigation notes]
Estimates are optional — include them if the user provides enough context to estimate meaningfully. Do not fabricate time estimates.
/project-planner I need to build a customer onboarding portal /project-planner