Menu
Get oriented with the solopreneur plugin โ see your AI team, check project status, and get suggestions for what to do next. Use when you're getting started or need a refresher.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Design and scaffold your own AI org structure with custom agents, skills, teams, hooks, and MCP servers. Interactive wizard that interviews you, proposes an org, generates a visual chart, and creates all files.
Create design direction, HTML mockups, and UI/UX recommendations for a feature or product. Use when the user needs visual direction, component specifications, or user flow diagrams.
Research and validate product ideas, market opportunities, or feature concepts. Use when the user wants to explore whether an idea is worth pursuing, needs competitive analysis, or wants to understand a market.
Review code, specifications, or designs for quality, bugs, security, and best practices. Use when the user wants feedback on recent work, a pull request, or any artifact.
Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.
Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.
| name | help |
| description | Get oriented with the solopreneur plugin โ see your AI team, check project status, and get suggestions for what to do next. Use when you're getting started or need a refresher. |
| argument-hint | optional: topic (skills, team, workflow, evals, getting started) |
The user wants to get oriented with the solopreneur plugin. Show them their AI team, where they are in the workflow, and what to do next.
If the user specified a topic, jump to the relevant section:
If no arguments, run the full onboarding experience (Steps 2, 4, 5). Do NOT auto-generate the org chart โ just mention it's available via /solopreneur:help team.
Check the .solopreneur/ directory to figure out where the user is in their journey. Scan in order:
No .solopreneur/ directory at all โ Brand new! Say: "Looks like you're just getting started. Your AI team is ready to go โ let's kick things off! Try /solopreneur:discover [your idea] to research and validate a product idea."
Has .solopreneur/discoveries/ with files but no .solopreneur/specs/ โ Say: "You've explored some ideas. Ready to turn one into a product spec? Try /solopreneur:spec [idea]"
Has specs but no .solopreneur/backlog/ โ Suggest /solopreneur:backlog [spec]
Has backlog with pending tickets but no .solopreneur/designs/ โ Suggest /solopreneur:design [feature] or /solopreneur:build depending on whether the project has a UI component
Has backlog with pending tickets โ Suggest /solopreneur:build [ticket] for single tickets or /solopreneur:sprint for parallel execution
Has built tickets (check backlog YAML for status: built or status: tested) โ Suggest /solopreneur:review
Has reviewed work โ Suggest /solopreneur:ship
Has shipped โ Suggest /solopreneur:release-notes [audience]
Present the suggestion conversationally: "Here's where you left off: [context]. I'd suggest [next step] โ want to do that?"
/help team)This step ONLY runs when the user explicitly asks for "team" (e.g., /solopreneur:help team). It is NOT part of the default onboarding flow.
Smart caching: Before generating, check if a cached org chart already exists:
.solopreneur/org-chart.html existsagents/ and skills/ directories (go up two directories from this SKILL.md to find the plugin root)open .solopreneur/org-chart.htmlGenerating the org chart:
The visualize-org.py script is at scripts/visualize-org.py relative to this plugin's root. Go up two directories from this SKILL.md (skills/help/SKILL.md โ skills/help/ โ skills/ โ plugin root) to find it.
mkdir -p .solopreneur && python3 <plugin-root>/scripts/visualize-org.py --plugin-dir <plugin-root> --marketing --output .solopreneur/org-chart.html && open .solopreneur/org-chart.html
Tell the user: "I've opened your AI team's org chart in your browser. It shows all your employees, what skills they handle, what tools they use, and how the workflow connects them. Click on any card for details."
If the open command fails (non-macOS), try xdg-open instead. If both fail, just tell the user the file path.
Present a compact reference:
Product Lifecycle (each step suggests the next):
/discover โ /spec โ /backlog โ /design โ /build โ /review โ /ship โ /release-notes
| Skill | What it does | Example |
|---|---|---|
/solopreneur:discover | Research and validate an idea | /solopreneur:discover meal planning app for busy parents |
/solopreneur:spec | Write a product requirements doc | /solopreneur:spec [discovery file or idea] |
/solopreneur:backlog | Break spec into prioritized tickets | /solopreneur:backlog [spec file] |
/solopreneur:design | Create UI/UX direction + HTML mockups | /solopreneur:design [spec or feature] |
/solopreneur:build | Plan or build a feature | /solopreneur:build [ticket or feature] |
/solopreneur:review | Multi-perspective quality review | /solopreneur:review recent |
/solopreneur:ship | Quality gate + deployment | /solopreneur:ship |
/solopreneur:release-notes | Audience-targeted announcements | /solopreneur:release-notes for twitter |
Team & Utility:
| Skill | What it does | Example |
|---|---|---|
/solopreneur:kickoff | Run a team meeting with multiple agents | /solopreneur:kickoff discovery sprint on [topic] |
/solopreneur:sprint | Build multiple tickets in parallel | /solopreneur:sprint |
/solopreneur:standup | Daily summary of recent activity | /solopreneur:standup |
/solopreneur:story | Turn your building journey into a narrative | /solopreneur:story blog post |
/solopreneur:scaffold | Design your own AI org from scratch | /solopreneur:scaffold "I am a freelance designer" |
/solopreneur:help | You're here! | /solopreneur:help skills |
Want to see your team visually? Run /solopreneur:help team to open the interactive org chart.
End with: "If you want to understand how skills, agents, hooks, or MCP servers work under the hood, just ask me directly โ I can look up the Claude Code documentation for you."
/help evals or /help testing)This step ONLY runs when the user explicitly asks for "evals" or "testing". It is NOT part of the default onboarding flow.
Present the eval system as a way to systematically improve skills:
What evals are:
Your plugin includes an automated testing system. Each skill has test cases that check whether it produces the right output. An LLM judge grades each test against specific expected behaviors.
Quick commands:
# See what tests exist (no cost โ just shows test cases)
bash evals/run-evals.sh --dry
# Run evals for a specific skill
bash evals/run-evals.sh [skill-name]
# Run all evals
bash evals/run-evals.sh
# Run all skills in parallel (faster for full suite)
bash evals/run-evals.sh --parallel
# Use a stronger model for more thorough testing
EVAL_MODEL=opus bash evals/run-evals.sh [skill-name]
The improvement loop:
bash evals/run-evals.sh [skill].eval-runs/[skill]/[test-id].judge.jsonAdding new test cases:
Each skill's eval.csv defines its tests. The format is:
id,should_trigger,prompt,expected_behaviors
should_trigger=true): Check the skill produces the right outputshould_trigger=false): Check the skill doesn't falsely triggerSee evals/README.md for detailed guidance on writing good test cases.