What problem does it solve? Agents working on AOPS projects need a consistent way to choose and follow a working discipline—solo-pm-loop, build-review-chat, design-first-consensus, or coordinator-loop—so that review requests, consensus, memory, and closeout behavior stay aligned with the approved workflow instead of drifting ad hoc. ## Core Features & Use Cases - Discipline selection: Maps session signals (mode, agent count, uncertainty) to one of four canonical disciplines, with operator override via aops-cli start --discipline. - Mission policy seeding: Bridges aops-cli start --json output into hosted mission policy via aops-cli mission create/update --policy-json, including roles, guardrails, and signal mapping. - Recipes and guardrails: Provides per-discipline execution recipes (review-request per slice, consensus-to-plan binding gate, coordinator delegation rules) plus an explicit closeout checklist covering memory, review triage, issue triage, and resume readiness. - Use Case: An operator asks an agent to run a live implementer/reviewer session; the agent selects build-review-chat, creates a review request per slice with aops-cli pm review-request create, waits for accepted review results before committing with explicit pathspec, and closes out with a handoff memory entry. ## Quick Start Ask the agent to use the aops-working-disciplines skill to pick the right discipline for your session and seed the mission policy from aops-cli start output.
