What files does the Project Planner skill generate?

The skill generates two primary documents inside a 'project-management/' directory: PROJECT-OVERVIEW.md, which covers vision and goals, and SPECIFICATIONS.md, which details technical requirements.

Does this skill write the actual application code?

No, the Project Planner focuses exclusively on the planning phase. It creates the structural foundation and technical blueprints that a coder agent or developer uses to build the application.

Can I customize the level of detail in the generated plans?

Yes, you can use configuration flags like LAZYDEV_PROJECT_SPEC_MINIMAL for faster results or focus the skill on specific areas like security and performance using environment variables.

When is the best time to trigger the Project Planner?

It is best used at the very beginning of a project or whenever you are introducing a major new feature set that requires architectural planning and technical specifications.

Project Planner

Name: Project Planner
Author: MacroMan5

byMacroMan5

•

Productivity & Workflow

Transforms high-level project ideas into comprehensive, structured technical documentation including vision, specifications, and API contracts.

About

The Project Planner skill for Claude Code acts as an automated solution architect, converting vague project concepts into professional-grade documentation. It automatically generates two primary files—PROJECT-OVERVIEW.md for high-level vision and goals, and SPECIFICATIONS.md for deep technical requirements—ensuring every new project starts with a clear, actionable roadmap. By formalizing features, data models, system architecture, and API contracts, it provides a consistent foundation for developers and AI agents to follow throughout the implementation lifecycle.

Key Features

Context-aware extraction of project goals, vision, and success criteria
Detailed non-functional requirements covering security, scalability, and performance
Structured templates for API contracts, data models, and system architecture
2 GitHub stars
Automated generation of PROJECT-OVERVIEW.md and SPECIFICATIONS.md
Multi-phase development roadmapping and comprehensive testing strategy outlines

Use Cases

Creating formal technical documentation and system designs for stakeholder review
Defining API contracts and database schemas before beginning implementation
Starting a new software project from a brief description or rough idea

About

Key Features

Context-aware extraction of project goals, vision, and success criteria
Detailed non-functional requirements covering security, scalability, and performance
Structured templates for API contracts, data models, and system architecture
2 GitHub stars
Automated generation of PROJECT-OVERVIEW.md and SPECIFICATIONS.md
Multi-phase development roadmapping and comprehensive testing strategy outlines

Use Cases

Creating formal technical documentation and system designs for stakeholder review
Defining API contracts and database schemas before beginning implementation
Starting a new software project from a brief description or rough idea