SimonTheSalesBooster

Decisiontree — Development skill for Claude Code

Development community

Decision Tree skill for Claude Code — interviews you relentlessly before building.

How to install Decisiontree

This entry records only its repository, not the path inside it, so there is no exact command to give. Open SimonTheSalesBooster/decisiontree and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Decisiontree does

Decision Tree skill for Claude Code — interviews you relentlessly before building.

Alternatives in Development

GenericAgent — Self-evolving agent: grows skill tree from 3.3K-line seed, achieving full system control with 6x less token co 6.1k ★
Godogen Source Repo — This repository contains two source trees for the same project: - claude/ — Claude Code source tree - codex/ 2.8k ★
Evo — turns your codebase into an autoresearch loop — discovers what to measure, instruments the benchmark, then run 1.4k ★

README

Decision Tree — AI Interviews You Relentlessly Before You Build Anything

**The reason most projects fail has nothing to do with execution.** It is that nobody asked the hard questions before building started. This Claude Code skill walks every branch of the decision tree, resolves dependencies, and produces a complete set of requirements in ~45 minutes — before a single line of code or copy is written.

[![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![Claude Code](https://img.shields.io/badge/works_with-Claude_Code-orange)](https://claude.com/claude-code) [![Strategy Sprints](https://img.shields.io/badge/built_by-Strategy_Sprints-red)](https://strategysprints.com)

The founder says "build me X." The team builds X. Three weeks later, everyone discovers that X required seven decisions nobody made.. and four of them contradict each other.

This skill eliminates that failure mode. It interviews you relentlessly — walking every branch of the decision tree, resolving dependencies one by one — until shared understanding is complete. Only then does building begin.

Who this is for

Technical founders who keep rebuilding the same feature because "it's not quite right"
Product managers running discovery before green-lighting scope
Consultants and coaches designing offers, courses, workshops, pricing structures
Agency owners scoping client projects to avoid the "that's not what I meant" moment at week 3
Solo developers who want an adversarial planning partner before committing 3 weeks

What happens when you run it

You describe what you want to build or figure out. Detailed or vague — both work.

Then the grilling starts.

Question after question. Each one walks a branch of the decision tree. Each one comes with a **recommended answer** — say "yes" to speed through the obvious ones, push back on the ones that matter. Dependencies surface. Contradictions get caught. Assumptions get named.

Sessions