mcpField
T
traction-review

traction-review

github.com/lvtd-llcMarketing & growth160 installsUpdated 7w ago
Repository

About traction-review

traction-review is a marketing skill for evaluating completed traction tests and choosing a next step. It weighs results against thresholds and customer quality, including strong signals that headline metrics may miss.

Key features

  1. 01Review goals and growth stage
  2. 02Compare results with thresholds
  3. 03Assess customer quality
  4. 04Identify engagement bright spots
  5. 05Recommend a channel or market decision

Use cases

  1. 01Deciding whether to expand a tested channel
  2. 02Finding promising customer segments in test results
  3. 03Reconsidering positioning after weak traction

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lvtd-llc/skills --skill traction-review

After installing, type/traction-reviewin Claude Code to confirm it loaded.

Details

From the project README

Traction Review

Use this skill after traction tests have run. The goal is to turn results into a decision: focus, iterate, repeat Bullseye, or reconsider the product or market.

Source Traceability

Primary source: Traction, chapters 2-5. Authoring notes: converted lines 394-902.

Review Workflow

  1. Restate the traction goal and current growth stage.
  2. Compare results against the prewritten success and kill thresholds.
  3. Evaluate customer quality, not only volume.
  4. Decide whether the result moved the needle for the current stage.
  5. Identify bright spots: small customer groups with unusually strong engagement, conversion, retention, or willingness to pay.
  6. Recommend one decision:
    • double down on the core channel,
    • run inner-ring optimization,
    • run another middle-ring test,
    • repeat Bullseye with new information,
    • revisit product, market, or positioning.

Output Format

# Traction Review

## Goal And Context
- Goal:
- Stage:
- Test period:

## Results
| Channel/Strategy | Cost | Reach | Conversion | Customer Fit | Notes |
|------------------|------|-------|------------|--------------|-------|

## Decision
[Double down, iterate, repeat Bullseye, or revisit product/market.]

## Reasoning
- What moved the needle:
- What failed:
- Bright spots:
- Risks:

## Next Actions
1. [Action]
2. [Action]
3. [Action]

Quality Bar

  • Do not declare success from vanity metrics.
  • Do not pivot before checking bright spots and engagement evidence.
  • Do not keep secondary channels alive just because they somewhat worked.
  • Reassess the Critical Path after meaningful evidence.

Comments

Markdown supported