Tracker intake
Symptom
The parent runs the plain-text feature ladder for a pasted issue key, calls tracker MCP from the parent chat, or sends a defect through PM → BA.
Cause
Class (micro | minor | feature) answers how big, not where the work came from. A tracker key changes the input contract. For a defect, the whole chain changes.
Do not
- Call tracker MCP, the Jira/
ghCLI, orjira_api.py/github_api.pyfrom the parent or from BA - Run PM or BA on a bug —
rca.mdis the spec - Let the developer start before
HANDOFF-bug-analyst.mdis SUCCESS - Write
route.mdbefore intake returns - Hardcode project key, JQL, owner/repo, MCP name, or issue-type mapping in a skill
- Switch
intake.jira.connectionorintake.github.connectionsilently when the configured one fails - Treat a bare
#123as GitHub whenintake.github.enabledis false orrepois empty
Convention
O1 detect → O2 intake → O3 resolve → O4 route → O5 drive. See Jira workflows and GitHub workflows.