ae-tracking-matrix
Tracking Matrix · Identification + Routing Foundation
Position: The Tracking Assistant Agent covers generate + audit + optimize + upload. Present a reviewable plan overview from the same canonical JSON in the conversation first, then ask the user to choose direct structured sync to Tracking Management or a local 11-sheet Excel. The sync branch creates no Excel; the Excel branch starts only after selection. After target/baseline/semantic validation, one explicit confirmation authorizes only the displayed remote scope via
references/workflows/validated-upload.md. No automatic upload, hidden Excel intermediate, implicit deletion/overwrite, or invented UI button. Language: this skill's main text is English; all user-facing replies (including routing, questions, review and acceptance) and newly authored business descriptions follow the user's language. Template-owned Chinese sheet names, headers and type labels remain unchanged. Do not call this an all-English template. This SKILL.md keeps only the "identify + route" logic (≤200 lines); execution flows are offloaded into in-package workflow references (references/workflows/*.md), loaded by route after identification. (v2.0: the nine former execution skills were merged into this package as workflow references — routing no longer depends on separate skill descriptions; only the two system skillsae-generate-tracking-codeandte-user-id-debugremain external.)
The te-user-id-debug handoff requires the system Skill supplied by the Agent environment; ae-cli does not install it. If it is unavailable, report the missing Skill before starting the deep investigation.
0. Trigger Boundary
Enter this flow when the user's request involves any of the following:
-
Tracking plan: generate / optimize / audit / increment / adjust / upload
-
Requirements document (PRD) → tracking suggestions
-
SDK tracking code, integration, reporting Q&A and troubleshooting
-
Tracking data verification (quality validation, plan acceptance — against the customer's real reported data)
-
Audit/review of an existing plan counts in ALL cases — even "just take a look". Never read a tracking xlsx with openpyxl/pandas before completing the four-step identification.
-
Tracking code generation counts too — "give me Android/iOS/Unity tracking code", "写埋点代码", "接入代码" all enter here first. After the four-step identification, this skill routes to the code-delivery execution skill (code_delivery). Never hang the code-generation skill directly from the user request: the identification step carries the naming dictionary and plan-consistency constraints that keep generated code aligned with the plan.