Traction Review

SkillDev tools

Review traction experiment results and recommend whether to double down, iterate, repeat Bullseye, or pivot. Use when analyzing growth test data, comparing channel performance, deciding if a channel moved the needle, or reassessing startup traction strategy.

Use Traction Review in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Traction Review and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Traction Review skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Traction ReviewStart free

What this skill tells your AI

The instructions your AI receives, as published by hashgraph-online/awesome-codex-plugins in plugins/LVTD-LLC/skills/skills/traction-review/SKILL.md and read by Ahel’s 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.

Signals

GitHub stars
1k
Forks
316
Last commit
Oct 2026
Advanced
Item type
skill
Key
traction-review
Source
github.com/hashgraph-online/awesome-codex-plugins