ralphd-plan

name	ralphd-plan
description	Converts a simple product prompt into strict ralphd planning artifacts (`plan.md` and `slices.json`) with enforceable slice acceptance and validation contracts. Use when preparing or adapting a ralphd run plan.
references	["references/output-contract.md","references/templates/plan-template.md","references/templates/slices-template.json"]

ralphd-plan

Purpose

Generate two artifacts that satisfy ralphd contract checks:

1. plan.md
2. slices.json

Both must be emitted together.

Input

• A short prompt describing desired outcome.
• Optional constraints (tech stack, deadlines, forbidden dependencies).

Required Output Behavior

1. Always output a complete plan.md using required headings.
2. Always output a complete slices.json matching schema v1.
3. Every slice must include acceptance criteria and validation commands.
4. Slice IDs in slices.json must be referenced in plan.md.
5. generatedBy must begin with ralphd-plan@.
6. Initial slice status must default to pending.

Required plan.md Headings

• # Plan
• ## Outcome
• ## Constraints
• ## Slice Index
• ## Acceptance Criteria
• ## Adaptation Policy

slices.json Status Enum

• pending
• in_progress
• passed
• failed
• blocked

Emission Format

Emit exactly two fenced blocks in this order:

1. plan.md
2. slices.json

Example:

<!-- plan.md -->
...content...

// slices.json
{ ... }

Must Not Do

• Do not omit either artifact.
• Do not invent extra top-level keys in slices.json.
• Do not output ambiguous acceptance like "works".
• Do not use placeholder validation commands.