planning

Enforce a five-round planning process before PRD creation.

1|Updated Jan 26, 2026

Search Tags:#planning #requirements #discovery #PRD #stakeholders #planning-session

Ready to run

npx skills add https://github.com/harrymunro/ralph-wiggum --skill planning-harrymunro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/harrymunro/ralph-wiggum/tree/main/skills/planning
Command: npx skills add https://github.com/harrymunro/ralph-wiggum --skill planning-harrymunro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a structured, five-round planning process to uncover and document requirements before creating a PRD, reducing rework and scope creep.

Core Features & Use Cases

5-round discovery: conducts five mandatory question rounds to capture problem, scope, and success criteria.
Planning summary: compiles answers into a concise planning document saved at tasks/planning-[feature].md.
PRD gating: ensures no PRD creation until planning is complete and validated.
Guided progression: after each round, prompts the user to continue or provide the next question.

Quick Start

Activate the Planning Skill and begin the first round of problem understanding with the user.

Frequently Asked Questions about planning

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

FAQPage Schema

What is a structured planning session for product requirements discovery?▼

A structured planning session for product requirements discovery enforces a five-round question process to capture problem scope and success criteria before creating a PRD.

How do I run a planning session to gather requirements before writing a PRD?▼

To run a planning session for a PRD, activate the skill to begin five mandatory question rounds, answering prompts sequentially to document problem understanding and validate scope.

Can I generate a PRD without completing the full requirements discovery process?▼

No, you cannot generate a PRD without completing requirements discovery, because a mandatory gating step blocks PRD creation until the five-round planning process is fully validated.

Does the planning process save documented answers and requirements outcomes?▼

Yes, the planning process saves documented answers and outcomes by compiling them into a concise planning summary file stored locally for future reference.

What is the best way to prevent scope creep during feature discovery?▼

The best way to prevent scope creep during feature discovery is enforcing a structured five-round planning process that validates problem scope and success criteria before PRD creation.

When should I use a formal planning session for product management?▼

You should use a formal planning session for product management when you need to uncover and document requirements for feature discovery and scoping to reduce rework before PRD generation.