Workflow · Brew 9 · Moka pot

Launch a one-person product

Take a one-person product from plan to launch: pick the offer, build the site and code, write the policy pages, pass the release gate, then announce it.

The steps, in order.

  1. Step 1

    Solo Income Blueprint Turns “I want to make money online” into one plan: a business model that fits your skills, time and budget, one offer, a demand check, a minimal tool stack and a seven-day launch. unversioned

  2. Step 2

    Site Prompt Turns a website topic into one self-contained, paste-and-build prompt: it builds and verifies the site in a scratch folder first, then embeds every file verbatim with a pinned stack and the checks that actually ran. unversioned

  3. Step 3

    Production Code Delivers code as a finished artifact rather than a snippet: complete scripts, bug fixes with the root cause, reviews, API integrations and SQL, each with the run instructions and the edge cases handled. unversioned

  4. Step 4

    Paper Trail Privacy policy, terms, refund and cookie pages written only from facts you confirm, then checked for placeholders, missing sections and emails nobody supplied. Says when a lawyer should look. unversioned

  5. Step 5

    Release Gate · Chair One answer to “can we deploy?”: runs web-preflight, the security red team and the performance audit in order, keeps three separate verdicts, and computes HOLD or ready with a script instead of judgement. v0.1.0

  6. Step 6

    Platform Content Writes platform-native content packs from one brief: X threads, LinkedIn posts, YouTube and TikTok scripts, Instagram captions, newsletters and blog articles, each shaped to how that platform is actually read. unversioned

Step five is the whole of Brew 3 · Espresso; paper-trail gives the gate the policy pages to check.

Install the whole workflow.

npx skills add arm-pz/solo-income-blueprint                  # step 1
npx skills add arm-pz/site-prompt                            # step 2
npx skills add arm-pz/production-code                        # step 3
npx skills add arm-pz/caffeinity-skills --skill paper-trail  # step 4
npx skills add arm-pz/release-gate-chair                     # step 5
npx skills add arm-pz/platform-content                       # step 6

In Claude Code you can take every skill at once instead: /plugin marketplace add arm-pz/caffeinity-skills, then /plugin install caffeinity@caffeinity-skills. Not sure this is the right workflow? Install caffeinity-routing and describe the outcome; it picks one.

Other workflows.

Need this fitted to your team's own tools and rules? We build custom skills.