Summary of key patterns for Codex conversation-based development centered on Markdown specs
SITE_SPEC.md # purpose, users, done checklist USER_FLOWS.md # step-by-step paths for students & teachers DATA_MODEL.md # name, check-in time, status data structure IMPLEMENTATION_PLAN.md # build order and test items CONVERSATION.md # conversation prompts and decision history
"Read the 5 planning docs above carefully, and under the website/ folder build 1) the student check-in card selection and QR generation screen 2) the teacher's real-time attendance monitoring screen in HTML/CSS/JS. Include mobile layout and exception handling."
After writing docs with Codex, review them with gstack skills. Don't accept the results as-is; put only what the team decided into the docs and record it in CONVERSATION.md.
/office-hours → PROJECT_BRIEF.md check problem·user·scope (before planning)
/plan-ceo-review → SITE_SPEC.md check scope (Hold Scope / Reduction mode)
/plan-eng-review → USER_FLOWS.md exception flows · hidden assumptions
DATA_MODEL.md data flow · fields · relationships
IMPLEMENTATION_PLAN.md build order · test plan
/autoplan (optional) → run the reviews above at once, list only items a person must decide
/document-release → after building, update docs to match the final code
(summary of all results) → CONVERSATION.md
"/plan-eng-review Review the 5 planning docs and list in a table the contradictions between docs, missing handling of studentId·QR expiry·duplicate check-in, and a test plan for each requirement ID."