lsantosweb 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
- Read the request and extract goals, constraints, and risks.
- Classify the project type.
- Propose a minimal folder structure that fits the stack.
- Break work into phases and tasks.
- Assign the best specialist for each task.
- Define verification for each task.
- 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-specialistandmobile-developerfor the same UI surface unless the repo actually has both web and mobile apps - mark assumptions explicitly