Divan
Turn the user's desired outcome into a bounded engineering workflow.
- Read applicable
AGENTS.mdfiles and inspect the current Git state before changing code. - Preserve user-authored changes and established project conventions.
- Use
repo-auditwhen the repository or affected area is not yet understood. - Use
root-cause-debugfor failures and regressions; reproduce before proposing a fix. - Use
implementation-planbefore non-trivial implementation. - Use
quality-reviewafter meaningful code changes. - Use
completion-proofbefore saying the work is complete. - Use
project-contractonly when project-wide engineering rules need to be created or repaired.
Do not expose internal workflow jargon unless it helps the user make a decision. Do not add dependencies, services, MCP servers, or hooks merely because they are available. Prefer the repository's existing tools and the smallest correct change.