improve-business
Guided journey from a stalled, plateaued business to one with an honest diagnosis, a working operating rhythm, and offers repriced to real value. Orchestrates eight skills phase by phase - good-strategy-bad-strategy, traction-eos, high-output-management, team-topologies, drive-motivation, lean-analytics, negotiation, monetizing-innovation - asking the user questions at every decision point and recording results in the project docs/ folder (STRATEGY.md, OPERATIONS.md, METRICS.md, IMPROVE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a business that has
npx skills add wondelai/skills --skill improve-business --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guided, resumable journey for a business that runs but isn’t moving, spanning eight phases that diagnose before treating. It orchestrates eight skills phase by phase and asks the user questions at every decision point, recording results in project docs (STRATEGY.md, OPERATIONS.md, METRICS.md, IMPROVE-BUSINESS-PLAN.md) so the journey can resume across sessions. It requires the Claude Code tool.
How it works
- Starts by reading existing plan and artifacts; if a tracker exists, it summarizes state and asks which phase to enter. If no tracker, it Intake and creates docs/IMPROVE-BUSINESS-PLAN.md with phase statuses.
- Proceeds phase by phase, invoking each phase’s dedicated skill by its slug (e.g., good-strategy-bad-strategy, traction-eos, high-output-management, team-topologies, drive-motivation, lean-analytics, negotiation, monetizing-innovation).
- For each phase: announces purpose, asks concrete questions, and produces/extends an artifact in docs/ (uppercase filenames) with specified sections (e.g., STRATEGY.md, OPERATIONS.md, METRICS.md).
- Updates the tracker with phase status, Key Decisions, and Next Actions; a phase is marked done only after user sign-off on the draft artifact.
- Ensures diagnosis exists before any treatment phase; Phase 1 must confirm a Diagnosis in STRATEGY.md before Phase 2+ proceed.
When to use it
- Use when a business with real revenue and customers has a flat line or stalled growth and the user wants to diagnose and fix strategy and execution across multiple layers (strategy, execution, management, structure, motivation, metrics, margin, pricing).
- Suitable when starting from scratch with no customers (use create-business) or when fundamentals exist and expansion is the goal (use grow-business).
What it can touch
- Files: docs/STRATEGY.md, docs/OPERATIONS.md, docs/METRICS.md, docs/CUSTOMER.md, docs/OFFER.md, docs/IMPROVE-BUSINESS-PLAN.md
- Artifacts: STRATEGY.md, OPERATIONS.md, METRICS.md, IMPROVE-BUSINESS-PLAN.md
- Tool: claude-code
Caveats
- License: MIT
- Requires interaction: asks the user to decide at each phase and record results; phases can be deferred or skipped according to gating rules.
- The skill’s phases and artifacts must be created or extended in the docs folder as uppercase files; new content is added, existing content extended.
# Improve a Business An interactive, resumable journey for a business that already runs but has stopped moving — real revenue, real customers, a flat line. Across eight phases it works the layers in order (strategy, execution, management, structure, motivation, metrics, margin, pricing), diagnosing before treating rather than chasing one tactic at a time. The agent asks before every decision and records each choice in `docs/` so the turnaround survives across sessions. ## Core Principle **A plateau is a diagnosis failure: diagnose before treating, and work the layers in order — strategy, execution, management, structure, motivation, metrics, margin, pricing.** Poking one tactic at a time never breaks a plateau because the constraints compound. This skill sequences the phases, asks the decision questions, and records what was decided; the constituent skills carry the actual method — invoke them rather than improvising their frameworks. ## Journey Map | Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1 | good-strategy-bad-strategy | What single challenge is capping the business? | Creates docs/STRATEGY.md — GATE | | 2 | traction-eos | How do we execute the strate
- Core Principle
- Journey Map
- Operating Rules
- Intake
- Phases
- Phase 1 — Diagnose the real challenge (good-strategy-bad-strategy) — GATE
- Phase 2 — Install an execution rhythm (traction-eos)
- Phase 3 — Manage for output, not activity (high-output-management)
- Phase 4 — Reshape teams around value streams (team-topologies)
- Phase 5 — Re-motivate the people who checked out (drive-motivation)
- Phase 6 — Measure the one number that tells the truth (lean-analytics)
- Phase 7 — Stop leaking margin in negotiations (negotiation)
- Phase 8 — Reprice around delivered value (monetizing-innovation)
- Optional Phases
What does the improve-business skill do?
Guided journey from a stalled, plateaued business to one with an honest diagnosis, a working operating rhythm, and offers repriced to real value. Orchestrates eight skills phase by phase - good-strategy-bad-strategy, traction-eos, high-output-management, team-topologies, drive-motivation, lean-analytics, negotiation, monetizing-innovation - asking the user questions at every decision point and recording results in the project docs/ folder (STRATEGY.md, OPERATIONS.md, METRICS.md, IMPROVE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a business that has
How do I install it?
Run `npx skills add wondelai/skills --skill improve-business --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wondelai/skills, a repository with 1,835 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.