planning

Decompose product requirements and MVP capabilities into a structured planning document.

Updated Apr 12, 2026

Search Tags:#planning #requirements #strategy #mvp #risk management #sequencing

Ready to run

npx skills add https://github.com/olivermorgan2/workflow-generator --skill planning-olivermorgan2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/olivermorgan2/workflow-generator/tree/main/skills/planning
Command: npx skills add https://github.com/olivermorgan2/workflow-generator --skill planning-olivermorgan2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves ambiguity in large projects by decomposing high-level product goals into concrete requirements, surfacing hidden risks, and establishing a clear, justified sequencing rationale before architectural decisions are finalized.

Core Features & Use Cases

Requirements Decomposition: Breaks down MVP capabilities into traceable, numbered requirements.
Risk & Assumption Mapping: Identifies potential delivery blockers and project dependencies with clear mitigation strategies.
Sequencing Justification: Provides a logical narrative for phase ordering, ensuring the build-out plan is defensible and well-structured.

Quick Start

Run the planning skill to generate a comprehensive design planning document based on your existing product requirements and MVP definitions.

Frequently Asked Questions about planning

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

FAQPage Schema

How do I break down MVP capabilities into traceable requirements?▼

To break down MVP capabilities into traceable requirements, decompose high-level product goals into structured, numbered items. This process hardens project scope by surfacing hidden risks and mapping assumptions before finalizing architectural decisions.

What is the best way to map project risks and assumptions during initialization?▼

Mapping project risks during initialization involves identifying potential delivery blockers and dependencies alongside your product requirements. This establishes clear mitigation strategies and ensures architectural clarity before technical implementation begins.

How do I justify phase sequencing for a complex product roadmap?▼

Justifying phase sequencing requires providing a logical narrative for phase ordering based on decomposed product requirements. This ensures your development roadmap remains defensible and well-structured prior to committing to architectural decisions.

When do I need to decompose product requirements into a structured planning document?▼

Decomposing product requirements into a structured planning document is needed during complex project initialization phases. It resolves ambiguity by establishing traceable requirements and justified development roadmaps before technical implementation starts.

Can I use automated template rendering to harden project scope before architecture is finalized?▼

Yes, you can harden project scope before architecture is finalized using automated template rendering. This generates a comprehensive design planning document that surfaces hidden risks and establishes clear sequencing rationale for your MVP.

What are the limitations of using requirements decomposition for project initialization?▼

Requirements decomposition is limited if applied outside complex project initialization phases. It requires existing MVP definitions and product goals to function, as it cannot generate foundational architectural clarity without established prerequisite inputs.