preplan

Draft a seven-item problem-definition agreement before planning handoff.

11|3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/kangig94/coral --skill preplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preplan
Source: https://github.com/kangig94/coral/tree/main/skills/preplan
Command: npx skills add https://github.com/kangig94/coral --skill preplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves misalignment by conducting a structured problem-definition conversation before planning.

Core Features & Use Cases

  • Autonomous drafting of a seven-item agreement capturing Problem Statement, Success Criteria, Scope, Assumptions, Affected Systems, Constraints, and Approach Direction, with uncertainty markers.
  • Creates a draft at .claude/coral/plans/pre-{topic}.md and supports iterative corrections through a guided conversation.
  • Ideal for complex initiatives where early clarity is critical, such as multi-team feature launches, risk assessments, and large planning efforts.

Quick Start

Provide a topic to begin the preplan.

Frequently Asked Questions about preplan

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

FAQPage Schema
How do I get stakeholder agreement on problem definition before starting complex planning?

To secure stakeholder agreement before complex planning, initiate a structured problem-definition conversation that drafts a formal agreement capturing Problem Statement, Success Criteria, Scope, Assumptions, Affected Systems, Constraints, and Approach Direction.

What is the best way to document project scope and constraints across multiple teams?

Documenting project scope and constraints across multiple teams is best achieved by autonomously drafting a seven-item agreement file that flags uncertainties, ensuring all affected systems and assumptions are explicitly recorded for iterative correction.

How do I prepare a pre-planning agreement for a multi-team feature launch?

Prepare a pre-planning agreement by providing a topic to start a guided conversation, which drafts a structured markdown file capturing success criteria, constraints, and approach direction to align stakeholders before the feature launch.

Can I iteratively correct assumptions and scope during problem definition?

Yes, you can iteratively correct assumptions and scope during problem definition through a guided conversation that updates the draft agreement, allowing stakeholders to refine constraints and flag uncertainties continuously.

When do I need a structured problem definition workflow for requirements gathering?

A structured problem definition workflow is needed for complex initiatives like multi-team feature launches and large planning efforts, where early clarity on problem scope, success criteria, and constraints across stakeholders is essential.