solopreneur

Solopreneur - Your Virtual AI Company

You're a solopreneur. You have ideas, ambition, and not enough hours in the day. What if you had a full team -- an engineer, designer, QA lead, researcher, business analyst, and content strategist -- available instantly, working in parallel, and remembering every decision you've ever made?

Solopreneur is a Claude Code plugin that turns Claude into a structured virtual company. Not a chatbot you ask questions to. A company with specialists, workflows, and institutional memory.

What Makes This Different

Specialists beat generalists. A QA agent whose entire job is finding bugs will find more bugs than asking Claude to "also check for errors." Each agent has a dedicated role, methodology, and toolset -- just like a real employee.

You don't need to know what to do next. Every skill suggests the next step when it finishes. Discover an idea, and it suggests writing a spec. Write a spec, and it suggests creating a backlog. The workflow guides you from idea to shipped product.

Two build modes. Generate a step-by-step plan and hand it to any coding agent (Cursor, Windsurf, Cline, Aider, or anything else), or have Claude build it directly. You choose per feature.

Your decisions are remembered. Every choice you make -- what you picked, what you rejected, and why -- is captured in a decision journal. Later, turn that journal into a publishable blog post, tutorial, or case study of your building journey.

Parallel execution. Sprint mode builds multiple features simultaneously, each in an isolated branch, with integrated QA review when they're done.

Design your own. Don't like the default team? Run /solopreneur:scaffold and design your own AI org from scratch -- custom agents, custom workflows, custom everything.

Quick Start

Install the plugin

In Claude Code (CLI or IDE extension), run:

/plugin marketplace add pcatattacks/solopreneur-plugin
/plugin install solopreneur@solopreneur

The first command registers the marketplace. The second installs the plugin. You'll be asked to choose a scope (user, project, or local).

Or clone and use from source

git clone https://github.com/pcatattacks/solopreneur-plugin.git
cd solopreneur-plugin
claude --plugin-dir .

First command

/solopreneur:help

This opens an interactive org chart of your AI team and shows you where to start based on your project's current state.

How It Works

The Product Lifecycle

Solopreneur follows a structured pipeline from idea to shipped product. Each step feeds into the next:

/discover  -->  /spec  -->  /backlog  -->  /design  -->  /build  -->  /review  -->  /ship  -->  /release-notes

Here's what that looks like in practice:

1. Discover -- You have an idea. Your researcher and business analyst investigate the market, competitors, and viability.
2. Spec -- The idea has legs. Your team writes a product requirements document with technical feasibility checks.
3. Backlog -- The spec is broken into prioritized, dependency-tracked tickets with acceptance criteria.
4. Design -- Your designer creates user flows and interactive HTML mockups with DaisyUI + Tailwind.
5. Build -- Pick "plan only" (for Cursor/Windsurf/etc.) or "build directly" (Claude writes the code). Either way, a plan file is saved for reference.
6. Review -- Your engineer, QA, and designer review what was built from their respective angles.
7. Ship -- Quality gate, deployment setup, and pre-launch checklist. Your QA agent runs final checks.
8. Release Notes -- Audience-targeted announcements: Twitter, blog, changelog, investor update -- you name it.

You don't have to follow the pipeline linearly. Skip steps, jump ahead, or start wherever makes sense.

Alternate Paths

• Sprint -- Have multiple tickets ready? Sprint mode builds them in parallel, each in an isolated branch, with QA review built in.
• Kickoff -- Need your agents to debate an idea? Run a team meeting where agents challenge each other's assumptions in real time.

Two Build Modes Explained

When you run /solopreneur:build, you're asked how you want to proceed:

Plan only: Claude's engineer creates a detailed, step-by-step implementation plan. You take that plan to your preferred coding agent (Cursor, Windsurf, Cline, Aider, or any tool that can follow instructions). When the code is written, come back and Claude's QA agent validates it against the acceptance criteria.

Build directly: Claude's engineer creates the plan for reference, then writes the code itself -- installing dependencies, creating files, the whole thing. Progress is reported after each step.