project-planner

Project planning documentation converts vague ideas into clear, actionable specs. This Skill takes your brief concept and produces two structured documents: a high-level PROJECT-OVERVIEW.md with vision and goals, and a SPECIFICATIONS.md with detailed technical requirements, enabling engineers and stakeholders to align immediately.

Technical requirements documentation captures architecture, dependencies, and implementation details needed by engineers. The Skill generates specifications covering feature definitions, constraints, and technical scope, ensuring your team has concrete requirements to build from rather than ambiguous briefs.

Create project documentation at project initiation when translating ideas into actionable plans. This process is essential before development begins to establish shared vision, success metrics, and technical scope across teams, preventing misalignment and rework.

Yes. Structured project documentation serves as a single source of truth for both technical teams and stakeholders. By producing clear overviews alongside detailed specifications, the Skill enables unified understanding of vision, goals, and implementation requirements across all parties.

Project-level documentation should separate high-level vision and success metrics from technical details. The Skill structures this by generating a dedicated overview document for strategic context and goals, paired with specifications for technical depth, so stakeholders and engineers each find relevant information quickly.

Specifications should capture enough technical detail for implementation without prescribing every decision. The Skill produces requirement-focused specs that define scope, constraints, and dependencies while leaving room for engineering judgment, balancing clarity with flexibility.