solo-dev-suite

Master orchestrator for the Solo Dev Suite — a collection of lifecycle skills (scope guardian, sprint planner, pricing architect, launch readiness, ADR generator, security audit, integration mapper, auto-docs, tech debt register, testing strategy) that share a central Project Profile. Triggers on requests like "solo dev suite", "run the suite on {project}", "set up a project profile", "what suite skills apply here", "show my projects", or any direct invocation of a child skill by name when no profile exists yet. Not for one-off tasks with no ongoing project — those stay as standalone skills.

Generates and maintains Architecture Decision Records (ADRs) in the Michael Nygard format -- numbered, sequentially stored Markdown docs capturing context, options considered, decision, and consequences. Triggers on "generate an ADR", "record this decision", "log architecture decision", "why did I choose X", "add an ADR", or "list my ADRs". Part of the solo-dev-suite -- loads the project profile via the orchestrator. Not for runtime config changes (those are just code) or meeting notes (use a wiki).

Generates and maintains project documentation (README, SETUP, ARCHITECTURE, CHANGELOG) by pulling from the profile and sibling sidecars. Re-runnable at every milestone so docs stay current without being a full-time job.

Scans a codebase for local-to-cloud migration blockers -- hardcoded paths, LAN URLs, dev-only bypasses, missing deploy configs -- and produces a scored readiness report. Triggers on "deploy readiness", "ready to deploy", "can I host this", "cloud migration check", "scan for local stuff", "deployment blockers". Part of the solo-dev-suite -- loads the project profile via the orchestrator. Unlike security-audit (a checklist), this skill actually reads code.

Generates a customized design-exploration loop prompt for an existing project by discovering its stack, domain, and aesthetic, then tailoring references and constraints accordingly. Triggers on requests like "design loop on {project}", "refine the UI of this project", "explore design directions for {project}", "make this look more polished", "visual refresh", "modernize the UI", or "UI audit". Not for greenfield design, CSS debugging, or single-component tweaks — requires a target directory with an existing UI surface to analyze.

Comprehensive feature-enhancement discovery skill. Points at any codebase — the current Claude Code workspace, a local source folder, or a Forgejo/Git repo URL — scans the full stack, inventories existing features, surfaces incomplete/stub work, then researches comparable apps and platforms to generate a prioritized list of value-add enhancements. Outputs a structured FEATURE_ENHANCEMENTS.md report. Trigger whenever the user says: "feature enhancement", "what features are we missing", "analyze my codebase for improvements", "compare to competitors", "what should I add next", "audit my app", "run the enhancement skill", "scan for TODOs and features", "what else should this do", or points at a project and asks for improvement ideas. Also triggers when user wants to know how their app stacks up against similar tools or what features competitors have that they don't.

Maps every third-party service the project depends on with 3-dimensional risk rating (blast radius, pricing exposure, deprecation risk), fallback plans, review cadence, and staleness detection. Triggers on "map my dependencies", "audit third-party services", "what am I depending on", "integration risk review", "add a service dependency", or "review my integrations". Part of the solo-dev-suite — loads the project profile via the orchestrator. Not for internal code dependencies (use tech-debt-register) or security-specific audits (use security-audit).

Pre-ship gate that produces a tailored launch checklist covering auth, error handling, legal, payment flow, email deliverability, performance, SEO, mobile, and monitoring — with severity-gated sign-off. Triggers on "launch readiness", "pre-ship check", "am I ready to launch", "go-live checklist", or "what's blocking launch". Part of the solo-dev-suite — loads the project profile via the orchestrator. Not for security audits (use security-audit) or documentation generation (use auto-docs).

Locks an MVP definition by sorting every feature into four buckets (LAUNCH-BLOCKING / POST-LAUNCH V1.1 / PARKING LOT / WON'T BUILD) with effort/impact scoring, then provides ongoing scope creep detection. Triggers on "lock the scope", "prioritize features", "MVP scope review", "am I creeping scope", "should I add feature X", "is this scope creep", or "rescope the project". Part of the solo-dev-suite -- loads the project profile via the orchestrator. Not for greenfield brainstorming (use the brainstorming skill) or tech architecture decisions (use adr-generator).

Designs a defensible SaaS pricing structure -- strategy (freemium/trial/paid), billing unit, tier count and content, psychological pricing, annual discounting, and launch vs steady-state pricing. Produces a versioned pricing model with change history and a rendered PRICING.md doc. Triggers on "design my pricing", "pricing strategy", "what should I charge", "tier structure", "iterate my pricing", "compare pricing", "am I pricing wrong". Part of the solo-dev-suite. Not for one-off "what's a fair price for X" questions (just answer those) or for non-SaaS monetization (ads, one-time sales, marketplaces).

Pre-ship security pass producing a prioritized findings list covering auth hardening, data exposure, secret management, and stack-specific checks. Triggers on "security audit", "security review", "security checklist", "am I leaking anything", "pre-ship security", or "check my security". Part of the solo-dev-suite -- loads the project profile via the orchestrator. Not a pentest -- a systematic "door-locked check" for solo devs.

Converts a backlog into realistic solo-dev sprints accounting for day job + family + surprise maintenance -- with velocity tracking, launch countdown, and honest capacity math.

Logs, categorizes, and prioritizes tech debt as it's incurred. Not a shame exercise -- a managed backlog with pay-down window recommendations and priority scoring.

Generates a right-sized, stack-aware testing strategy specifying what to unit test, integration test, E2E test, and manually test -- avoiding both under-testing and 100%-coverage dogma.

Takes a software product idea — described in plain text, a pitch document, a notes file, or a conversational description — and produces a comprehensive Market Feasibility Report. The report assesses the idea's viability across seven dimensions: technical, economic, legal/regulatory, operational, scheduling, market/commercial, and pricing strategy. This skill does NOT require a codebase. It works from an idea description alone, though it can optionally incorporate an existing repo, prototype, or design document if provided. Trigger phrases include: "feasibility study", "is this idea viable", "should I build this", "market feasibility", "can this work", "evaluate this idea", "assess this project", "business viability", "feasibility report", "will this sell", "is there a market for", or any time the user describes a software product concept and asks whether it's worth pursuing. This skill is also appropriate when the user pitches an idea and asks "what do you think?" — always consider whether a feasibility as

Analyzes a software product from a local folder path OR a GitHub URL and produces a comprehensive, structured pricing and marketing strategy report. Use this skill any time a user wants to price their software, evaluate monetization options, build a go-to-market strategy, or understand what their product is worth to different customer segments. Trigger phrases include: "price my software", "pricing strategy for my project", "how should I charge for this", "what should I sell this for", "marketing strategy for my app", "monetization plan", "help me price [product name]", or any time the user provides a GitHub URL or local folder and asks about pricing, selling, or monetizing. This skill is also appropriate when the user just shares a repo and asks "what do you think?" — always consider whether pricing guidance would be valuable in that context.