| name | source-command-do-feature |
| description | Converted Codex workflow from Claude slash command `do-feature`. Use when the user asks to run the equivalent command or describes this workflow. |
Command Workflow: do-feature
Treat Claude-only tool names as conceptual workflow steps and use available Codex tools/policies.
Codex Policy Gates
- Ask before external actions such as GitHub repository creation,
git push, deploys, or sending messages unless the user explicitly requested that exact action.
- Deployments must go through GitHub CI/CD; direct server access is only for emergency debugging of broken production.
- Never ask the user to paste secrets in chat. Direct them to
.env files or GitHub Actions secrets.
Do Feature
Project Documentation Autosync
If this command changes any project-local .claude/** file, immediately run:
~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply
If sync reports a conflict, stop and report it. Include generated .codex/** changes in the same commit as the .claude/** source change.
Execute a full feature using a team of agents.
Step 1: Load Skill
Invoke Skill tool: Skill(skill: "feature-execution")
Step 2: Find Feature
- User provides feature path or name
- Read
work/{feature}/tech-spec.md — verify exists and approved
- Read
work/{feature}/tasks/ — verify task files exist
- If tech-spec or tasks missing → stop, tell user what's needed
Step 3: Execute
Follow the loaded feature-execution skill workflow.
The skill checks checkpoint.yml in Phase 1 and handles resume automatically.
