Start Here¶
Orca is local mission control for AI coding work. Start with one Mission.
The Four Parts¶
- Mission: the durable outcome, acceptance criteria, blockers, evidence, and lifecycle.
- Executor: Codex, Claude Code, another agent, or a human doing the work.
- Skills: optional procedures that help the executor plan, build, review, or ship.
- Integrations: optional adapters for trackers, docs, and other external systems.
Only the Mission is required. This separation is what keeps Orca useful across harnesses instead of turning it into another directory of prompts.
The First Path¶
- Install with Quickstart.
- Create one Mission with observable acceptance criteria.
- Let any executor make the change.
- Use
orca mission checkfor command-verifiable criteria. - Use
orca mission satisfyfor explicit review evidence. - Resolve blockers and run
orca mission complete.
The full walkthrough is in First Workflow.
Choose The Next Layer Only When Needed¶
- Need an agent implementation procedure? See Commands.
- Need reusable agent guidance? See Skills.
- Need host-specific behavior? See Compatibility Matrix.
- Need the larger capability catalog? See Feature Index.
- Need the conceptual boundary? Read What Orca Is.
The catalog is reference material. It is not the onboarding flow and it is not the definition of the product.