Skip to main content

Agent Task Routing

Use the smallest workflow that matches the task. Skill frontmatter decides activation; this projection explains the boundary, expected output, and handoff for each core task.

TaskSkillMutation boundaryOutputHandoff
Simple lookup or bounded editNo skilldirect-boundedA sourced answer or the smallest verified edit.Route unresolved factual synthesis to research and multi-step product choices to plan.
Researchresearchread-only-unless-persistence-requestedEvidence, contradictions, confidence, and remaining human decisions.Send accepted future decisions to plan; send observed failures to debug.
Planningplanplan-artifacts-before-implementationLocked decisions, executable order, boundaries, and validation.Send factual prerequisites to research and implementation only after scope lock.
Debuggingdebugdiagnose-first-fix-when-requestedReproduction, failing layer, root cause, bounded fix, and proof.Route architectural redesign or unresolved product behavior to plan.
Change reviewreviewread-only-pinned-diffActionable regressions, remaining gaps, and readiness verdict.Return fixes to the implementing task; use resolve-pr-comments for active PR feedback.
Architecture discoveryplanread-only-until-human-selectionRanked candidate cards and a selected interface only after human choice.Send the selected candidate into the owning Plan Hub for implementation.
Architecture certificationmodule-seams-reviewread-only-pinned-proofPinned proof of boundaries, exports, adapters, consumers, tests, and registry freshness.Route uncertified design changes to plan and concrete regressions to the implementation owner.
Repository auditauditread-only-numbered-findingsEvidence-backed dead code, drift, dependency, guidance, and invariant findings.Send approved cleanup-shaped findings to clean and architecture choices to plan.
Approved cleanupcleanapproved-finding-ids-onlyThe smallest implementation for the approved findings with residue checks.Return new or uncertain findings to the user instead of expanding scope.
Live product QAqa-sessionsession-bounded-fix-and-revalidateStable observations, bounded fixes, revalidation, and deferred handoff.Send deferred backlog work to qa-triage and root-cause investigations to debug.
QA notes and backlogqa-triageauthorized-product-records-and-private-qa-rowsScoped Product records and private QA rows.Send live product fixes to qa-session and unclear failures to debug.
PR feedbackresolve-pr-commentscurrent-actionable-feedback-and-bounded-siblingsValidated comment resolution, bounded sibling sweep, and fresh proof.Return product or architecture decisions to the user or owning Plan Hub.
Pre-merge readinessshipreadiness-and-user-authorized-publish-actionsFresh gate evidence, branch/commit readiness, and explicit blockers.Return failures to the owning implementation task; never redesign during the gate.
Design directiondesignadvisory-until-explicit-polish-scopeA grounded paradigm, material, or layout decision, design review findings, or an AI design-tool prompt contract.Send cross-surface token or dialect changes to planning; send implementation defects to debugging.
Doc review feedbackdoc-feedbacktriage-then-scope-locked-editsA triaged feedback record and each accepted item addressed in the agreed in-repo or out-of-repo mode.Route discovered product defects to debugging and net-new scope to planning.

Authority order

  1. nearest AGENTS.md
  2. code and checked-in configuration
  3. packages/shared/src/ontology/green-goods-ontology.json
  4. owning Plan Hub
  5. task-specific skill

Ownership and synchronization

The upstream surface owns truth. Public documentation explains or projects that truth; it does not publish live Plan Hub state, Linear status, or private QA evidence.

SurfaceRoleOwnsVisibility
ImplementationauthorityRuntime behavior, routes, exports, endpoints, deployment state, and workflows.repository
OntologyauthorityCross-package entities, vocabulary, relationships, schemas, and lifecycle meaning.repository
Maturity projectionsauthorityDerived feature maturity labels and projection rules.repository
Agent skillsauthorityTask activation, mutation boundaries, proof rules, and handoffs for agent workflows.repository
Plan HubsauthorityAccepted decisions, execution state, lane evidence, dependencies, and closeout rationale.repository
QA catalogauthorityStable QA case definitions, expected outcomes, and evidence requirements.repository
Private QA evidenceevidenceRun-specific observations and private supporting evidence.private
LinearcoordinationStakeholder-visible priorities, accepted work, and delivery state mirrored from repository authorities.external
Authored documentationprojectionStable explanations, user flows, recovery guidance, and navigation.public
Generated documentationprojectionDeterministic public inventories and diagrams projected from checked-in authorities.public

A routed skill must not absorb neighboring work. When the requested outcome changes, follow the task's handoff instead of expanding the active workflow.