Skip to content
Back to skills

Traction Review

ASecurity

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.

  • 3 stars
  • 0 votes
  • 0 copies
  • 7 views
  • Added September 12, 2026
ai-agentsgogitperformance

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add thedixitjain/the-mega-skill-library --skill traction-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Traction Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Traction Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedixitjain-traction-review/badge)](https://www.skillsdirectory.com/skills/thedixitjain-traction-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: traction-review
description: "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."
category: engineering-core
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/LVTD-LLC/skills/skills/traction-review/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/LVTD-LLC/skills/skills/traction-review/SKILL.md
---


# 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

```markdown
# 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.

---

**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/LVTD-LLC/skills/skills/traction-review/SKILL.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.