From pm-sidehustle
Set up a side business in the right order — the do-first sequence (separate money, basic terms, simple records) vs. the feels-official-but-waits list (logos, LLCs-by-default, office chairs), with the structure question framed honestly and routed properly. Use when asked I'm starting a side business what do I need, do I need an LLC, set up my side hustle properly, or what comes first legally and financially. Produces the ordered setup sequence, the structure-decision framing (jurisdiction-flagged, professional-routed), the money-hygiene rules, and the employer-conflict check most people skip.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-sidehustle:side-business-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
New side businesses fail setup in both directions: six weeks on a logo and an LLC for a business with zero customers, or a year of real revenue flowing through a personal checking account with no records, no terms, and a possibly-violated employment contract. The right order is boring and short: check the employer conflict *first*, separate the money *immediately*, get paid under simple written...
New side businesses fail setup in both directions: six weeks on a logo and an LLC for a business with zero customers, or a year of real revenue flowing through a personal checking account with no records, no terms, and a possibly-violated employment contract. The right order is boring and short: check the employer conflict first, separate the money immediately, get paid under simple written terms, keep records from dollar one — and let the structure question (sole proprietor vs. LLC vs. local equivalents) be decided when the facts justify it, with a professional, because it's jurisdiction- and situation-specific.
Ask for these if not provided:
[The clauses to reread · the equipment/hours rule · the found-a-conflict route]
[Money separation · the records file/sheet started · terms template readied]
[Registration steps as locally required (typed, verify-locally) · the tax-setaside % habit · insurance question if liability texture warrants (typed, professional-routed)]
[The honest trade table: sole-prop vs entity · this business's triggers, assessed · "ripe now" or "revisit at [milestone]" · route: local accountant/attorney]
[Logo, site polish, cards — after customer one]
Registration, tax, and entity rules are jurisdiction-specific — every flagged step needs local verification, and the structure decision deserves a local professional. Not legal or tax advice.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-sidehustleGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.