| name | dolphi-agent-executor |
| description | Execute implementation work in the Dolphi codebase using the project's policy, workflow, and response template. Use when handling any feature, bug fix, refactor, test, or documentation request in this repository that must comply with offline-first privacy, BRD/PRD scope, and change-control rules. |
Dolphi Agent Executor
Overview
Apply the repository's operating rules for every task and keep outputs aligned with docs/product/BRD.md and docs/product/PRD.md.
Required Context Loading Order
Read these files in this order before implementation:
../../agent.md
../../docs/governance/AGENT_POLICY.md
../../docs/governance/AGENT_WORKFLOW.md
../../docs/governance/AGENT_TEMPLATE.md
../../docs/product/BRD.md
../../docs/product/PRD.md
../codex-prompt-generator/SKILL.md
Execution Rules
- Use
$codex-prompt-generator first for every prompt and force Plan Mode before implementation starts.
- Follow the full step order in
docs/governance/AGENT_WORKFLOW.md for every prompt.
- Enforce all policy constraints in
docs/governance/AGENT_POLICY.md.
- Map requested changes to BRD/PRD requirements and acceptance criteria.
- Keep edits minimal and within approved scope.
- Preserve local-first privacy defaults and offline behavior.
- Flag and document any scope, schema, or memory-model changes before implementation.
- If new reusable behavior is needed, invoke
$skill-creator and create/update the required skill artifacts.
- Keep all skill artifacts repo-local under
../../skills/ and do not create skills in global .codex/skills.
Privacy Gate (Always Apply)
- Do not add automatic cloud upload behavior.
- Keep user files and derived artifacts local by default.
- Require explicit user action for export/backup actions.
- Call out privacy impact in the final response, even when there is no impact.
Change-Control Gate (Always Apply)
Before coding, verify:
- Scope expansion beyond BRD/PRD is documented.
- Schema or memory logic changes include migration and rollback notes.
- Any privacy-weakening proposal is escalated as a product decision.
Output Contract
Return implementation updates using the exact fields in ../../docs/governance/AGENT_TEMPLATE.md.
Task Types Supported
- Feature implementation
- Bug fixes
- Refactors
- Test additions and hardening
- Documentation updates tied to BRD/PRD