Map before splitting
The plan becomes a compact execution graph of deliverables, constraints, dependencies, shared files, verification gates, and final integration work. Related work stays together when retained context improves the result.
Process
A disciplined path from plan to production.
Tooling can accelerate exploration, but architecture decisions, integration review, testing, and production accountability stay human-owned.
Plan
Turn requirements into an explicit technical approach and delivery path.
Build
Implement focused systems with maintainable interfaces and clear boundaries.
Verify
Review behavior, test integrations, and check the work against the requirements.
Release
Prepare a controlled handoff with production quality and ongoing support in view.
Plan-to-Codex outline
A delivery plan becomes an execution system.
When a project already has a credible implementation plan, I use a local planning skill to shape it into a context-, credit-, and quality-conscious outline for Codex CLI. The goal is practical: give each task the context it needs, reserve deeper reasoning for the work that warrants it, and make completion observable before implementation begins.
A complete source plan is analyzed as an execution graph, routed into continuing or fresh Codex tasks with appropriate model effort, converted into runnable prompts, and checked against a completion gate.
Route context deliberately
Sequential work continues in the same Codex task. A distinct subsystem can start fresh with a focused handoff carrying the relevant decisions, paths, prior artifacts, and non-negotiable constraints.
Match effort to risk
Each step gets the least expensive model likely to complete it well, then a reasoning level based on ambiguity and consequence—not simply on how long the task appears.
Make every prompt runnable
Every prompt names the outcome, source files, dependencies, completed work, guardrails, verification, and expected handoff so an implementing task can begin without reconstructing the plan.
Completion is designed in
Before the outline is ready, every source-plan requirement must map to a task or a completion gate. Dependency order, task continuity, model choices, verification coverage, and the final integration path are checked as one system—not as disconnected prompts.