Ae Generate Tracking Plan

ae-generate-tracking-plan

Cross-skill collaboration

When remaining work is outside this skill's scope, or a necessary prerequisite needs another capability, follow the collaboration protocol [blocked]. Choose from the skills available in this run by capability, preserve verified context, and continue the remaining task. Reuse this protocol if already loaded.

Conversation language: This skill document is in English, but all output to the user MUST be in the user's input language. English input → English reply; Chinese input → Chinese reply; Japanese input → Japanese reply. If uncertain, default to English. This applies to all output: section titles, phase names, template prompts, example text, option lists, etc. ⚠️ CRITICAL: Template localization is CLI-owned. Do NOT manually translate imported template content with the model. Use the src/tracking/i18n module as the source of truth by setting AE_LANG=<user_lang>, writing draft.meta.lang, and regenerating through ae-cli tracking code import-template / ae-cli tracking plan draft. Before changing any template-owned localized label, first look up the corresponding translation in src/tracking/i18n (for example resources/xlsx/sheets.ts, resources/xlsx/headers.ts, resources/xlsx/types.ts, and resources/cli/*.json). If no matching translation exists there, preserve the imported text and ask before rewriting business semantics. Do NOT copy Chinese text verbatim from this document into English/Japanese replies unless it is an identifier, template name needed for CLI import, or original source material quoted for traceability.

Terminology Glossary

When to Trigger

Trigger when user mentions: "tracking plan / tracking template / AE plan / help me create tracking" etc. App types covered: H5 / Web / iOS / Android / Mini-program / Unity. Follow strictly Phase 0 → 1 → 2 → 3 → 4, do not skip steps.

Phase 1 / 3 / 4 are executed via ae-cli tracking CLI (ae-cli tracking plan draft / ae-cli auth login / ae-cli tracking plan upload / ae-cli tracking plan delete). All CLI commands must be prefixed with AE_LANG=<user_lang> (e.g. AE_LANG=en ae-cli tracking plan draft ...), ensuring CLI output messages and generated xlsx headers match the user's language. Upload commands MUST also pass --lang <user_lang> so the server parses the uploaded xlsx with the same sheet/header language.

Language rules: For newly generated content, user-facing fields in draft.json (display_name, event_desc, event_tag, property display_name, property desc, etc.) should be generated in the user's input language. Every event, event property, common event property, and user property must have a non-empty display_name. A canonical snake_case identifier is not a substitute for a user-facing display name. For imported templates, do NOT translate those fields manually. Template sheet names, headers, property type display values, CLI messages, and auto-track/i18n-owned labels must come from src/tracking/i18n via AE_LANG=<user_lang> and draft.meta.lang. When a localized label is needed, inspect src/tracking/i18n and use the existing resource key/value; do not invent translations from the model. If template business text needs localization and the CLI/i18n resources do not provide it, preserve the imported text and ask the user before rewriting business semantics. Only identifier fields like event_name, prop_name remain in English. Property names are snake_case; event names are lowercase by default, uppercase only when the user asks to preserve it. This skill only cares about command behavior, not internal implementation.

Phase 0 — Anchor (one question per message)

Step 1: Language initialization

Determine <user_lang> from user's input language: Chinese→zh, English→en, Japanese→ja, Korean→ko. Other languages default to en. All subsequent CLI commands must be prefixed with AE_LANG=<user_lang> to ensure CLI output and generated xlsx headers match the user's language. When uploading the xlsx, pass --lang <user_lang> as well; it must match draft.meta.lang / the generated xlsx language.

Collect the following 5 items sequentially, do NOT ask all at once:

Item 1 — Application Scenario

Ask: "What is your application's business scenario? One sentence summary, e.g.: An e-commerce website where users browse products and place orders"

After user responds, record to meta.scenario and generate meta.plan_name.

Item 2 — Source Material + Business Dimension (combined)

Before asking, decide whether the current runtime is an agent sandbox. The agent may judge this from runtime context such as sandbox-provisioned cli-token.json, restricted filesystem access, or absence of the user's local files. Do not ask the user just to decide sandbox visibility.

Product document is available in sandbox environments only for files that are readable inside the sandbox workspace, including files the user attaches/uploads into the conversation workspace. It cannot read arbitrary local paths outside the sandbox unless those files are mounted or attached. Codebase is a local-material option and must be hidden in sandbox environments unless the codebase is already present in the readable workspace. When options are hidden, renumber the visible list contiguously from 1; never show skipped numbers.

If not in a sandbox environment, ask exactly:

Choose your source material (up to 2):
1 - Product document (local path, image file, or folder) — Extract events and properties from product docs; supports md/pdf/docx/xlsx/pptx/URL/images (png/jpg/jpeg/webp)2 - Detailed description (conversational) — Describe app business flow, core features, user behaviors, monetization model, etc.3 - Codebase (local project path; hidden in sandbox) — Analyze source code to extract events and properties4 - Pre-built template (built-in industry and game genre templates) — Select a built-in template5 - Modify existing tracking plan (local AE format xlsx file) — Import an existing tracking plan xlsx as baseline for modification; can be combined with Product doc / Description / Codebase, but NOT with Pre-built template6 - Data sample / file profile (from ae-data-integration inspect) — Map data columns (CSV/Excel/JSONL) to events & properties from an inspect profile; single-source path, not combinable with other options
Reply with number(s), e.g. 1,5 or 4. Select up to 2 (option 6 is single-source).

If in a sandbox environment, ask exactly:

Choose your source material (up to 2):
1 - Product document (sandbox workspace path, uploaded attachment, URL, image file, or folder) — Extract events and properties from product docs; supports md/pdf/docx/xlsx/pptx/URL/images (png/jpg/jpeg/webp). You can attach/upload relevant files here.2 - Detailed description (conversational) — Describe app business flow, core features, user behaviors, monetization model, etc.3 - Pre-built template (built-in industry and game genre templates) — Select a built-in template4 - Modify existing tracking plan (sandbox workspace path) — Import an existing tracking plan xlsx as baseline for modification; can be combined with Product doc / Description, but NOT with Pre-built template5 - Data sample / file profile (from ae-data-integration inspect) — Map data columns (CSV/Excel/JSONL) to events & properties from an inspect profile; single-source path, not combinable with other options
Reply with number(s), e.g. 1,4 or 3. Select up to 2 (option 5 is single-source).

Do not rewrite this source material list as unnumbered bullets, cards, or prose. The user must be able to reply with the visible numbers. When translating this prompt, preserve the numeric prefixes and line breaks exactly. Every visible option MUST be on its own line and MUST begin with 1 -, 2 -, 3 -, etc. Never place two numbered options in the same paragraph or visual line. If a Markdown renderer may collapse soft line breaks, use Markdown hard line breaks (two trailing spaces before newline) rather than blank lines. Translation may change only the option text, not the numbering prefix or one-option-per-line structure.

User can multi-select (max 2). Interpret numbers by the visible list shown to the user, not by the non-sandbox canonical list.

Canonical source material options (non-sandbox numbering):

1. Product document ****(****local path, sandbox workspace path, uploaded attachment, URL, image file, or folder) — Extract events and properties from product docs; supports md/pdf/docx/xlsx/pptx/URL/images (png/jpg/jpeg/webp)
2. Detailed description (conversational) — Describe app business flow, core features, user behaviors, monetization model, etc.
3. Codebase (local project path; hidden in sandbox) — Analyze source code to extract events and properties
4. Pre-built template (built-in industry and game genre templates) — Select a built-in template (run AE_LANG=<user_lang> ae-cli tracking plan list-templates --json to see available templates)

Based on user selection, determine source material type and record to meta.source_type:

Follow-up questions (ask in follow-up order defined in Multi-Source Combination Rules below):

• Product doc → if not in a sandbox environment, ask exactly:
  text

  What is the product document path?
  You can provide one or more items, separated by commas or newlines:1. Local file path2. URL3. Image file path4. Folder path

• Product doc → if in a sandbox environment, ask exactly:
  text

  What is the product document path?
  You can provide one or more items, separated by commas or newlines:1. Sandbox workspace path2. Uploaded attachment path3. URL4. Image file path5. Folder path
  You can also attach/upload relevant files here, and I will read them from the sandbox workspace if available.

• Detailed description → If too vague, follow up on core features, user behaviors, business flows, monetization
• Codebase → ask "What is the project directory path?", then scan source to extract business logic
• Pre-built template → display matching templates for user confirmation
• Modify existing tracking plan → ask "Please provide the xlsx file path of your existing tracking plan", then follow the flow below
• Data sample → ask "Please provide the path of the inspect profile JSON (or the run directory containing it)", then read the ae-local-data-profile/v1 product and follow the "Data-path (source_type = data)" flow below

Modify Existing Tracking Plan Flow (when user selects this option):

1. Import: Ask user for the file path, then immediately import:

   bash

   AE_LANG=<user_lang> ae-cli tracking code import-template --template <path> --out .ae-cli/draft.json

2. Check result:

   • If CLI errors (file not found / parse failure) → report error, ask user to fix the file and retry
   • If draft.json has events array empty → 🛑 Severe: No AE-format sheets found (missing # prefix sheets like #事件数据). Tell user the file does not appear to be an AE tracking plan xlsx. User must fix the original file and re-import.

3. Content validation (when events are non-empty):

   bash

   AE_LANG=<user_lang> ae-cli tracking plan validate --in .ae-cli/draft.json --fix

4. Handle validation results by severity:

   • If validate passes with no issues at all → skip to Step 5.

   Severity	Examples	Handling	User Action
   🔧 Minor (auto-fixable)	display_name duplicate, array_row sub-property inconsistency, event name duplicate	--fix auto-fixes, writes to draft.json. Inform user of what was fixed.	None (informed)
   ⚠️ Medium (needs confirmation)	property name snake_case violation, property name duplicate, invalid property type, nested property parent is not a composite type	List each issue with current value → suggested fix. User confirms item by item before writing to draft.json.	Confirm each fix
   🛑 Severe	File cannot be parsed, or events array is empty after import	Reject. Tell user the specific issue. User fixes original file and re-imports.	Fix original file

   Medium issue confirmation format:

   ⚠️ The following content needs to be fixed:
   | # | Issue | Location | Current | Suggested ||---|-------|----------|---------|------------|| 1 | snake_case | event_name | UserLogin | user_login (keep UserLogin only if the user asked to preserve case) || 2 | snake_case | prop_name | vipLevel | vip_level || 3 | invalid type | property "level" | integer | number |
   Apply all suggested fixes? ok / specify per item / skip

   • ok → apply all suggested fixes to draft.json
   • specify per item → confirm each item one by one
   • skip → keep current values, handle in Refine phase later

   ⚠️ Never modify the user's original xlsx file. All changes go into draft.json.

5. Re-validate after fixes → loop until clean, then continue to the next follow-up question (if combined with another source material), or Item 3 (if existing_plan is the only source).

Codebase analysis flow (when source_type includes codebase):

1. User provides project directory path
2. Scan directory structure, identify tech stack (engine/framework/language)
3. Read core business modules (game logic, scene management, UI interaction, state/data models, networking/payment, etc.)
4. Extract from code:
   • Events: Player interaction actions (click/swipe/trigger), scene transitions, game state changes (start/pause/end), business flow nodes (purchase/upgrade/unlock)
   • Event Properties: Action parameters (bullet type/enemy level/item ID), state values (score/HP/coins), context (level ID/difficulty/mode)
   • User Properties: Persistent state (level/experience/VIP/cumulative spend)
5. Map extracted results to AE naming conventions (event names lowercase by default, uppercase only on request; property names snake_case; + display_name in user's language)
6. Confirm extracted results with user, supplement missing items

Business Dimension Confirmation:

After source material is confirmed, must process business dimension info based on source_type. User must explicitly confirm before proceeding.

If source_type is template or starts with template_ (covers template, template_prd, template_codebase, template_chat):

Display template's preset business dimensions:

Business Dimension (inherited from template: <template name>)
Revenue Model: <revenue_model>Core Loop: <core_loop>Functional Entries: <functional_entries>Currency System: <currency_system>
Confirm using these business dimensions? ok / modify

• User ok → proceed to next step
• User says "modify" → switch to prd/chat flow for user to supplement
• For combos (e.g. template_prd): after confirming template dimensions, also note any supplementary insights from prd/chat as context for Phase 1.2.

If source_type includes existing_plan:

Infer business dimensions from the imported plan content:

1. Analyze existing events: Examine event_tag values to identify functional modules (e.g. events tagged "Battle" → 战斗 module). Examine event names for payment/ad-related patterns to infer revenue model.
2. Inference display: Format inference results as a summary:
   Business Dimension (inferred from existing plan: <filename>)
   Revenue Model: <inferred from payment/ad events>Core Loop: <inferred from event flow>Functional Entries: <inferred from event_tag values>Currency System: <inferred from currency-related properties>
   Confirm these business dimensions? ok / modify

3. Follow up missing: Only ask about items that could not be inferred
4. Event injection preview: Show suggested injected event modules (only add events not already in the plan); user ok to proceed

• For combos (e.g. existing_plan_prd): after confirming dimensions from the plan, also note any supplementary insights from prd/chat as context for Phase 1.2.

If source_type is prd / codebase / chat:

1. Inference display: Format inference results as a summary, using business-dimension-mapping.md as the mapping baseline
2. Follow up missing: Only ask about missing items or items inferred as "simple"
3. Event injection preview: Show suggested injected event modules; user ok to proceed

Platform validation: Use business-dimension-mapping.md Chapter 5 decision rules to check if injected events' platform assignments are reasonable.

Template matching (prd / codebase / chat scenarios, optional; NOT applicable to existing_plan or template scenarios):

After business dimension confirmation, auto-detect matching templates based on app type:

AE_LANG=<user_lang> ae-cli tracking plan list-templates --json

Show matching templates to user for confirmation. Confirmed templates serve as baseline and participate in Phase 1 event merging.

Multi-Source Combination Rules (when user selects 2 source materials)

Follow-up Order (Phase 0 questioning sequence):

Do not follow user's selection order. Instead, use this order:

existing_plan（blocking validation, always first）→ codebase/prd（user's selection order）→ chat → template

Rationale:

• existing_plan must go first — import + validate may require the user to fix their file; processing it early avoids wasted context
• codebase / prd — directly reflect actual business requirements, prioritized over generic descriptions and templates
• chat — conversational description, supplements business context
• template — generic industry template, least specific to the user's business

Source material processing happens primarily in Phase 1.2 (Merge Source Materials). The one exception is existing_plan: it is imported and validated in Phase 0 because user-provided files may need fixing before proceeding. All other sources are processed in Phase 1.2 per their standard flow.

Merge priority (Phase 1.2): existing_plan → template → codebase → prd → chat → autotrack Earlier sources take precedence — same-name events keep the earlier version, later sources only add new events or merge prop_names without overwriting.

Business Dimension Inference (combined scenarios):

Use the baseline source's inference method as primary. Supplementary sources (especially prd/chat) may contribute additional information — present a merged view for user confirmation.

Valid Combinations:

The "Baseline" column identifies which source has higher merge priority (see Phase 1.2 merge order), which may differ from the user's selection order. Follow-up questioning uses the fixed order in "Multi-Source Combination Rules" above, not the user's selection order.

Forbidden: existing_plan + template (both provide event baselines; semantic conflict).

Record business dimension info to meta.business_dimension:

"business_dimension": {  "revenue_model": "<model>",  "core_loop": "<description>",  "functional_entries": ["<entry list>"],  "currency_system": { ... },  "ad_scenes": [],  "iap_items": []}

Data-path (source_type = data) — condensed single-gate flow

When the user selects the Data sample / file profile option (source_type = data), the flow diverges from the standard 5-item anchor. This path maps table columns → events/properties instead of inventing events from business understanding, and uses a single confirmation gate instead of the 5-segment Refine loop.

What to skip (only Item 1 — Application Scenario and Item 2 — Data sample are collected):

• Item 3 (SDK Integration Config) → skip. meta.sdk_integration_mode = "none" (data ingested via RESTful / LogBus / DataX, no SDK). No SDK auto-track events are injected (Phase 1.4 already skips none).
• Item 4 (User Identity System) → skip the visitor-ID strategy question. Derive meta.user_identity from the inspect profile's identity_candidates instead (e.g. a distinct_id / account_id column), account_id_source: "user_account" when an account column exists, otherwise "none".
• Business Dimension confirmation → skip. Mapping is driven by columns, not by revenue model / core loop. meta.business_dimension stays empty.

Draft construction (replaces Phase 1.1/1.2/1.3 for the data path):

1. Read the inspect profile: the ae-local-data-profile/v1 JSON product (columns / types / samples / UE eligibility / mapping confidence). If it is not present or is stale, re-run ae-cli data-integration inspect for the source file first.
2. Event model determination (reuse UE routing): single-table single-event track / single-table multi-event (event-name column) / single-table user_set / mixed. The agent may propose splitting one table into multiple events (e.g. an ad table split by campaign_type into ad_show / ad_click); such proposals MUST be confirmed in the gate.
3. Column → property mapping draft:
   • Identify system columns first: time field, distinct_id / account_id, event-name column, user-property-name column.
   • Map the remaining columns to event properties / user properties / super properties.
   • Naming: snake_case property names, event names lowercase by default (uppercase only on request) + display_name + desc + event_tag (language follows the user's input).
   • Type inference: CSV columns default to string; infer number / bool / datetime / enum from field name + value distribution + business doc/prompt priors. Uncertain or conflicting columns are marked "to-confirm" and asked only inside the gate (do not ask column-by-column beforehand).
4. Single confirmation gate (replaces Phase 2, see below).
5. Merge with existing plan (reuse Phase 4.1/4.2 conflict detection).
6. Persist: .ae-cli/draft.json → xlsx → upload (sdk_integration_mode = none).

Single confirmation gate (one round, one summary table):

Present ONE merged table covering all of the following in a single message, then wait for a single reply:

• Event list: event_name / display_name / desc / event_tag / platform.
• Property list: name / display_name / type / desc / source, with uncertain types highlighted (marked "to-confirm").
• Field scope: default to plan-internal fields only; include a full-import switch for bringing all source columns in.
• Unrecognized / dirty data handling: how unmapped columns, null values, and unparseable rows are treated.
• Same-name property type conflicts: flagged inline in the gate (see Phase 4.2 Type A).

User replies once: ok (accept all), or targeted edits — rename / retype / add / remove individual columns or events. After the gate is confirmed, jump to Phase 3 (project token) then Phase 4 (merge + upload); do NOT enter the 5-segment Refine loop.

dry-run mode:

When the user requests dry-run (or the caller passes data-integration plan --dry-run), produce the draft preview + column→property mapping summary ONLY:

• Show the single confirmation gate table (events + properties + field scope + unrecognized-data handling) and the mapping result, but do NOT write .ae-cli/draft.json.
• Do NOT generate xlsx, do NOT archive to plans/, do NOT upload to AE.
• State explicitly that nothing was persisted; the user can approve a real run afterwards.

Item 3 — SDK Integration Config (client + server combined)

Ask: "What is your client platform? (multi-select OK, e.g. Android + iOS) Will you integrate a server-side SDK?"

After asking this Item 3 question, stop and wait for the user's answer. Do not display Item 4 in the same response.

Language filter: The following SDKs have Chinese-only documentation and are visible to Chinese users only: Mini-program, Mini-game, OpenHarmony, LayaAir, Egret, Cocos2d-Lua. Do not show these to non-Chinese users.

Client integration (multi-select OK):

Programming language (Android / iOS SDK only):

Follow-up: chose Android SDK → ask "Which programming language? Java / Kotlin / both" Follow-up: chose iOS SDK → ask "Which programming language? Objective-C / Swift / both"

Record to client_platform_languages:

"client_platform_languages": {  "android": ["java", "kotlin"],  "openharmony": ["typescript"]}

⚠️ Multi-platform meta field rules: When ≥2 client platforms are selected, Draft meta must use client_platforms (array) + client_platform_languages (dictionary). Do NOT use only client_sdk_type (single value) + client_language (single value), which would only record one platform. Single-platform scenarios use client_sdk_type + client_language.

Server integration:

SDK integration mode auto-detection:

none mode: Suitable for historical data import, batch data sync, third-party system integration, etc. Refine phase does not inject SDK auto-track events.

Item 3 confirmation gate:

After the user answers Item 3, normalize the SDK configuration and ask only the missing follow-up questions (for Android/iOS programming language or Other server language).

Then summarize the normalized SDK config and ask: "Confirm this SDK integration config? Reply ok to continue to Item 4, or describe changes."

Do not display Item 4 or ask identity questions until the user explicitly confirms this SDK integration config.

Item 4 — User Identity System (visitor ID + account ID combined)

Ask: "What is the visitor ID generation strategy?"

Options:

• auto — SDK auto-generates (default, suitable for most scenarios)
• device_id — Use device ID (iOS IDFV / Android AndroidID)
• custom — Custom visitor ID (must call identify() immediately after SDK init)

Follow-up: chose custom → ask "What value should the visitor ID use? e.g.: device ID / UUID / guest temp ID"

Ask: "What is the account ID source?"

Options:

• user_account — User account ID (unique identifier after login)
• role_id — Role ID (game-specific; one account may have multiple roles)
• none — No account system (pure guest mode)

Follow-up:

• chose user_account → ask "What specific value for account ID? e.g.: user_id (user ID), phone (phone number), email (email address)"
• chose role_id → explain "Role ID is suitable for games — one account can create multiple roles, enabling finer-grained per-role behavior analysis"

Record to meta.user_identity:

Phase 1 — Draft

1.1 Construct Canonical Draft

Draft conceptual structure (internal JSON; users do not view directly):

Draft├── meta:│   ├── app_type:                   App type│   ├── sdk_integration_mode:       SDK integration mode: client_only / server_only / both│   ├── client_platforms?:          Client SDK type list (required when multi-platform, e.g. ["android","ios"])│   ├── client_sdk_type?:           Primary client SDK type (single platform, backward compatible)│   ├── client_platform_languages?: Per-platform languages (required when multi-platform, e.g. {"android":["kotlin"],"ios":["swift"]})│   ├── client_language?:           Client dev language (single platform, backward compatible)│   ├── server_language?:           Server dev language (only when server_only or both)│   ├── project_id?:                AE project ID (filled in Phase 3)│   ├── host?:                      AE web address (filled in Phase 3)│   ├── plan_name:                  Plan name│   ├── lang:                       xlsx output language (zh/en/ja/ko), based on user's current language; controls generated xlsx headers/sheet names│   ├── scenario:                   Business scenario description│   ├── source_type:                Source material type│   ├── user_identity:              User identity config│   │   ├── account_id_source:      Account ID source: user_account / role_id / none│   │   ├── account_id_field?:      Account ID field name (only when user_account, e.g. user_id / phone / email)│   │   ├── distinct_id_strategy:   Visitor ID strategy: auto / device_id / custom│   │   └── distinct_id_custom_value?: Custom visitor ID value│   └── business_dimension:         Business dimension config (injected in Phase 1.3)│       ├── revenue_model:          Revenue model: IAA / IAP / mixed / subscription / commission│       ├── core_loop:              Core gameplay loop description│       ├── functional_entries:     Functional entry list│       ├── currency_system:        Currency system│       ├── ad_scenes:              Ad scenes (IAA / mixed only)│       └── iap_items:              IAP items (IAP / mixed only)├── events:                         Event array, each with platform field├── event_properties:               Global event property pool (deduplicated)├── common_event_properties:        Common/super properties (attached to every event)└── user_properties:                User properties

SDK integration mode fields:

// Multi-platform example (Android + iOS){  "sdk_integration_mode": "both",       // client_only / server_only / both  "client_platforms": ["android", "ios"],   // Required for multi-platform  "client_platform_languages": {            // Required for multi-platform; per-platform languages    "android": ["kotlin"],    "ios": ["swift"]  },  "server_language": "java"                // Only when server_only or both}
// Single platform example (backward compatible){  "sdk_integration_mode": "client_only",  "client_sdk_type": "android",            // Single platform  "client_language": "kotlin"              // Single platform}

Event platform tag (events[].platform):

{  "event_name": "order_create",  "display_name": "Order Create",  "platform": "server",    // client / server / both  "prop_names": ["order_id", "order_amount", "payment_method"],  "source": "prd"}

• platform: "client" — Client-side upload (user behavior events)
• platform: "server" — Server-side upload (business data events)
• platform: "both" — Both sides upload (timestamps must be synced)

Property object format (event_properties / common_event_properties pool entries):

{  "name": "order_amount",  "display_name": "Order Amount",  "type": "number",  "desc": "Order total in cents",  "source": "prd"}

⚠️ Field names: use name (NOT prop_name), display_name, type, desc, source. Events reference properties by prop_names: ["order_amount", ...] — this is an array of property name references (string array), NOT property objects.

User property format (user_properties pool entries):

{  "name": "vip_level",  "display_name": "VIP Level",  "type": "number",  "desc": "Current VIP level of the user",  "source": "chat",  "update_type": "user_set"}

update_type is one of: user_set (overwrite), user_setOnce (first-set-only), user_add (numeric accumulate), user_append (array append).

User identity fields (meta.user_identity):

{  "account_id_source": "user_account", // Account ID source: user_account / role_id / none  "account_id_field": "user_id",       // Account ID field name (only when user_account)  "distinct_id_strategy": "auto",      // Visitor ID strategy: auto / device_id / custom  "distinct_id_custom_value": null     // Custom visitor ID value description (only when strategy=custom)}

Property types (enum): string / number / bool / datetime / object (single object, with sub-properties) / array_row (object array, supports parent.child nesting) / array_string (string array)

Naming rules: Property names must be snake_case; event names are lowercase by default, and uppercase is kept only when the user asks to preserve it. Use display_name for human-readable names.

1.2 Merge Source Materials

Merge order: existing_plan → template → codebase → prd → chat → autotrack

Earlier sources take precedence — same-name events keep the earlier version, later sources only add new events or merge prop_names without overwriting.

• existing_plan: Already imported and validated in Phase 0 (see "Modify Existing Tracking Plan Flow"). Events are in draft.json as the baseline; each item marked source: "existing_plan". Higher-priority sources supplement with new events only; same-name events keep the existing_plan version.
• template: User-selected industry template (see "Template Lookup Convention" below) as baseline; each item marked source: "template"
  • Templates are resolved by ae-cli from the ae-cli package root and user template directory
  • Import command: AE_LANG=<user_lang> ae-cli tracking code import-template --template-name "<template name>" --out .ae-cli/draft.json
  • ⚠️ Must validate immediately after template import (see Phase 1.6); template content may not be fully correct
  • ⚠️ Do not manually translate template content after import: Do NOT read draft.json and model-translate display_name, event_desc, event_tag, or property display_name/desc. Keep imported business content as produced by the CLI/template reader unless the user explicitly asks for semantic rewriting.
  • ⚠️ Use src/tracking/i18n for localization owned by the CLI: AE_LANG=<user_lang> + draft.meta.lang control CLI messages, xlsx sheet names, xlsx headers, property type display values, and auto-track/i18n-owned labels. If these are wrong, inspect the existing translations under src/tracking/i18n, then regenerate with the intended locale instead of editing labels by hand.
  • ⚠️ No model-invented translations for template labels: When replacing or explaining a localized template-owned label, use the exact value from src/tracking/i18n resources. If no corresponding resource exists, preserve the template text and ask the user before changing semantics.
  • ⚠️ event_tag is not free-form model translation: Do not manually map 业务事件/系统事件 to another language. Preserve template tags, or rely on src/tracking/i18n and autotrack generation for system labels when the CLI owns them.
• codebase: Scan project source directory, extract events/properties from business logic; same-name events merge prop_names without overwriting existing fields; new items source: "codebase"
• prd: Read all user-provided product documents (md / pdf / docx / xlsx / pptx / URL / images), extract events and properties from each file; same-name events merge prop_names without overwriting existing fields; image files analyzed via multimodal interpretation of UI elements and interaction flows; all new items source: "prd"
  • Read each format with the table below. Preferred tool first; when it is missing, fall back rather than fail the read.

    Format	Read via
    md	read directly
    docx	pandoc -t markdown <file>; fallback markitdown <file> (pip install markitdown if missing); last resort unzip -p <file> word/document.xml and read the text
    pdf (text)	extract text (native Read or a PDF text extractor)
    pdf (scanned)	render pages to images, then read with vision
    xlsx	read rows/columns with a structure-preserving reader (openpyxl / pandas, pip install if missing); a tracking table's row/column layout carries meaning — do NOT rely on a flattened markdown dump
    pptx	markitdown <file> (pip install markitdown if missing)
    png/jpg/jpeg/webp	multimodal interpretation, analyze UI elements and interaction flows

  • xlsx is a third source-material path, distinct from the two existing xlsx flows. A human-readable tracking table (event / property / type rows) is read row-by-row here. An AE-format tracking-plan xlsx goes through import-template; a CSV/Excel data sample goes through the data path (ae-cli data-integration inspect). Never route one into another's flow.
  • prd path is a folder: Recursively scan all files in the directory:
    • md/pdf/docx/xlsx/pptx → read per the table above, extract events/properties
    • png/jpg/jpeg/webp → multimodal interpretation, analyze UI elements and interaction flows
    • subdirectories → recurse
    • other files → skip
  • prd path is a URL: Fetch URL content directly, process by the same rules above
• chat: Anchor phase business scenario + refine phase edit instructions, source: "chat"
• autotrack: Auto-inject SDK auto-track events based on meta.client_sdk_type (only for client_only or both mode), source: "autotrack"

1.3 Inject Business Dimension Events

Based on meta.business_dimension collected in Phase 0, inject corresponding events by the following rules.

Revenue model → Required events:

Core loop → Event sequence:

Parse node actions from user's core_loop description, map to events:

Example: "Players repeatedly clear stages to earn coins, use coins to gacha for heroes" → Stage module: stage_start (stage begin), stage_complete (stage clear), stage_fail (stage fail) → Resource gain: token_get (coin gain, props: token_type=diamond, token_amount) → Gacha module: gacha_draw (gacha pull), pool_type (pool type), draw_count (draw count) → Hero gain: hero_get (hero acquired), hero_id

Functional entries → Module event groups:

Currency system → Property design:

Injection rules:

1. Business dimension events marked source: "business_dimension"
2. When merging with source material events, same-name events keep the source material version, do not overwrite
3. When revenue model is none (no monetization), skip revenue-related event injection

1.4 Auto-inject SDK Auto-track Events

Based on SDK integration mode collected in Phase 0, decide whether to inject auto-track events:

Injection conditions:

• sdk_integration_mode === "client_only" → inject auto-track events
• sdk_integration_mode === "both" → inject auto-track events (client side only)
• sdk_integration_mode === "server_only" → do NOT inject (server SDKs have no auto-track)
• sdk_integration_mode === "none" → do NOT inject (no SDK; data ingestion via other methods)

Injection rules:

1. Only inject recommended events; optional events are not auto-injected (prompted in Refine phase for optional enablement)
2. Auto-track events placed at the end of events array, marked source: "autotrack"
3. Auto-track event event_tag set to "System Event"
4. Auto-track events only carry preset properties (prop_names is empty or contains only preset property names)
5. Preset properties prefixed with # are not added to event_properties pool (auto-collected by SDK)
6. Cleanup + Deduplication: The CLI will:
   • Remove auto-track events inherited from templates or existing plans that don't match the user's selected SDKs. For example: if a template built for Android/iOS contains ta_app_install, ta_app_start, ta_app_end but the user selects JavaScript SDK, those ta_app_* events will be automatically removed since JavaScript SDK does not support them.
   • Inject the correct auto-track events for the user's selected SDKs.
   • Deduplicate by event name globally — won't inject events that already exist in the draft (correct auto-track events inherited from templates are kept).

SDK type → Recommended events (see references/autotrack-events.md for details):

Auto-track event purpose notes:

• Auto-track events are the SDK's built-in auto-reporting mechanism; you do not need to manually define same-name events
• Example: JavaScript SDK's ta_page_show auto-collects page views; no need to define home_page_show, about_page_show etc.
• If templates already contain auto-track events (e.g. ta_app_install in industry templates), CLI will not inject duplicates
• These events require enabling corresponding switches during SDK initialization in the ae-generate-tracking-code phase

Draft JSON example:

{  "event_name": "ta_app_install",  "display_name": "App Install",  "event_desc": "Triggered on first app install; upgrades do not trigger; reinstall after deletion triggers",  "event_tag": "System Event",  "platform": "client",  "prop_names": [],  "source": "autotrack"}

Note: Auto-track event platform is always "client", because only client SDKs have auto-track capability.

1.5 Persist + Generate xlsx

Must write draft.json first, then run draft command. Do not skip this step and run ae-cli tracking plan draft directly.

• Save draft to .ae-cli/draft.json
• ⚠️ Write meta.lang: Set draft.meta.lang based on user's current language (zh/en/ja/ko), ensuring generated xlsx headers / sheet names / type values match the AE platform language
• Must verify file was updated after writing (check file modification time or content); only generate xlsx after confirming new content
• Generate upload-ready xlsx:

AE_LANG=<user_lang> ae-cli tracking plan draft --in .ae-cli/draft.json --out .ae-cli/draft.xlsx

1.6 Rule Validation (must execute)

Auto-validate during xlsx generation to ensure compliance with AE tracking plan rules:

AE_LANG=<user_lang> ae-cli tracking plan draft --in .ae-cli/draft.json --out .ae-cli/draft.xlsx --fix

Validation rules:

Validation flow:

1. CLI auto-validates draft.json
2. Fixable issues found → auto-fix → update draft.json → generate xlsx
3. Non-fixable issues found → error; manual fix of draft.json needed
4. No issues → proceed to Phase 1.7

Note: Display names can be the same across different property pools (e.g. vip_level can be both an event property and a user property).

Relationship to Phase 0 existing_plan validation: The underlying rule engine is the same, but Phase 0 uses interactive 3-tier (Minor/Medium/Severe) because the user is present to confirm each fix. Phase 1.6 uses batch 2-tier (auto-fixable / manual-fix-needed) because it runs as part of the automated draft generation. Rules that are "Medium (needs confirmation)" in Phase 0 appear as "❌ Manual fix needed" here — the same rule, just without the interactive prompt.

1.7 Show Summary

Display to user via markdown table: event count / event property pool size / super property count / user property count; show deliverable paths.

After displaying, tell user:

Phase 1 complete.Next: Phase 2 — Refine to confirm the plan.

📁 Template Lookup Convention

Run the following command to dynamically discover available templates:

AE_LANG=<user_lang> ae-cli tracking plan list-templates --json

Language rules: Template names and template business content must not be model-translated. Use localized names only when they are returned by the CLI or found in src/tracking/i18n resources. If list-templates --json only returns the original template name, display that name as-is and keep it unchanged for import. Before presenting or modifying any localized template-owned label, look it up in src/tracking/i18n; do not invent a translation.

Built-in templates are resolved by ae-cli from the ae-cli package root. User templates are resolved from the ae-cli user template directory. Do not manually construct ./tracking-plan-template/... paths from the user's current workspace.

Search directories in order:

1. <ae-cli package root>/tracking-plan-template/ — bundled templates
2. ~/.ae-cli/templates/ — user-provided template directory

Each template prefers .md distilled file (if same-name .md exists, return md path; otherwise return xlsx path). Display the template names returned by the CLI, and keep the exact name from the JSON result for import. Auto-detect format on import:

AE_LANG=<user_lang> ae-cli tracking code import-template --template-name "<template name>" --out .ae-cli/draft.json

Phase 2 — Refine (5-segment loop)

Data path (source_type = data): skip this 5-segment loop entirely — use the single confirmation gate defined in "Data-path (source_type = data)" instead.

In order, one conversation round per segment:

1. sdk_config (SDK config + User identity, combined) — Show SDK integration mode, platform/language, visitor ID strategy, account ID source, corresponding SDK calls
2. business (Business dimension + Business events, combined) — Show revenue model, core loop, functional entries, injected event modules (grouped by platform)
3. autotrack (Auto-track events) — Show SDK auto-track events in a separate table, note enablement method
4. common_props (Super properties) — Show all super properties, note usage scenarios and considerations
5. props (Event properties + User properties) — Show event property pool grouped by event + user properties table

Per-segment flow:

1. Display corresponding section of current draft
2. Ask a segment-specific confirmation question. Always include the current segment number, current segment key, and next segment key:
   text

   Segment <n>/5 <segment_key> confirmed? Reply ok to continue to Segment <n+1>/5 <next_segment_key>, or describe changes.

   For Segment 5:
   text

   Segment 5/5 props confirmed? Reply ok to archive the plan and continue to Phase 3, or describe changes.

3. User gives natural language instructions → update .ae-cli/draft.json → re-run:
   bash

   AE_LANG=<user_lang> ae-cli tracking plan draft --in .ae-cli/draft.json --out .ae-cli/draft.xlsx

4. User ok → proceed to next segment

ok is a refine state-machine input, not a repeated-message error. If the user replies ok multiple times in a row, advance exactly one segment per ok in order. Before each confirmation prompt, print the new segment heading first, so consecutive confirmations do not look like the same question repeated.

User may say "Go back to segment N" at any time to jump to any segment (N = 1-5).

sdk_config (Phase 2 Segment 1)

Show SDK integration config + user identity system:

SDK Integration Config:- Integration mode: <client_only / server_only / both / none>- Client: <platform> (<language>)- Server: <language>
User Identity Config:- Account ID source: <user_account / role_id / none>- Account ID field: <specific field>- Visitor ID strategy: <auto / device_id / custom>

User ok / modify.

business (Phase 2 Segment 2)

Show business dimensions + business events:

Business Dimensions:- Revenue model: <IAA / IAP / mixed / subscription / commission>- Core loop: <description>- Functional entries: <list>- Currency system: <hard currency / soft currency>
Injected Event Modules (grouped by platform):
Client events (platform=client):- <event>: <display_name> — <event_desc>- ...
Server events (platform=server):- <event>: <display_name> — <event_desc>- ...
Both-platform events (platform=both):- <event>: <display_name> — <event_desc>

Conflict detection: If business dimensions contradict source materials, prominently flag for user confirmation.

User ok / modify.

autotrack (Phase 2 Segment 3)

Only shown for client_only or both mode.

Display SDK auto-track event list, with notes:

• These events are auto-collected by the SDK; no manual track() calls needed during code generation — just enable corresponding switches during SDK init
• display_name or event_desc can be adjusted; event names cannot be changed

User ok / modify.

common_props (Phase 2 Segment 4)

Show all super properties (name / display_name / type / desc).

Notes:

• Super properties are attached to every event; ideal for business-wide global dimensions
• Common super properties (by app type):
  • H5/Web: channel (source channel), referrer_domain (referring domain)
  • Mobile App: channel, app_version, platform
  • Game: channel, vip_level, server_id
  • Mini-program: channel, scene
• Prohibited: Do NOT set SDK preset properties (# prefix) as super properties

User ok / modify.

props (Phase 2 Segment 5)

Show event property pool (grouped by event) + user properties table:

• Event properties: name / display_name / type / desc, grouped by event_tag
• User properties: name / display_name / type / update_type / desc

User property update methods:

User ok → immediately execute archive command, then proceed to Phase 3.

Refine Phase Heuristic Suggestions

• Super properties vs Event properties: Property appears on 3+ events → promote to super property; super properties are suitable for business-wide global dimensions (channel, vip_level, ab_test_group)
• Prohibited: Do NOT set SDK preset properties (# prefix) as super properties
• Events must have properties: Every event must have at least one semantically meaningful, describable property
• Nested properties: array_row parent properties have parent.child sub-properties describing a group of objects

Post-Phase 2 — Pre-delivery Self-check

⚠️ Before uploading to AE, must complete the following self-check. Fix any issues before uploading.

Naming Convention Check

• Do event/property names start with a letter?
• Do event/property names contain only letters, digits, and underscores (no Chinese, no spaces)?
• Are there duplicate event names or synonymous events coexisting (e.g. order_create and create_order)?
• Does the same property name map to multiple display names or types?
• Does every event, event property, common event property, and user property have a non-empty display_name in the user's language?

Revenue Model Required Events Check

Paired Event Consistency Check

Start/end paired events (e.g. battle_start/battle_end) must carry same-name, same-structure object arrays:

• Object array sub-properties reported by start event must be same name and same type in end event
• Check: stage pairs (stage_start/stage_complete), battle pairs (battle_start/battle_end), gacha pairs (gacha_draw/hero_get), etc.

Unit Description Check

• Are monetary fields annotated with unit (cents/USD)?
• Are duration fields annotated with unit (seconds/milliseconds)?
• Are balance fields annotated as post-recharge balance or pre-operation balance?

Enum Value Check

• Are enum values listed in event description (≤ 10 values)?
• For > 10 values, is there a note to use a dimension table?
• Is the null-value fallback strategy documented (e.g. "unknown channel → use unknown")?

Object Array Usage Check

Only use object arrays (array_row) when ALL THREE conditions are met; otherwise use object or plain properties:

1. An event property has multiple same-type entities to record
2. Each entity needs ≥ 2 properties recorded
3. Entity count is variable

Object Usage Check

Use object (object) when the following condition is met; distinguish from object arrays:

• One-to-one relationship → use object: e.g. user's current "equipment" details, player's "current deployed hero" (only one)
• One-to-many relationship → use array_row: e.g. "backpack items" list, "lineup heroes" list (multiple)

Quick rule: data shaped like {...} → use object; data shaped like [{...}] → use array_row.

Post-Phase 2 — Archive

After all 5 Refine segments are confirmed (user ok on Segment 5), archive immediately; do not skip or delay:

AE_LANG=<user_lang> ae-cli tracking plan archive --draft .ae-cli/draft.json --xlsx .ae-cli/draft.xlsx --name "<plan_name>"

Output lands at plans/<date>-<plan_name>.xlsx; draft.json is updated with meta.archived_at.

After archiving, tell user:

✅ Archive completeFile path: plans/<date>-<plan_name>.xlsx
Next: Phase 3 — Upload to AE:1. Login to AE to get token2. Get AE project ID3. Upload plan to AE

⚠️ Hard rule: Archive must complete before entering Phase 3. Before Phase 3.1's first question, must confirm meta.archived_at exists.

Phase 3 — Token & projectId

At the start of Phase 3, tell user:

## Phase 3 — Upload PreparationNext steps:1. Check active AE host and login status2. Login to AE to get token if needed3. AE project ID

3.1 Check Active AE Host and Login Status

Do not ask for the AE web address first. ae-cli stores an active AE host, and auth commands can use it directly.

First check current auth/host status:

ae-cli auth status

If an active host is configured, save that host to .ae-cli/draft.json meta.host. If auth status reports authenticated: true, skip login and continue to project ID.

Only if ae-cli reports no active host / no AE host configured, ask the user:

"What is the AE web address?"

After user responds, configure it and save the same value to .ae-cli/draft.json meta.host:

ae-cli config set-host <host>

If auth status reports unauthenticated, use the agent split-flow. Do not run blocking ae-cli auth login directly from an AI agent.

Step 1 — request an authorization URL and return control to the user:

ae-cli auth login --no-wait

Show the returned verification_url to the user and ask them to complete authorization. Keep the returned device_code for the next step.

Step 2 — after the user says authorization is complete, finish login:

ae-cli auth login --device-code <device_code>ae-cli auth status

Do not retry with ae-cli auth login --host <host> unless the previous command explicitly failed because no active host was configured. In that case, configure the host first, then restart the split-flow with --no-wait.

Common error tips and self-recovery:

Token cached for 20 hours; same host avoids re-auth.

3.2 Get AE Project ID and Update Draft

Ask user: "What is the AE project ID? Go to AE Admin → 'Project Settings' → 'Integration Config' → copy 'Project ID', or check the AE system URL parameter currentProjectId=<id>"

After user provides projectId, update .ae-cli/draft.json meta.project_id.

Phase 4 — Upload

At the start of Phase 4, tell user:

## Phase 4 — Upload to AEChecking project's existing plan...

4.1 Check Project's Existing Plan

Before uploading, check if the project already has a tracking plan:

AE_LANG=<user_lang> ae-cli tracking plan fetch --project <projectId> > .ae-cli/existing-plan.json

Do not add --host here unless the user explicitly provides a reachable override for this command. In agent sandboxes, ae-cli can resolve the request host from the sandbox-provisioned cli-token.json; passing a stale Kubernetes internal host can bypass that fallback.

Result assessment:

• File empty or command error 404 → project has no plan; upload directly
• File has content → project has an existing plan; show summary + conflict detection

When existing plan exists, display:

Project already has a tracking plan:- Events: XX- Event properties: YY- Super properties: ZZ- User properties: WW
Choose upload mode:1. Append (keep existing plan, add new events/properties)2. Replace (delete existing plan, upload new plan)
Append / Replace?

4.2 Append Mode Conflict Detection

When user chooses "Append", must detect conflicts (AE merge-by-name has silent discard risk):

Read two files:

• Existing plan: .ae-cli/existing-plan.json
• New plan: .ae-cli/draft.json

Detect two types of conflicts:

Conflict Type A: Same-name property type mismatch (severe)

AE rule: Same-name properties must have the same type, otherwise reported data will be discarded.

Detection logic:

Compare event_properties / common_event_properties / user_properties three property pools:

• For each property in the new plan, find same-name property in existing plan
• If same name but different type → record as property_type_conflict (severe error)

Conflict display:

⚠️ Severe conflict: Same-name property type mismatch
The following properties have different types in the existing plan vs. new plan.Appending will cause reported data to be discarded:
| Property Name | Existing Type | New Plan Type ||---|---|---|| order_amount | number | string || vip_level | string | number |
Suggestions:1. Modify the new plan's property types to match the existing plan2. Or choose "Replace" mode to redefine types
Continue append (without fixing) / Modify draft / Switch to replace?

Conflict Type B: Same-name events (advisory)

AE merge-by-name: Same-name events are not overwritten; new-name events are added. Event names are case-sensitive (Purchase ≠ purchase) — changing only the case creates a new event, not a rename.

Detection logic:

For each event in the new plan, find same-name event in existing plan:

• If same-name event exists → record as event_exists (advisory, not an error)

Conflict display (advisory only):

⚠️ Advisory: The following events already exist in the project (append mode will not overwrite)
- user_login (existing: 2 properties, new plan: 3 properties)- order_create (existing: 5 properties, new plan: 5 properties)
After append:- Existing event property associations will not change- New properties for existing events will not be added- New events will be added normally
Continue append? yes / no

4.3 Upload Flow

Decide based on conflict detection results:

Upload command:

AE_LANG=<user_lang> ae-cli tracking plan upload --project <projectId> --xlsx .ae-cli/draft.xlsx --draft .ae-cli/draft.json --lang <user_lang> [--replace]

• With --replace: Delete existing project plan first then upload (when user chooses "Replace", or severe conflict switches to replace)
• Without --replace: AE merge-by-name merge (no conflicts, or advisory only with user confirmation to append)

Upload commands MUST pass --lang <user_lang> explicitly. --lang must match the generated xlsx language and draft.meta.lang; AE_LANG is only used for CLI messages and xlsx regeneration context. Do not call AE user language config APIs and do not use --switch-lang. If the xlsx language is wrong, regenerate the xlsx with the intended language before uploading:

AE_LANG=<user_lang> ae-cli tracking plan draft --in .ae-cli/draft.json --out .ae-cli/draft.xlsxAE_LANG=<user_lang> ae-cli tracking plan upload --project <projectId> --xlsx .ae-cli/draft.xlsx --draft .ae-cli/draft.json --lang <user_lang> [--replace]

On successful upload, prompt user to verify in AE Admin. Provide the full URL (tracking plan page URL format: https://<host>/#/data/plan).

Then read the uploaded plan back through ae-cli and synchronize its display names to any event/property metadata that already exists in the project:

AE_LANG=<user_lang> ae-cli tracking plan get --project-id <projectId> --host <host>AE_LANG=<user_lang> ae-cli tracking plan sync-display-names \  --project-id <projectId> \  --draft .ae-cli/draft.json \  --host <host>

sync-display-names is intentionally safe to rerun:

• It fills only blank event/property metadata display names.
• It never overwrites a non-empty display name already maintained in AE.
• missing_in_metadata means that the event/property has not appeared in project metadata yet; it is not an upload failure. Report those names and rerun the same command after the first Debug or production data reaches AE.
• missing_display_name_in_draft means the generated plan is incomplete. Add the missing localized display_name, regenerate/validate the xlsx, and rerun the upload/synchronization flow.

4.4 Upload Failure Handling and Auto-fix

Use --auto-fix option on upload (enabled by default); CLI auto-detects and fixes errors:

AE_LANG=<user_lang> ae-cli tracking plan upload --project <projectId> --xlsx .ae-cli/draft.xlsx --draft .ae-cli/draft.json --lang <user_lang> [--replace]

AE API Error Types

Auto-fix Flow

CLI auto-executes:

1. Upload xlsx to AE
2. Check if eventErrorMap has errors
3. Fixable errors → auto-fix draft.json → regenerate xlsx → re-upload
4. Loop up to 3 times; prompt user for manual intervention if exceeded

Example output:

🔧 Auto-fixing upload errors (attempt 1/3)...Fixed: Fixed object array sub-property inconsistency, Fixed display name duplicate[plan-upload] regenerated: .ae-cli/draft.xlsx

4.5 Post-success Actions

After successful upload and display-name synchronization, prompt user to verify in AE Admin. Provide the full URL (tracking plan page URL format: https://<host>/#/data/plan). Include a short synchronization summary: updated counts, preserved existing counts, and any names still missing from project metadata.

Ask about generating tracking code:

The tracking plan has been uploaded successfully. Would you like to generate tracking code next?

• Yes → guide user to use the ae-generate-tracking-code skill
• No → inform user of plan archive location: plans/<date>-<plan_name>.xlsx; can continue anytime

Prohibitions

• Asking all anchor questions at once
• Skipping Phase 3 and uploading directly
• Manually assembling xlsx bypassing .ae-cli/draft.json
• Translating "Super Property" as "超级属性" in any user-facing output (interaction prompts, plan summaries, event/property descriptions) — the correct AE Chinese term is "公共事件属性" or "公共属性"
• Calling fetch AE API directly within the skill — all AE communication must go through project scripts / CLI

Internal Reference (contributor use; not skill usage paths)

• skills/ae-generate-tracking-plan/references/te-api.md — AE backend endpoint capture documentation
• skills/ae-generate-tracking-plan/references/xlsx-schema.md — xlsx format contract (writer rules + reader compatibility)
• skills/ae-generate-tracking-plan/references/autotrack-events.md — SDK auto-track event definitions (per-platform event lists + SDK type mapping)
• skills/ae-generate-tracking-plan/references/business-dimension-mapping.md — Business dimension → event/property mapping table (revenue model / functional entries / currency system → injected events)
• src/plan/types.ts — Draft TypeScript type definitions