ck:plan-json

ck:plan-json — Phased JSON Planning

Every mode always creates plans/{slug}/plan.json and one or more phase JSON files. The master stays compact so an AI executor loads step detail only for the active phase.

No legacy or single-file format compatibility is supported.

---

Step 0 — Load Input

Resolve the primary requirement input in this order:

1. --spec <path> — preferred: load the supplied spec.md.
2. If no spec is supplied, use the inline feature description or requirement text.
3. If neither exists, ask for a description or spec path.

Also accept:

• --project {slug} — project ID; default is the current directory name.
• --mode {fast|hard} — override automatic scope detection.
• --output <path> — master entry point; default is plans/{slug}/plan.json. Phase files are siblings beside this master.

---

Step 1 — Analyze Scope and Phases

Report:

Scope:
  Phases: {N}
  Files: {N total, N new, N modify}
  Complexity: {Fast | Hard}

• Fast — one small component and at most three affected files. Fast creates exactly one phase JSON file.
• Hard — two or more phases, at least four files, multiple components, or external integrations.

If Hard has no spec, suggest /ck:brainstorm before continuing.

Decompose work into ordered, dependency-aware phases. Use deterministic kebab-case names and phase-{phase_id:02d}-{name}.json filenames. Maximum 15 steps per phase; add another phase when more steps are needed.

---

Step 2 — Generate Phase Files First

Phase files contain and own detailed steps. Write every complete phase file first, before the master exists or is updated.

Each phase file uses this structure:

{
  "plan_id": "{slug}",
  "phase_id": 1,
  "name": "setup-project",
  "goal": "Initialize the project",
  "status": "pending",
  "current_step": 1,
  "design_constraints": [
    "Cook confirms unit-test and quality-gate choices before each phase"
  ],
  "quality_profile": {
    "repository_conventions": {},
    "boundaries": {},
    "applicable_rules": [],
    "allowed_exceptions": []
  },
  "quality": { "status": "not_evaluated", "report": "", "receipt": "", "remediation_cycles": 0 },
  "testing": { "status": "not_started", "report": "" },
  "steps": [
    {
      "step_id": 1,
      "description": "Create the project structure",
      "status": "pending",
      "input_files": [],
      "output_files": ["src/README.md"],
      "ai_generated_code": "",
      "debug_logs": [],
      "success_criteria": ["The expected file exists"]
    }
  ]
}