traction-test-planner
Design cheap, measurable traction tests from Traction for startup growth channels. Use when planning marketing experiments, middle-ring tests, A/B tests, acquisition test spreadsheets, channel validation, or growth experiment success criteria.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- traction-test-planner
- license
- MIT
- metadata
- { "tags": "traction,growth,experiments,marketing,analytics", "version": "0.1.0", "category": "Marketing", "displayName": "Traction Test Planner" }
- description
- Design cheap, measurable traction tests from Traction for startup growth channels. Use when planning marketing experiments, middle-ring tests, A/B tests, acquisition test spreadsheets, channel validation, or growth experiment success criteria.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 1
- 参考文档references/middle-ring-test-prompts.md3.1 KB
03 SKILL.md 正文
Traction Test Planner
Use this skill to design traction tests that create decision-quality evidence. It turns a candidate channel strategy into a scoped experiment with assumptions, metrics, budget, duration, and next-step rules.
Source Traceability
Primary source: Traction, chapters 3 and 4, plus the appendix.
- Chapter 3 defines the three core test questions for middle-ring channels. Authoring notes: converted lines 585-606.
- Chapter 4 distinguishes cheap channel tests from optimization and explains inner-ring testing. Authoring notes: converted lines 675-786.
- The appendix lists phase I test prompts for the 19 traction channels. Authoring notes: converted lines 3323-3372.
See middle-ring-test-prompts.md for paraphrased starter tests by channel.
Test Types
Middle-Ring Test
Use when validating whether a channel strategy could become the core channel. Keep it cheap, fast, and strategy-level.
Answer:
- Acquisition cost: what would it cost to acquire a customer?
- Reach: how many relevant customers may be available?
- Fit: are these customers desirable right now?
Inner-Ring Test
Use after a core channel is chosen. Inner-ring tests optimize the winning strategy or search for a better strategy inside the same channel.
Examples:
- Test a new audience, keyword group, offer, landing page, creative angle, or partner segment.
- Run A/B tests where traffic and measurement are already in place.
- Use other channels only as support for the core channel, not as competing strategies.
Workflow
1. State The Decision
Write the decision the test must enable. Good tests decide something specific:
- Continue, kill, or revise this channel strategy.
- Promote this channel into the inner ring.
- Scale spend, hold spend, or change audience.
- Choose between two channel strategies.
2. Write Assumptions
List the assumptions that must be true for the strategy to work.
Use this structure:
| Assumption | How Test Measures It | Kill Threshold |
|---|
3. Set Metrics
At minimum, include:
- Reach available.
- Conversion rate.
- Cost to acquire a customer.
- Customer quality or intent.
- Lifetime value estimate, if available.
If the user lacks analytics, include a setup step before the test. A test without tracking creates anecdotes, not evidence.
4. Bound Budget And Time
For early-stage tests, prefer less than one month and a small budget. If the user proposes a large test before there is evidence, reduce scope.
5. Define Outcomes Before Running
Every test needs decision rules:
- Double down when results beat the success threshold and customer quality is acceptable.
- Iterate when one metric fails but the channel shows a fixable signal.
- Kill when reach, cost, or customer fit cannot plausibly move the traction goal.
Output Format
# Traction Test Plan
## Decision
[What this test will decide.]
## Channel Strategy
- Channel:
- Strategy:
- Target customer:
- Stage:
## Assumptions
| Assumption | Measurement | Threshold |
|------------|-------------|-----------|
## Experiment Design
- Setup:
- Audience/source:
- Offer/message:
- Landing or conversion path:
- Budget:
- Duration:
## Metrics
| Metric | Target | Tracking Method |
|--------|--------|-----------------|
## Decision Rules
- Double down if:
- Iterate if:
- Kill if:
## Next Step After Test
[What to do for each likely outcome.]
Quality Bar
- Do not design tests that only measure vanity traffic.
- Do not optimize multiple variables before validating strategy-level promise.
- Make tracking explicit before the test starts.
- Prefer comparable metrics across channels.
- Call out when the test cannot plausibly move the user's traction goal.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.