codex2paper structures your repo so AI coding agents can:
- plan before execution
- iterate with phase boundaries
- integrate external critique
- keep decisions traceable
It is designed to work with CLI agents like Claude Code and OpenAI Codex.
Agent workflows break down when:
- planning is implicit (no durable artifact)
- context is scattered across prompts
- feedback is unstructured
- iteration loops drift
In practice, strong workflows converge on:
markdown files as the source of truth (Medium)
codex2paper formalizes that structure.
All work happens through a staged loop:
- Converge
- Validate
- Experiment
- Method
- Writing
Each phase has:
- a dedicated markdown file
- an explicit gate
- a clear output
The agent reads, edits, and advances these files.
git clone <repo>
cd codex2paperThen in Claude Code / Codex:
Read control.md and summarize current phase.
Propose next actions based on queue.md.
Typical loop:
- Ask agent to update
direction.md - Generate a plan (Plan Mode / markdown)
- Send for external critique
- Write back into
reviews.md - Advance phase in
control.md
control.md— current phase + next actionqueue.md— active tasksdirection.md— problem framingbaselines.md— validationreviews.md— external critique + decisionsweekly_review.md— decision logskills/— agent-facing workflowsEXAMPLE_ROUND.md— full loop example
Claude Code already supports:
- planning before execution (Plan Mode)
- markdown-driven context (
CLAUDE.md, etc.) - subagents and structured workflows (Claude)
codex2paper adds:
- persistent phase structure
- cross-iteration memory
- explicit research gates
- no automation
- no experiment runner
- no agent orchestration layer
- no mcp
This repo only defines structure + conventions.
Lightweight pattern. Works best for:
- iterative research
- paper-oriented projects
- agent-assisted exploration
See ACKNOWLEDGEMENTS.md.
