heavy-planner

Guide requirement analysis through iterative questions to produce structured project plans.

40|9|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/clasen/Skills --skill heavy-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: heavy-planner
Source: https://github.com/clasen/Skills/tree/main/heavy-planner
Command: npx skills add https://github.com/clasen/Skills --skill heavy-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ambiguous project requirements by prompting thorough discovery and clarification before developing a plan.

Core Features & Use Cases

  • Requirement Discovery: Guides users through detailed questions to clarify goals, scope, constraints, and risks.
  • Operational Interrogation: Employs systematic questioning to surface assumptions, edge cases, and dependencies.
  • Structured Specification: Produces a comprehensive, testable project plan once all uncertainties are resolved.
  • Use Case: When initiating a new product development process, use this Skill to meticulously define objectives, constraints, and scenarios to ensure successful execution.

Quick Start

Ask the AI "What do you want to build?" and follow its detailed interrogation until all core questions are satisfactorily answered before requesting a development plan.

Frequently Asked Questions about heavy-planner

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

FAQPage Schema
How do I clarify ambiguous project requirements before creating a specification?

Clarify ambiguous project requirements by using systematic interrogation to surface scope, constraints, assumptions, and risks. This ensures all uncertainties are resolved through detailed, iterative questioning before a structured plan is produced.

What is the best way to conduct requirement discovery for a new product development process?

Conduct requirement discovery for new product development by guiding users through detailed questions to meticulously define objectives, constraints, and scenarios. This operational interrogation surfaces edge cases and dependencies to ensure successful execution.

Does this requirement interrogation approach work for complex project planning?

Yes, this requirement interrogation approach works for complex project planning by systematically gathering scope and risks to produce testable specifications. It ensures all ambiguities are resolved for precise and actionable project plans.

When should I use systematic questioning instead of directly writing a project plan?

Use systematic questioning instead of directly writing a project plan when initiating complex projects with unclear goals. Prompting thorough discovery and clarification first prevents ambiguities from undermining the final structured specification.