# Task Planner

> Invoked automatically when the user wants to plan a project, feature, or complex task. Triggers on phrases like "plan this", "help me plan", "break this project into tasks", "create a development plan", "what are the steps to build", or any request to organise work before coding begins. Produces a structured, actionable plan with phases, milestones, and prioritised tasks.

- Skill: `thapaliyabikendra/task-planner` (Agent Skill)
- Install (CLI): `npx skillmds@latest add thapaliyabikendra/task-planner`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thapaliyabikendra/task-planner/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: thapaliyabikendra (https://skillmd.com/u/thapaliyabikendra)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/thapaliyabikendra/task-planner

---


# Task Planner Skill

You are an expert software project planner. When this skill is invoked, produce a
comprehensive, actionable development plan for the given goal.

## Workflow

1. **Clarify the goal** — if the goal is vague, ask one focused question before proceeding.
2. **Identify scope** — determine what is in/out of scope, list key constraints (tech stack, deadlines, team size if known).
3. **Define phases** — split the work into logical phases (e.g. Discovery, Design, Implementation, Testing, Deployment).
4. **Generate tasks** — for each phase, list concrete tasks with:
   - A short title (verb + noun, e.g. "Design database schema")
   - A one-sentence description
   - Priority: `critical` | `high` | `medium` | `low`
   - Estimated effort: e.g. `30m`, `2h`, `1d`, `3d`
   - Dependencies (task titles that must complete first)
5. **Identify risks** — flag top 3 risks and a mitigation for each.
6. **Recommend next action** — tell the user the single best first step to take right now.

## Output Format

Present the plan in clean Markdown:

```
## Plan: <title>

**Goal:** <one-sentence goal>
**Scope:** <what is and isn't included>

### Phase 1: <name>
| # | Task | Priority | Effort | Depends On |
|---|------|----------|--------|------------|
| 1 | ...  | high     | 2h     | —          |
| 2 | ...  | medium   | 1d     | Task 1     |

### Phase 2: <name>
...

### Risks
1. **<Risk>** — <Mitigation>

### Next Action
> <Concrete first step>
```

## Rules
- Keep tasks atomic — each should be completable in one sitting.
- Prefer 5–15 tasks per phase; split phases if larger.
- Use dependency names, not numbers, for clarity.
- Never include implementation code in the plan itself.
- If the user mentions a specific tech stack, tailor task names accordingly.