| title | Codex walkthrough |
|---|---|
| folder | docs/cross-tool |
| description | How to use Specorator with Codex while preserving worktrees, artifacts, and verification. |
- Read
AGENTS.md,.codex/instructions.md, andmemory/constitution.md. - For a new feature, create or update
specs/<feature>/workflow-state.md, then draftidea.md,research.md, andrequirements.mdin order. - Ask Codex to stop and surface clarifications when intent, requirements, or acceptance criteria are missing.
Use role names from .claude/agents/ as explicit instructions: "act as analyst for Stage 1", "act as pm for requirements", or "act as reviewer for this PR". Codex should follow the role scope even though it does not launch Claude subagents.
For recurring practices, point Codex at the matching .claude/skills/<name>/SKILL.md file. For architecture improvement, include .claude/skills/improve-codebase-architecture/SKILL.md and ask Codex to present deepening opportunities before editing code.
Write feature work under specs/<feature>/. Keep task IDs, requirement IDs, tests, ADRs, and workflow-state status synchronized.
For non-trivial changes, create a worktree under .worktrees/<slug>, run npm run verify, commit, push, and open a PR. Use .codex/workflows/pr-delivery.md for the delivery loop.