# 🧩 Workflow Recipes > **Skills you can chain.** A recipe runs several skills in sequence and *passes each output forward as context* for the next β€” so a fuzzy idea comes out the other end as a finished, joined-up set of artifacts. No other skills library chains across professions like this. Run one as a slash command in Claude Code (e.g. `/ship-a-feature a referral program for B2B users`), or fetch it over MCP with the `get_workflow` tool. There are **9 recipes** today: | Recipe | Command | Lifecycle | Chains | |--------|---------|-----------|--------| | **Ship a Feature** | `/ship-a-feature` | Discover β†’ Decide β†’ Build β†’ Ship | 5 skills | | **Close the Quarter** | `/close-the-quarter` | Measure β†’ Communicate | 4 skills | | **Launch a Product** | `/launch-a-product` | Decide β†’ Ship | 5 skills | | **Rescue an Account** | `/rescue-an-account` | Measure β†’ Communicate | 4 skills | | **Run Discovery** | `/run-discovery` | Discover β†’ Decide | 4 skills | | **Repurpose Content** | `/repurpose` | One source β†’ many platforms | 3 skills | | **Launch an AI Feature** | `/launch-an-ai-feature` | Spec β†’ Design β†’ Evaluate β†’ Budget β†’ Document | 5 skills | | **Grow a Product** | `/grow-a-product` | Diagnose β†’ Experiment β†’ Retain β†’ Nurture | 4 skills | | **Land a Job** | `/land-a-job` | Decode β†’ Research β†’ Apply β†’ Interview | 4 skills | ## Ship a Feature β€” `/ship-a-feature` *Discover β†’ Decide β†’ Build β†’ Ship* Β· Take a raw feature idea from fuzzy brief all the way to a launch plan, end to end. `ambiguity-resolver` β†’ `prd-template` β†’ `rice-prioritisation` β†’ `roadmap-narrative` β†’ `go-to-market` 1. **ambiguity-resolver** β†’ produces a sharp problem statement and scoped boundaries. 2. **prd-template** β†’ produces a full PRD with goals, requirements, and success metrics. 3. **rice-prioritisation** β†’ produces a RICE score positioning this work against alternatives. 4. **roadmap-narrative** β†’ produces where this sits on the roadmap and the story around it. 5. **go-to-market** β†’ produces a launch plan: audience, messaging, channels, and timeline. ## Close the Quarter β€” `/close-the-quarter` *Measure β†’ Communicate* Β· Turn the quarter's raw numbers into a leadership-ready story and board deck. `metrics-framework` β†’ `churn-analysis` β†’ `executive-update` β†’ `board-deck-narrative` 1. **metrics-framework** β†’ produces the metric tree and what actually moved. 2. **churn-analysis** β†’ produces why customers left and what is avoidable. 3. **executive-update** β†’ produces a tight leadership briefing of the quarter. 4. **board-deck-narrative** β†’ produces a slide-by-slide board deck storyline. ## Launch a Product β€” `/launch-a-product` *Decide β†’ Ship* Β· Go from competitive landscape to positioning to a fully checklisted launch and press release. `competitor-teardown` β†’ `product-positioning-doc` β†’ `go-to-market` β†’ `product-launch-checklist` β†’ `press-release` 1. **competitor-teardown** β†’ produces the competitive map and gaps to exploit. 2. **product-positioning-doc** β†’ produces positioning, value props, and messaging pillars. 3. **go-to-market** β†’ produces the GTM plan across audience and channels. 4. **product-launch-checklist** β†’ produces an owner-by-owner launch readiness checklist. 5. **press-release** β†’ produces the announcement press release. ## Rescue an Account β€” `/rescue-an-account` *Measure β†’ Communicate* Β· Diagnose an at-risk customer and build the full save play through to renewal. `cs-health-scorecard` β†’ `churn-analysis` β†’ `cs-escalation-brief` β†’ `renewal-playbook` 1. **cs-health-scorecard** β†’ produces a health score with the specific risk drivers. 2. **churn-analysis** β†’ produces the root cause and whether the risk is avoidable. 3. **cs-escalation-brief** β†’ produces an internal escalation brief for the save. 4. **renewal-playbook** β†’ produces the renewal strategy and negotiation plan. ## Run Discovery β€” `/run-discovery` *Discover β†’ Decide* Β· From a vague opportunity to validated insight and a prioritised next step. `ambiguity-resolver` β†’ `discovery-interview-guide` β†’ `user-research-synthesis` β†’ `rice-prioritisation` 1. **ambiguity-resolver** β†’ produces a one-page problem brief from the fuzzy opportunity. 2. **discovery-interview-guide** β†’ produces a screener and discussion guide for user interviews. 3. **user-research-synthesis** β†’ produces themes and insights from the research. 4. **rice-prioritisation** β†’ produces a ranked, defensible list of what to do next. ## Repurpose Content β€” `/repurpose` *One source β†’ many platforms* Β· Turn one blog post, video, or idea into a full platform-native content pack β€” thread, LinkedIn, newsletter, carousel, and short-form script β€” with sharpened hooks and a thumbnail concept. `content-repurposer` β†’ `hook-writer` β†’ `thumbnail-creator` 1. **content-repurposer** β†’ produces platform-native drafts for X, LinkedIn, newsletter, carousel and short-form video. 2. **hook-writer** β†’ produces stronger, scroll-stopping hooks for each piece. 3. **thumbnail-creator** β†’ produces a thumbnail concept for the video version. ## Launch an AI Feature β€” `/launch-an-ai-feature` *Spec β†’ Design β†’ Evaluate β†’ Budget β†’ Document* Β· Take an AI/LLM feature idea from a probabilistic-aware PRD through retrieval/agent design, an eval plan with a ship bar, a cost & latency budget, and a launch-ready model card. `ai-feature-prd` β†’ `rag-design-doc` β†’ `ai-eval-plan` β†’ `llm-cost-latency-budget` β†’ `model-card` 1. **ai-feature-prd** β†’ produces a PRD designed for a probabilistic system β€” uncertainty UX, guardrails, fallback, and a quality bar. 2. **rag-design-doc** β†’ produces the retrieval/generation design (chunking, retrieval, reranking, grounding, failure modes). 3. **ai-eval-plan** β†’ produces an eval harness: datasets, rubrics, baselines, a ship threshold, and a regression gate. 4. **llm-cost-latency-budget** β†’ produces per-request token math, model tiering, caching, p95 targets, and spend guardrails. 5. **model-card** β†’ produces a launch-ready model card: intended use, sliced eval, limitations, and a rollback trigger. ## Grow a Product β€” `/grow-a-product` *Diagnose β†’ Experiment β†’ Retain β†’ Nurture* Β· Turn a growth goal into a full-funnel diagnosis, a prioritised experiment backlog, a retention loop, and the lifecycle journeys that nurture users β€” a joined-up growth plan. `marketing-funnel-plan` β†’ `growth-experiment-backlog` β†’ `retention-loop-design` β†’ `lifecycle-crm-plan` 1. **marketing-funnel-plan** β†’ produces a full-funnel map with the biggest leak identified and a 90-day focus. 2. **growth-experiment-backlog** β†’ produces a prioritised, properly-powered experiment backlog (ICE) against that stage. 3. **retention-loop-design** β†’ produces a retention/engagement loop (triggerβ†’actionβ†’rewardβ†’investment) and activation path. 4. **lifecycle-crm-plan** β†’ produces behaviour-triggered lifecycle journeys that drive the loop, with holdouts and suppression. ## Land a Job β€” `/land-a-job` *Decode β†’ Research β†’ Apply β†’ Interview* Β· Go after a specific role end to end: decode the job description, research the company, tailor your CV and cover letter to it, and prep for the interview β€” each step building on the last. `jd-decoder` β†’ `company-brief` β†’ `job-application` β†’ `interview-prep` 1. **jd-decoder** β†’ produces what the posting really wants, your honest fit, and the keywords to mirror. 2. **company-brief** β†’ produces a research brief β€” business model, trajectory, and the challenges this role would touch. 3. **job-application** β†’ produces an ATS-tailored CV summary and a cover letter aligned to the decoded requirements. 4. **interview-prep** β†’ produces a tailored prep pack β€” likely questions for this role and round, STAR answers, a story bank, and questions to ask. --- **Add your own:** define it in [`workflows.json`](workflows.json), add a matching `commands/.md`, and run `node scripts/build-workflows.mjs`. Recipes are just composition β€” every step is an existing skill you can already run on its own.