boshu2__agentops/docs/agent-workflow-reference.md

Agent workflow reference

AGENTS.md directs the agent to own the authorized outcome through finish. Zero AgentOps skills are required. Use the native agent and shell; the tracker, Git and runtime keep their existing authority.

1. Use the existing intent. Plan only for missing intent or consequential uncertainty. A trivial change needs no Plan, Recall or Learn worksheet.
2. Implement the smallest useful change, repair known defects directly, and revise an approach when evidence disproves its assumption within unchanged outcome and scope. Changing acceptance needs caller authority.
3. Run cheap discriminating checks while editing, then required integration checks. Reserve capacity for finishing, final judgment and needed repairs.
4. Obtain fresh author-distinct final judgment over the exact subject. Same-family is default; cross-model is opt-in, with no fixed ten-minute cap. PASS requires all acceptance and empty not_checked; evidence gaps remain visible.
5. Repair known findings within real bounds and revalidate the changed subject. A genuine causal stall admits at most one bounded helper, never a chain. Report the outcome and evidence truthfully when complete or actually stopped.

Memory supplies on-demand recall and separately budgeted mining/curation over caller-selected reviewed external topic pages. BD owns work/status/handoffs, Git content, and native/CASS sources episodes. Learning can update, qualify or remove a rule; no-change is valid. Only later work establishes benefit. This lean route uses public or already-cleared inputs and claims no native restricted-source enforcement.

Specialists, anti-ceremony audits, factories and outer-goal guidance are optional. The RPI charter is an explicitly selected workflow; native goals and direct coding do not require it. A skill earns its context cost by resolving a task-specific need, not by occupying a phase in a sequence. No new scheduler, command or process ledger is needed. The grandfathered pure fixed-dispatch adapter is separately described in its own reference. Optional context-budget tooling (an opt-in read-budget hook plus bulk-read / code-write delegation) is described in context-budget delegation.

For exact intent snapshots, subject manifests, evidence storage, scope and freshness, use RPI traversal and Validate mechanics. New proof goes to caller-selected protected external non-Git storage; missing routing does not permit a workspace fallback. Legacy .agents/ evidence remains preserved.