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.
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:
plan.md
slices.json
Both must be emitted together.
Input
A short prompt describing desired outcome.
Optional constraints (tech stack, deadlines, forbidden dependencies).
Required Output Behavior
Always output a complete
plan.md
using required headings.
Always output a complete
slices.json
matching schema v1.
Every slice must include acceptance criteria and validation commands.
Slice IDs in
slices.json
must be referenced in
plan.md
.
generatedBy
must begin with
ralphd-plan@
.
Initial slice status must default to
pending
.
Required
plan.md
Headings
slices.json Status Enum pending in_progress passed failed blocked Emission Format Emit exactly two fenced blocks in this order: plan.md slices.json Example:
...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.