How do I install the Task Planner skill?

Run npx skillmds@latest add thapaliyabikendra/task-planner in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Task Planner safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Task Planner?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Task Planner free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Task Planner?

thapaliyabikendra (@thapaliyabikendra) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Task Planner by thapaliyabikendra — Agent Skill

Name: Task Planner
Author: thapaliyabikendra

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.

File contents

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

Clarify the goal — if the goal is vague, ask one focused question before proceeding.
Identify scope — determine what is in/out of scope, list key constraints (tech stack, deadlines, team size if known).
Define phases — split the work into logical phases (e.g. Discovery, Design, Implementation, Testing, Deployment).
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)
Identify risks — flag top 3 risks and a mitigation for each.
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.

---name: task-plannerdescription: 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.---# Task Planner SkillYou are an expert software project planner. When this skill is invoked, produce acomprehensive, actionable development plan for the given goal.## Workflow1. **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 FormatPresent 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>...### Risks1. **<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.

Frequently asked questions