Skip to content

Agent Instructions

Repository AGENTS.md files should be short, durable, and enforce the following contract. Phase 4 shipped it in plugin source; Phase 5 migrated each active repository instruction file and removed checked-in shared skills after upgrade, rollback, and fresh-process acceptance.

  • Inspect the current repository and applicable nested instructions before work.
  • Treat Linear as the product and explicitly tracked work control plane, GitHub as code delivery, and Markdown as durable technical reasoning.
  • Use Anuva skills for stateful workflows and named Anuva CLI operations for deterministic side effects.
  • Permit implicit repository-change classification. Routine is issue-free and the request authorizes implementation; Material is issue-free by default and pauses for an exact plan; Product Main required creates nothing and returns an exact intake proposal.
  • Create standalone Linear tracking only when the user explicitly requests it.
  • Require separate merge approval for routine work and separate plan and merge approvals for material work.
  • Never invoke a generic shell through the harness or invent unregistered commands.
  • Run reusable Anuva, GitHub, Git, and test commands directly and separately; shell command-string wrappers remain interactive and never inherit a nested direct-command allowance.
  • Treat config/codex/default.rules as the reviewed source. Test it with bun run check:rules; install, rollback, and inverse rollback require their exact machine-operation gate and a Codex restart after every active change.
  • Respect repository ownership and do not modify sibling repositories from the wrong Codex task.
  • Use change-folder artifacts in proportion to complexity, recovery, and Product Main handoff needs.
  • Keep user-facing documentation reachable through navigation or a meaningful index and strictly verify each logical update once.
  • Ask at documented approval boundaries and show the exact pending mutation.
  • Preserve user work in dirty worktrees and avoid unrelated changes.

Keep volatile change scope in the task, PR, Linear issue when selected, and change docs, not AGENTS.md. Keep detailed reusable procedure in skills, not duplicated across agent guidance. Use the Windows Development Machine Bootstrap instead of copying another machine's raw configuration, caches, credentials, or working trees.