preplan

Solid

Use when a problem needs clarification and agreement before planning begins. Supports --deep and --delegate.

AI & Automation 11 stars 2 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Pre-plan Structured problem-definition conversation with the user before planning begins. ## Argument Routing | Argument | Mode | | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | `<prompt>` | Self-execute on current host (default) | | `--deep` | Enable pioneer review for elegant alternatives | | `--delegate` | Delegate pioneer to the other host (Codex when current is Claude, Claude when current is Codex; from SessionStart `Current host:`). Activates `--deep`. | Strip `--deep` and `--delegate` flags before passing the prompt to the execution path. <Preplan_Protocol> <Role> You are the **Problem Definer**: gather context, fill a structured agreement, refine through conversation, propose transition to planning. Not responsible for: plans (plan), implementation (ralph), architecture (architect). NEVER implement. NEVER write source code. Problem definition only. </Role> <Structure> The agreement consists of 7 items. Fill autonomously where possible, mark uncertain items with the "unco...

Details

Author
kangig94
Repository
kangig94/coral
Created
5 months ago
Last Updated
yesterday
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

plan

Use when a task needs structured planning before implementation. Supports --delegate and round=N.

11 Updated yesterday
kangig94
AI & Automation Featured

plan

Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request doesn't need, then STOPS at a build-location gate (build here, hand off to another session, or just keep the plan). Plan never implements. Trigger with /hyperflow:plan, "design this", "plan this", "decompose this", "how should we", "what's the best way to", "break this down", "enhance this prompt".

2,560 Updated today
jeremylongshore
AI & Automation Solid

plan-create

Propose a phased, gated implementation plan before any work begins. Trigger when the user runs /plan-create, says "make a plan", "plan this out", "design before coding", "let's plan first", "architect this", or asks for a phased approach before implementation. Also trigger proactively when a task is complex enough that jumping straight to execution would be risky — multi-file changes, new features, architectural shifts, refactors spanning multiple components, or any task where misalignment early would be expensive to fix later. Output: a structured PLAN.md with phases, changes, risks, and verification criteria. Design only — no implementation code is written during /plan-create. Use plan-phases to restructure an existing plan, plan-execute to run an approved plan, plan-deep-dive to inspect a plan, plan-evolve to evolve shipped work, and plan-cleanup after execution.

0 Updated today
allemaar