Loading...
Loading...
Compare original and translation side by side
Files to check (in pipeline order):
1. gtm-context.md - Business context (written by gtm-analytics-audit on first run)
2. gtm-credentials.json - OAuth credentials (gtm-setup)
3. gtm-token.json - Auth tokens (gtm-setup)
4. gtm-config.json - Account/container IDs (gtm-setup)
5. audit-report.json - Codebase scan results (gtm-analytics-audit)
6. gtm-tracking-plan.json - Tracking specification (gtm-strategy)
7. gtm-implementation-log.json - What was built (gtm-implementation)
8. gtm-test-results.json - Test pass/fail (gtm-testing)
9. gtm-fix-guide.md - Fix instructions (gtm-fix-guide)
10. docs/gtm-event-schema.md - Technical docs (gtm-reporting)
11. docs/gtm-executive-summary.md - Stakeholder docs (gtm-reporting)gtm-tracking-plan.jsongtm-implementation-log.jsongtm-test-results.jsongtm-config.jsonFiles to check (in pipeline order):
1. gtm-context.md - Business context (written by gtm-analytics-audit on first run)
2. gtm-credentials.json - OAuth credentials (gtm-setup)
3. gtm-token.json - Auth tokens (gtm-setup)
4. gtm-config.json - Account/container IDs (gtm-setup)
5. audit-report.json - Codebase scan results (gtm-analytics-audit)
6. gtm-tracking-plan.json - Tracking specification (gtm-strategy)
7. gtm-implementation-log.json - What was built (gtm-implementation)
8. gtm-test-results.json - Test pass/fail (gtm-testing)
9. gtm-fix-guide.md - Fix instructions (gtm-fix-guide)
10. docs/gtm-event-schema.md - Technical docs (gtm-reporting)
11. docs/gtm-executive-summary.md - Stakeholder docs (gtm-reporting)gtm-tracking-plan.jsongtm-implementation-log.jsongtm-test-results.jsongtm-config.json=== GTM Pipeline Status ===
Project: [containerId from gtm-config.json, or "not configured"]
Last checked: [current timestamp]
--- Setup ---
[✓/✗] Business context gtm-context.md [found / not found]
[✓/✗] GTM credentials gtm-credentials.json [found / not found]
[✓/✗] GTM config gtm-config.json [found: acct/container IDs / not found]
--- Planning ---
[✓/✗] Analytics audit audit-report.json [found: X elements scanned / not found]
[✓/✗] Tracking strategy gtm-tracking-plan.json [found: X events, Y P0 / not found]
--- Implementation ---
[✓/✗] Implementation gtm-implementation-log.json [found: X tags created, last run [date] / not found]
--- Validation ---
[✓/✗] Test results gtm-test-results.json [found: X passed, Y failed / not found]
[✓/✗] Fix guide gtm-fix-guide.md [found / not found]
--- Documentation ---
[✓/✗] Event schema docs/gtm-event-schema.md [found / not found]
[✓/✗] Executive summary docs/gtm-executive-summary.md [found / not found]
--- Coverage ---
Events planned: [X from tracking plan, or "N/A"]
Events implemented:[X from implementation log, or "N/A"]
Tests passing: [X/Y, or "N/A"]=== GTM Pipeline Status ===
Project: [containerId from gtm-config.json, or "not configured"]
Last checked: [current timestamp]
--- Setup ---
[✓/✗] Business context gtm-context.md [found / not found]
[✓/✗] GTM credentials gtm-credentials.json [found / not found]
[✓/✗] GTM config gtm-config.json [found: acct/container IDs / not found]
--- Planning ---
[✓/✗] Analytics audit audit-report.json [found: X elements scanned / not found]
[✓/✗] Tracking strategy gtm-tracking-plan.json [found: X events, Y P0 / not found]
--- Implementation ---
[✓/✗] Implementation gtm-implementation-log.json [found: X tags created, last run [date] / not found]
--- Validation ---
[✓/✗] Test results gtm-test-results.json [found: X passed, Y failed / not found]
[✓/✗] Fix guide gtm-fix-guide.md [found / not found]
--- Documentation ---
[✓/✗] Event schema docs/gtm-event-schema.md [found / not found]
[✓/✗] Executive summary docs/gtm-executive-summary.md [found / not found]
--- Coverage ---
Events planned: [X from tracking plan, or "N/A"]
Events implemented:[X from implementation log, or "N/A"]
Tests passing: [X/Y, or "N/A"]--- Recommended Next Step ---
[CONDITION → RECOMMENDATION]:
Nothing exists → "Start with gtm-analytics-audit to scan your codebase and capture project context, then gtm-setup to configure GTM API access."
context + setup missing → "Run gtm-setup to connect your GTM account. API credentials are needed before any implementation."
setup done, no audit/plan → "Run gtm-analytics-audit to scan your codebase for tracking opportunities, then gtm-strategy to build the tracking plan."
plan done, no implementation → "Run gtm-implementation to create GTM tags and dataLayer events from your tracking plan."
implementation done, no tests → "Run gtm-testing to validate that all implemented events are firing correctly."
tests done with failures → "X tests failed. Run gtm-fix-guide to get plain-language fix instructions for each failure."
all tests passing, no docs → "Implementation complete. Run gtm-reporting to generate technical docs and stakeholder summary."
docs done → "Pipeline complete. Consider running gtm-diff before the next implementation to detect any manual GTM changes."--- Recommended Next Step ---
[CONDITION → RECOMMENDATION]:
Nothing exists → "Start with gtm-analytics-audit to scan your codebase and capture project context, then gtm-setup to configure GTM API access."
context + setup missing → "Run gtm-setup to connect your GTM account. API credentials are needed before any implementation."
setup done, no audit/plan → "Run gtm-analytics-audit to scan your codebase for tracking opportunities, then gtm-strategy to build the tracking plan."
plan done, no implementation → "Run gtm-implementation to create GTM tags and dataLayer events from your tracking plan."
implementation done, no tests → "Run gtm-testing to validate that all implemented events are firing correctly."
tests done with failures → "X tests failed. Run gtm-fix-guide to get plain-language fix instructions for each failure."
all tests passing, no docs → "Implementation complete. Run gtm-reporting to generate technical docs and stakeholder summary."
docs done → "Pipeline complete. Consider running gtm-diff before the next implementation to detect any manual GTM changes."--- Flags ---
[Only show if anomalies detected]
⚠ gtm-test-results.json is older than gtm-implementation-log.json
→ Tests may not reflect the latest implementation. Re-run gtm-testing.
⚠ gtm-tracking-plan.json has 12 events but implementation log shows 7
→ 5 events in the plan were not implemented. Run gtm-implementation to complete.
⚠ gtm-token.json exists but is more than 7 days old
→ OAuth token may have expired. Run gtm-setup to refresh credentials.--- Flags ---
[Only show if anomalies detected]
⚠ gtm-test-results.json is older than gtm-implementation-log.json
→ Tests may not reflect the latest implementation. Re-run gtm-testing.
⚠ gtm-tracking-plan.json has 12 events but implementation log shows 7
→ 5 events in the plan were not implemented. Run gtm-implementation to complete.
⚠ gtm-token.json exists but is more than 7 days old
→ OAuth token may have expired. Run gtm-setup to refresh credentials.