Skip to content

Agent workflow

  1. Read local project instructions and look up the assigned Plane item.
  2. Inspect existing changes before selecting a branch or worktree.
  3. Load only the documentation needed for the current task.
  4. Implement and verify without disturbing concurrent sessions.
  5. Commit reviewed changes, record evidence in Plane, and leave a short handoff.

Codex reads local AGENTS.md according to its instruction hierarchy. OpenCode supports AGENTS.md and explicit instruction-file/URL configuration. Claude behavior depends on installed version; CLAUDE.md imports the shared file for compatibility. Verify loading in the actual client instead of assuming a remote URL is automatically read.

A documentation-repository clone does not automatically apply its instructions to unrelated repositories. Copy/import the reviewed shared rules into a project's local instruction structure deliberately, preserving existing project-specific rules.

Minimal telemetry

Dashboard lifecycle messages contain only a pseudonymous session identifier, status and timestamp. Do not send prompts, transcripts, tool arguments, code or credentials. Existing Office integration still requires real lifecycle verification for each client. Langfuse tracing requires an explicit SDK/OTel integration; it is not subscription usage metering.

Mandatory stack policy

The AI stack operating guide defines the Plane work-item requirement for all planned work, canonical Forgejo Markdown storage, lifecycle reporting, verification and completion criteria. Its mandatory policy is embedded in global client instructions for Windows and WSL; the detailed guide must be read at every task start and after handoff/compaction when absent from context. Existing repository rules and user scope still apply.