What problem does it solve? Starting a new web application or major feature without a structured plan leads to scope creep, oversized work chunks, and lost context between sessions. This Skill turns a project description into context-safe implementation phases with verification criteria, so work can be built iteratively and resumed cleanly. ## Core Features & Use Cases - Phased Implementation Plans: Generates IMPLEMENTATION_PHASES.md with typed phases (Infrastructure, Database, API, UI, Integration, Testing), each limited to 5-8 files with task checklists, verification criteria, and exit criteria. - Supporting Planning Documents: Produces DATABASE_SCHEMA.md, API_ENDPOINTS.md, ARCHITECTURE.md, UI_COMPONENTS.md, TESTING.md, AGENTS_CONFIG.md, and INTEGRATION.md when project complexity warrants them. - Phase Validation: Automatically flags oversized phases and suggests splits when file counts, dependencies, or duration exceed context-safe limits. - Use Case: Describe a URL shortener with user accounts and analytics; the Skill asks targeted questions about auth, data model, and scope, then outputs a six-phase plan plus database schema and API endpoint documentation. ## Quick Start Ask the assistant to use the project-planning skill to structure your new web app idea into implementation phases.