project-plan-formulation

Automate creation of a structured PROJECT_PLAN.md through collaborative interviews.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dczmer/skill-issues --skill project-plan-formulation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-plan-formulation
Source: https://github.com/dczmer/skill-issues/tree/main/skills/project-plan-formulation
Command: npx skills add https://github.com/dczmer/skill-issues --skill project-plan-formulation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the creation of a structured PROJECT_PLAN.md by guiding a collaborative interview process.

Core Features & Use Cases

  • Conducts iterative interviews to gather overview, tech stack, architecture, development process, conventions, and security considerations.
  • Supports section targeting, supplemental context, and gated approvals to merge inputs into a cohesive plan.
  • Provides built-in error handling, cross-section consistency validation references, and a final assembly step to produce a versioned document.

Quick Start

Invoke with /project-plan-formulation to start an interactive interview that builds your PROJECT_PLAN.md

Frequently Asked Questions about project-plan-formulation

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

FAQPage Schema
How do I create a structured project plan document for software architecture?

Generate a project plan document through a collaborative interview that collects your tech stack and architecture details. The process merges inputs into a versioned PROJECT_PLAN.md, applying cross-section consistency checks to ensure your software architecture planning is cohesive.

What is an interactive interview process for project management planning?

An interactive interview for project management planning systematically gathers development conventions and security considerations through targeted questions. It uses gated approvals to validate each section, ensuring your final document reflects consistent and comprehensive team inputs.

Can I generate specific sections of a project plan instead of the whole document?

Yes, you can generate specific sections of a project plan using section targeting. This allows you to focus the interview on individual areas like development process or security considerations, supplementing them with additional context before merging into the final document.

How do you ensure consistency across different sections of a project plan?

Ensure consistency across project plan sections through built-in cross-section consistency validation. This mechanism checks for alignment between your tech stack, architecture, and development process inputs during gated approval steps, preventing contradictions before final document assembly.

What is the best way to document team conventions and security considerations in a project plan?

Document team conventions and security considerations by conducting an iterative interview that captures these specific inputs. The process integrates them into a versioned PROJECT_PLAN.md, applying consistency validation to ensure your conventions align with the overall architecture and process documentation.