Plan

Purpose

Turn a prompt into a concise, high-quality spec without writing any code.

Input handling

• •Treat the input as a prompt describing the desired change or feature.
• •If the prompt references existing plans or docs, read them first.

Planning mode (no implementation)

• •Do NOT write or modify production code.
• •Do NOT run refactors or tests.
• •Focus purely on requirements, design, and verification steps.

Planning workflow

1. •Read repo guidance

• •Read AGENTS.md and ~/.codex/docs/style-guide.md.
• •If docs/overview.md exists, read it.

1. •Clarify scope

• •Identify assumptions, constraints, and open questions.
• •If critical details are missing, list the exact questions needed.
• •Aggressively clarify relevant ambiguities with the user until the plan is clear and high quality.
• •Confirm the prompt is verifiable: there must be a concrete success signal (tests to write, or a UI behavior that can be driven/checked via MCP Chrome DevTools).

1. •Produce the spec

• •Create a terse but complete spec with:
  • •Objective (1 sentence)
  • •Requirements (bulleted)
  • •Non-goals (bulleted)
  • •Architecture/approach (bulleted)
  • •Data changes/migrations (if any)
  • •Testing strategy (bulleted)
  • •Rollout/validation steps (bulleted)
  • •Risks and mitigations (bulleted)

1. •Write spec file

• •Save to factory/spec-<very-brief-description>.md in the repo root.
• •Use a short, lowercase, dash-separated description (3-6 words max).

1. •Update shared context

• •Append a one-line summary and the spec path to factory/context.md.

Output format

• •One-line summary with spec filename.
• •List any open questions.