project-planning

Name: project-planning
Availability: InStock
Author: pavel-molyanov

Conduct adaptive interviews to generate project documentation and technical decisions.

244|75|Updated Dec 22, 2025

Search Tags:#architecture #documentation #deployment #tech stack #project planning #scrum

Ready to run

npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill project-planning-pavel-molyanov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-planning
Source: https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/project-planning
Command: npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill project-planning-pavel-molyanov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the initial project setup by conducting an adaptive interview to define project scope, make technical decisions, and automatically generate comprehensive project documentation.

Core Features & Use Cases

Adaptive Interview: Gathers project details through a dynamic, question-by-question conversation.
Technical Decision Making: Proposes and confirms tech stacks, deployment strategies, and project architecture.
Automated Documentation: Fills out essential project documents like project.md, architecture.md, patterns.md, and deployment.md.
Use Case: When starting a new software project, use this Skill to guide you through defining the project's purpose, target audience, key features, technology choices, and deployment plan, ensuring all foundational documentation is created in one go.

Quick Start

Initiate project planning by describing your new project.

Frequently Asked Questions about project-planning

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

FAQPage Schema

How do I create comprehensive project documentation for a new software project?▼

You can create project documentation through an adaptive interview process that gathers details on project scope, features, and deployment, automatically generating essential files like project.md, architecture.md, patterns.md, and deployment.md.

What is the best way to define MVP scope and tech stack during initial project setup?▼

Defining MVP scope and tech stack is handled through a dynamic, question-by-question conversation that proposes and confirms technical decisions, ensuring your project architecture and feature scope are documented accurately and consistently.

Can I use an automated interview to select a deployment strategy and document architecture?▼

Yes, an adaptive interview guides you through selecting a deployment strategy and technical stack, automatically populating your architecture.md and deployment.md files with the confirmed technical decisions.

How does the project planning process work for generating foundational knowledge files?▼

The project planning process works by conducting a question-by-question interview to define the project's purpose, target audience, and key features, resulting in all foundational project knowledge files being populated in one go.

Do I need any specific tools or dependencies to start planning my project architecture?▼

No specific dependencies are required to start planning your project architecture; you simply initiate the process by describing your new software project to the adaptive interview system.

What limitations are there when defining technical decisions for project planning?▼

The project planning process focuses on initial setup and technical decision making for software projects, meaning it is designed for generating foundational documentation rather than managing ongoing development or execution tasks.