Plan Writer

Activation

1. •Activate during workflow planning phases.
2. •Activate on explicit $codex-plan-writer.
3. •Mandatory for complex requests with scope medium or large.

Output File Naming

• •Derive a short kebab-case slug from the task intent (2-3 keywords).
• •Maximum 30 characters.
• •Examples: ecommerce-cart.md, login-fix.md, dark-mode.md.

Output Location

Write plan file to project root: ./{task-slug}.md

Required Plan Structure

1. Overview

• •what is being built or changed
• •why it matters

2. Success Criteria

• •measurable "done" conditions

3. Tech Stack (if relevant)

• •selected technologies and rationale

4. Task Breakdown

For each task include:

• •task name and id
• •domain (frontend | backend | mobile | debug)
• •priority (P0 | P1 | P2 | P3)
• •dependencies
• •input
• •output
• •verify method
• •rollback strategy

5. Phase X Verification Checklist

• •lint passes
• •tests pass
• •security scan reviewed
• •all tasks completed

Rules

• •Do not include implementation code in plan files.
• •Keep tasks small and verifiable.
• •Explain why each task exists, not only what to do.

Exit Gate

Plan writing is complete only when:

1. •plan file exists at ./{task-slug}.md
2. •all required sections exist
3. •user has reviewed and approved the plan