FESADev/plugins/fesa-commands/commands/phase-draft.md

description

description
Draft Harness phase and step files for FESA implementation planning.

/phase-draft

Preflight

• Read /AGENTS.md, /PROGRESS.md, /PLAN.md, /docs/README.md, /docs/HARNESS_ENGINEERING.md, and all Phase 1 design docs.
• Use $fesa-readiness first.
• Use $fesa-phase-planning and the repo harness-workflow skill when file generation is requested.
• Do not spawn subagents unless the user explicitly asks for delegated work.

Task

• Identify readiness blockers before drafting steps.
• Keep each phase step self-contained for a fresh Codex session.
• Include a sprint contract: objective, required reading, scope, allowed files, explicit non-goals, tests to write first, reference artifacts, acceptance commands, evaluator checklist, and handoff requirements.
• Do not hide unresolved formulation or reference decisions inside broad implementation steps.

Verification

• Parse generated JSON phase files.
• Re-read generated stepN.md files for self-containment.
• Run python scripts/validate_workspace.py.

Result

• Action: drafted phase files
• Status: success | partial | blocked
• Details: phase directory, step count, blockers, and validation result