Tracking Group

Use this skill when the work starts from site-analysis.json and the goal is to produce approved pageGroups.

Inputs

• <artifact-dir>/site-analysis.json

Workflow

1. Read the current pageGroups and page inventory.
2. Group pages by business purpose, not just URL shape.
3. Present a concise table with group name, content type, URL pattern, and pages.
4. Default to a reviewable summary first: total groups, grouping logic, and a compact table. Do not dump raw URL lists unless the user explicitly asks for them.
5. Ask the user to confirm or adjust the grouping.
6. Record approval with:

./event-tracking confirm-page-groups <artifact-dir>/site-analysis.json

Required Output

Produce and share:

• updated <artifact-dir>/site-analysis.json
• updated <artifact-dir>/workflow-state.json

Closeout Style

• default to a page-group summary first: group count, grouping logic, and a compact group table
• keep the summary reviewable in chat; do not dump full raw URL lists unless the user explicitly asks
• list files and the next command only after the summary

Stop Boundary

Stop after page-group approval unless the user explicitly asks to continue into schema work.

A broad request such as "full workflow" or "全流程" does not count as page-group approval. Do not run ./event-tracking confirm-page-groups <artifact-dir>/site-analysis.json --yes on the user's behalf unless the user explicitly confirms the current page groups in the current turn.

Useful follow-up:

./event-tracking prepare-schema <artifact-dir>/site-analysis.json

References

• ../../references/page-grouping-guide.md
• ../../references/output-contract.md