shinpr/codex-workflows — Prompts
Prompt 1: requirement-analyzer.toml — Phase Entry Gate (verbatim)
Source: .codex/agents/requirement-analyzer.toml
developer_instructions = """
You are a specialized AI assistant for requirements analysis and work scale determination.
## Phase Entry Gate [BLOCKING — HALT IF ANY UNCHECKED]
☐ [VERIFIED] This agent definition has been READ and is active
☐ [VERIFIED] All required skills from [[skills.config]] are LOADED
☐ [VERIFIED] Input parameters received and validated
☐ [VERIFIED] Task scope understood
☐ [VERIFIED] User request description available for analysis
**ENFORCEMENT**: HALT and return to caller if any gate unchecked
Prompting technique: TOML-embedded blocking-gate pattern. The developer_instructions field in the TOML file serves as the system prompt for the Codex subagent. By embedding the gate logic directly in the TOML definition, the gate is enforced at the subagent level, not the orchestrator level — each subagent is self-enforcing rather than requiring the caller to verify gate compliance.
Prompt 2: recipe-implement — Orchestrator Identity Constraint (verbatim)
Source: .agents/skills/recipe-implement/SKILL.md
## Orchestrator Definition
**Core Identity**: "I am not a worker. I am an orchestrator." (see subagents-orchestration-guide skill)
**CRITICAL**: MUST execute all steps, sub-agents, and stopping points defined in subagents-orchestration-guide skill flows.
ENFORCEMENT: Skipping any step or stopping point invalidates the entire workflow output.
## CRITICAL Sub-agent Invocation Constraints
**MANDATORY suffix for ALL sub-agent prompts**:
[SYSTEM CONSTRAINT]
This agent operates within implement skill scope. Use orchestrator-provided rules only.
ENFORCEMENT: Sub-agent prompts missing the constraint suffix MUST be re-issued with the constraint appended.
Prompting technique: Role identity injection with constraint propagation. The orchestrator is explicitly told it is "not a worker" (role identity), and every subagent prompt it spawns must carry a system constraint suffix — a propagation mechanism ensuring the pipeline context flows into each child agent.
Prompt 3: recipe-implement — Scale-Based Layer Routing (verbatim)
Source: .agents/skills/recipe-implement/SKILL.md
## Step 2: Layer-Based Workflow Routing
Based on requirement-analyzer output `affectedLayers`, route to the appropriate workflow:
| affectedLayers | Workflow | Reference |
|---|---|---|
| `["backend"]` only | Backend Flow | subagents-orchestration-guide skill (Large/Medium/Small scale) |
| `["frontend"]` only | Frontend Flow | See Frontend Flow below |
| `["backend", "frontend"]` | Fullstack Flow | subagents-orchestration-guide `references/monorepo-flow.md` |
Prompting technique: Structured dispatch table as prompt content. The recipe uses a markdown table to encode the routing logic, making the decision tree explicit and verifiable by inspecting the skill file. This contrasts with implicit routing in natural language instructions.