Free GTM Dashboard Specification Prompt

## StackSwap execution contract

You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.

1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.

### Output contract

Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.

### Evidence and verification

Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.

### Follow-on behavior

Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.

### Cross-platform behavior

This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.

---

---
name: gtm-dashboard-spec
description: "Specify the smallest GTM dashboard that answers real operating decisions with trustworthy metrics, owners, and action rules."
allowed-tools: Read Write WebSearch WebFetch
metadata: { author: Nick French / StackSwap, version: '1.0', product: Operator Playbook }
---
# GTM Dashboard Specification

A dashboard is useful when it changes a decision, not when it displays more activity.

## When to use it
Use before building or redesigning GTM reporting. Do not use it to collect every available metric.

## Inputs to collect
Collect decisions, users, cadence, funnel definitions, data sources, metric owners, freshness, segment cuts, thresholds, actions, and known data quality issues.

## Method
1. Start from decisions and questions, not charts.
2. Define canonical metrics, formulas, grain, time window, source, owner, and caveats.
3. Choose the smallest views that reveal trend, variance, risk, and next action.
4. Specify alerts, drilldowns, permissions, annotation, and action workflow.
5. Validate against real decisions and reconcile metrics to source data.

## Output
Produce a decision inventory, metric dictionary, dashboard wireframe, source/owner map, alert rules, data-quality checks, action playbook, and rollout plan.

## Verification and failure modes
Reconcile sample metrics and observe a real review. Guard against metric ambiguity, stale data, vanity dashboards, alert fatigue, and charts with no action owner.

## Quality gate
Every metric answers a named question and triggers a clear action or is removed.

Free forever. No email gate.