project-planner

Generate a structured PROJECT_PLAN.md through iterative questioning and decision tracking.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cncorp/arsenal --skill project-planner-cncorp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-planner
Source: https://github.com/cncorp/arsenal/tree/main/dot-claude/skills/project-planner
Command: npx skills add https://github.com/cncorp/arsenal --skill project-planner-cncorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you create a comprehensive project specification through an iterative question-and-answer process, tracking decisions in a Markdown planning document.

Core Features & Use Cases

  • Planning doc generation: creates docs/specs/<project>/PROJECT_PLAN.md.
  • Iterative questions: guides you to answer key questions until a complete spec is formed.
  • Decision tracking: captures decisions and open questions in a structured format.

Quick Start

Start by describing your project idea. The skill will create the planning directory and PROJECT_PLAN.md, then guide you through questions and decisions until the spec is complete.

Frequently Asked Questions about project-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured project plan from an unstructured idea?

Project planning transforms rough ideas into structured specifications through iterative questioning. This Skill automates that process by guiding you through key decisions, capturing requirements, and building a living PROJECT_PLAN.md document that evolves as you answer each question.

What gets included in the project planning document?

The PROJECT_PLAN.md captures decisions made, open and closed questions, technical sections, and an implementation roadmap. The document updates iteratively as you provide answers, creating a comprehensive spec that tracks your project's evolution and scope.

Can I use iterative planning for scope and requirements elicitation?

Yes. Iterative Q&A planning is designed for scope definition, requirements gathering, and decision tracking. By answering guided questions progressively, you build a complete specification that captures functional and technical requirements without ad-hoc planning chaos.

How does the Skill know what questions to ask next?

The Skill uses your answers to identify gaps in scope, requirements, and decisions, then prompts targeted follow-up questions. This guided approach ensures your spec becomes complete incrementally, with each answer informing the next question until planning is finalized.

What format does the planning output use?

Planning output is structured as Markdown in docs/specs/<project>/PROJECT_PLAN.md. Markdown format makes the spec readable, version-controllable, and easy to share or integrate into documentation systems while maintaining a clean, organized structure.