| name | gemini-command-author |
| description | Create Markdown implementation or retry instructions for Gemini work in this repository and place them in `communication/CodexToGemini/command_waiting/`. Use when Codex needs to hand off a concrete task, include repo-specific constraints, attach file links, and queue the work without doing the implementation locally. |
Gemini Command Author
Write one Markdown instruction per task and queue it in communication/CodexToGemini/command_waiting/.
Workflow
- Read the repo-specific context from:
- If the task touches samples or documents, load:
- Draft a single-task instruction using the template in references/instruction-template.md.
- Use a unique filename:
YYYYMMDD-HHMMSS-<task-id>.md.
- Save only to
communication/CodexToGemini/command_waiting/.
Required Content
- Clear task goal and completion criteria
- Exact file paths Gemini may need to read or edit
- Commands Gemini must run for proof
- Expected report contents
- Branch instructions:
- branch from
develop
- use a
codex/ branch name
- do not merge to
develop
- report the branch name back to Codex
- Constraints:
- C# first
- 2D first
- Codex does not implement the task
- Evidence-based claims only
- Repo-local evidence only for semantic upgrades
Writing Rules
- Keep the instruction decision-complete
- Link directly to important repo files when they matter
- State unknowns explicitly instead of guessing
- Do not combine unrelated work in one instruction
- If a task uses hardware or byte-window helper skills, state whether they are allowed only for raw annotation or also for semantic evaluation
- For
xdos-semantics-engine, explicitly state that it is an annotation helper and cannot by itself justify provisional or confirmed
- When generating a user-facing handoff code block for Gemini, never include nested code blocks inside it
- If commands must be shown inside that user-facing code block, render them as plain text bullet items
References
