Use when editing Orcho CLI behavior: orcho-core/cli/, CLI help text, output modes, interactive prompts, stdout/stderr formatting, transcript behavior, latest/resume commands, or public orcho, orcho run, orcho cross, orcho status, orcho evidence, orcho diff, orcho web UX. Do not use for pipeline semantics alone.
Use when editing orcho-core isolation and workspace safety: pipeline/project/isolationsetup.py, worktree selection/bootstrap, pre-run dirty intake, sandbox policy, runspace paths, dependency checkout subjects, git worktree tests, sandbox ADRs, or generated worktree handling. Do not use for runtime agent sessions or…
Use when editing phase lifecycle/execution mechanics: phase handlers/registry, orcho-core/pipeline/phases/, project run phase bookkeeping, subtask DAG execution, StepOutcome, subtask receipts, done-criteria attestation, phase transitions, and phase-level handoff/routing. Do not use for parser verdicts, gate decisions…
Use when editing orcho-core parser and gate semantics: planparser, reviewparser, releaseparser, plancontract, qualitygates, pipeline/control, review/repair/final acceptance, halt/resume/operator decisions, release verdicts. Do not use for prompt wording or public wire shape unless paired.
Use only for orcho-core triage/routing questions when the affected subdomain is unclear and no specific specialist, file path, or known subsystem is named. Route among prompt engine, runtime/session, phases/DAG, parsers/gates, evidence/observability, isolation/worktrees/sandbox, test infrastructure/goldens…
Use when editing Orcho runtime/session code: orcho-core/pipeline/runtime/, pipeline/engine/session.py, pipeline/sessionadapters.py, agents/runtimes/, agents/protocols.py, agents/registry.py, runtime invocation, session continuity/reset, runtime context autonomy, or agent runtime adapters. Do not use for prompt…
Use when editing orcho-core/sdk/, docs/sdkschema.json, public dataclasses, status/history/evidence/metrics/cost/run-diff payloads, plan/review/release wire schemas, or any core shape exposed through MCP. Pair with orcho-mcp for MCP-visible changes. Do not use for private parser internals or prompt prose.
Use when editing orcho-core shared test infrastructure: tests/conftest.py, tests/fixtures/, golden snapshots, snapshot normalizers, pytest config, collection hooks, acceptance fixtures, schema/golden regeneration, or broad fixture behavior. High blast radius; inspect consumers before editing.
Use only when selecting targeted tests, smoke checks, pytest marks, or verification strategy for orcho-core changes, including questions like "which tests should I run?" Covers SDK schema, prompts, runtime/session, evidence, cross-project, CLI, profiles/plugins, skills registry, golden fixtures, and acceptance mock…
Use for Orcho prompt authoring/rendering internals: orcho-core/pipeline/prompts/, orcho-core/core/prompts/, prompt templates/contracts, cache-aware rendering, session/delta prompt metadata, prompt snapshots, and prompt boundary tests. Pair with evidence/observability only when rendered prompt data is stored as…
Instructions for symphos-ai/orcho-core, covering orcho-core instructions, scope, workspace development pipeline, stable install is read-only and build, run, and test.
Use when editing orcho-mcp MCP server behavior: tools/resources/prompts registration, schemas, tools.py, resources, prompts.py, supervisor, run control, event tail, docs/mcpschema.json, stdio transport, progressToken notifications, or MCP client-facing payloads. Pair with orcho-core-sdk-wire when core shape changes.
Instructions for symphos-ai/orcho-mcp, covering orcho-mcp instructions, scope, local instruction files, workspace development pipeline and stable install is read-only.