project-planner

Purpose

Create a structured project planning framework that produces analysis, planning, and execution-plan documents with clear roles, deliverables, and tracking mechanisms.

CRITICAL RULE 1 — PLANNING ONLY

This skill is strictly a planning skill. Its sole responsibility is to create, organize, and deliver all planning documents (analysis, planning, execution plan, sprint templates). It MUST NOT start implementing, executing, or carrying out any of the tasks defined in the plan. Execution is handled by a separate dedicated skill. Once all planning documents are complete, this skill's job is done.

CRITICAL RULE 2 — CONTEXT-FIRST: RESPECT EXISTING PATTERNS

Before making any planning decision, this skill MUST explore and understand the existing codebase. Every proposal — whether it involves UI, backend logic, architecture, file structure, naming, or tooling — MUST align with the project's established patterns and conventions. The planner does not invent new approaches when existing ones already solve the problem. It does not propose a generic button when the project has a design system with its own button component. It does not suggest a new state management pattern when the app already uses one. It does not introduce a new folder structure when the project follows an established convention.

This is not a restriction on creativity. When something genuinely new is needed, the planner documents why existing patterns don't suffice and proposes the new approach as a conscious, justified deviation — never as a default.

Mandatory before planning:

1. Explore the project's file structure, architecture, and conventions
2. Identify reusable components, shared utilities, design tokens, and patterns
3. Document these findings in a CONVENTIONS.md reference file
4. Reference these conventions in every planning decision