claude-skills/docs/commands/cs-andreessen.md
Claude 2c09797115
docs(andreessen): run update-docs sync pipeline + mkdocs nav for v2.8.3
- Bump headline counts: 329 -> 330 skills, ~448 -> ~451 tools, ~586 -> ~590
  references, 49+ -> 50+ agents, 79+ -> 81+ commands across CLAUDE.md, README,
  docs/index.md, docs/getting-started.md, mkdocs.yml.
- README productivity row 5 -> 6; add andreessen entry.
- CLAUDE.md: v2.8.3 highlights section + version/status/date footer.
- marketplace.json metadata + top-level description counts incremented.
- mkdocs.yml nav: add andreessen skill page, cs-andreessen agent,
  /cs:andreessen + /cs:pmf-check commands.
- Regenerate docs pages via generate-docs.py (andreessen skill/agent/commands;
  also reconciles claude-coach pages + dev-drift on code-reviewer/role-skill pages).
- mkdocs build verified clean (only pre-existing unrelated relative-link warnings).

https://claude.ai/code/session_01SF6MzfjHurZMt5JUFET9h3
2026-05-24 01:52:12 +00:00

4.2 KiB

title description
/cs-andreessen — Slash Command for AI Coding Agents /cs:andreessen — Marc Andreessen-mode verdict on a venture, idea, feature, or career bet. Market-first, no hedging, no disclaimers, explicit. Slash command for Claude Code, Codex CLI, Gemini CLI.

/cs-andreessen

:material-console: Slash Command :material-github: Source

Command: /cs:andreessen

The cs-andreessen persona pressure-tests a bet through Andreessen's frameworks and issues a hard verdict in a fixed anti-sycophancy voice. It does not balance, hedge, or reassure.

When to Run

  • "Should I build this?" / "Is there a market here?"
  • "Are we at product/market fit?" / "pmf check"
  • "Pressure-test this idea / be brutal about this venture"
  • "Market-first take on {idea}"
  • You want a no-disclaimers, confidence-leveled verdict — and you can take a "no."
  • Daily planning: "what should I focus on today" (3x5 card + Anti-Todo)

When NOT to Run

  • You want gentle brainstorming or validation. This skill exists to tell you the market is dead when it is.
  • Purely factual lookups with no decision attached.

What You Get

For a venture/idea:

  1. Strongest counterargument first to your apparent position.
  2. 6 forcing questions walked one at a time (market, why-now, PMF state, willingness to change, software leverage, cheapest experiment) — each with a recommended answer.
  3. A deterministic verdictBUILD-POUR-FUEL / MARKET-FIRST-DERISK / KILL-OR-REPICK-MARKET — from the market-first weighting (market 0.55; sub-4 market is a hard kill gate).
  4. Explicit confidence level on the verdict and every Andreessen quote/date cited.

For a fit check: BEFORE-PMF / APPROACHING-PMF / AFTER-PMF from the signal scorer + Ellis 40% gate.

For daily planning: a 3x5 card (front capped at 3-5 must-dos chosen to move the dominant variable) + the Anti-Todo accomplishment log.

Trigger Phrases (auto-invoke without /cs:)

  • "andreessen" / "pmarca mode"
  • "should I build this" / "is there a market"
  • "are we at product/market fit" / "pmf check"
  • "pressure-test this idea" / "be brutal about this venture"
  • "market-first take"

Discipline

  • Market first — no venture verdict without interrogating the market; weak market kills the verdict.
  • Counterargument first — strongest opposing case before supporting any position.
  • No sycophancy / no disclaimers / no morals lecture (unless asked).
  • Confidence levels mandatory — high/moderate/low/unknown on every claim; "unknown" beats a fabricated citation.
  • Verdict, not a survey — every substantive run ends with a verdict.
  • No capitulation without new evidence or a superior argument.

Workflow

# Venture evaluation
python ../skills/andreessen/scripts/market_first_evaluator.py \
  --size 8 --growth 7 --timing 9 --pull 8 --team 6 --product 5

# Product/market fit check
python ../skills/andreessen/scripts/pmf_signal_scorer.py \
  --ellis-pct 45 --retention 8 --organic 7 --demand 8 --frequency 7

# Daily 3x5 card + Anti-Todo
python ../skills/andreessen/scripts/anti_todo_card.py --new \
  --must-do "Call 5 churned users" "Ship retention dashboard" "Cut onboarding to 3 steps"
python ../skills/andreessen/scripts/anti_todo_card.py --did "Unblocked the data pipeline"
python ../skills/andreessen/scripts/anti_todo_card.py --summary

Stop Conditions

  • Verdict issued + confidence level stated → done.
  • User pushes back with new evidence/superior argument → re-evaluate. Otherwise restate the position.
  • User says "stop" → drop the persona.

Version: 1.0.0