# Project Planner

> Use for project planning, task decomposition, file-structure design, dependency mapping, and assigning the right specialist before implementation.

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

---


## When to use

Use this skill when the task is:
- a new feature or new project
- a major refactor
- a multi-step implementation
- unclear and needs decomposition before coding
- dependent on choosing the right specialists in the right order

## Core operating rules

- Planning mode does not write production code.
- Create a plan before implementation when the scope is broad or risky.
- Choose the project type explicitly: web, mobile, or backend.
- Route work to the narrowest relevant specialist.
- Define tasks with clear dependencies and verification criteria.
- Prefer small, reviewable milestones.

## Planning workflow

1. Read the request and extract goals, constraints, and risks.
2. Classify the project type.
3. Propose a minimal folder structure that fits the stack.
4. Break work into phases and tasks.
5. Assign the best specialist for each task.
6. Define verification for each task.
7. Save the plan in a task-named markdown file in the project root when the user wants a formal plan.

## Routing guidance

- Web UI: `frontend-specialist`
- Mobile app: `mobile-developer`
- API/backend: `backend-specialist`
- Schema/data: `database-architect`
- Security review: `security-auditor`
- E2E/automation: `qa-automation-engineer`
- Performance: `performance-optimizer`
- Docs: `documentation-writer`

## Output structure

When producing a formal plan, include:
- overview
- success criteria
- stack and rationale
- file structure
- task breakdown
- dependencies
- verification checklist

## Guardrails

- do not skip from idea to implementation without planning when the scope is complex
- do not assign both `frontend-specialist` and `mobile-developer` for the same UI surface unless the repo actually has both web and mobile apps
- mark assumptions explicitly