justin/pm-claude-skills
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: workflow recipes, eval badges, one-click MCP, playground upgrades, sample gallery, skill-of-the-week

Browse Source 
Signature features that turn breadth (174 skills) into a differentiated product:

- Workflow recipes: 5 cross-profession chains (workflows.json) that pass each
  output forward — slash commands (/ship-a-feature etc.), WORKFLOWS.md generated
  by scripts/build-workflows.mjs, README + MCP (list_workflows/get_workflow) wired
- Eval-backed quality: real per-skill scores from evals/results.json surfaced as
  badges in the playground and an honest README section (6 scored skills)
- One-click MCP: 'claude mcp add' install + workflow tools, works in any MCP client
- Playground: 'which skill?' recommender, with/without compare toggle, shareable
  ?skill= deep-links with prefilled inputs
- Sample-output gallery: hand-written examples for the hero five + generator
  (scripts/build-samples.mjs) + web/examples.html
- Skill-of-the-week: scheduled workflow + script that composes X/LinkedIn posts
  and posts to an optional webhook

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Mohit
2026-06-19 09:56:11 +01:00
parent 7f06f0a993
commit 54f76456ab
30 changed files with 1168 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files
commands/README.md
+12
View File
@@ -11,6 +11,18 @@ Claude Code **slash commands** that run a skill on whatever you pass them.
| `/retro` | Structured sprint retrospective | retro-analysis |
| `/exec-summary` | Crisp executive summary | executive-summary |
## 🧩 Workflow recipes — chained commands
These run **several skills in sequence**, passing each output forward as context. Full detail in [WORKFLOWS.md](../WORKFLOWS.md).
| Command | Chains | Lifecycle |
|---|---|---|
| `/ship-a-feature` | ambiguity-resolver → prd-template → rice-prioritisation → roadmap-narrative → go-to-market | Discover → Ship |
| `/close-the-quarter` | metrics-framework → churn-analysis → executive-update → board-deck-narrative | Measure → Communicate |
| `/launch-a-product` | competitor-teardown → product-positioning-doc → go-to-market → product-launch-checklist → press-release | Decide → Ship |
| `/rescue-an-account` | cs-health-scorecard → churn-analysis → cs-escalation-brief → renewal-playbook | Measure → Communicate |
| `/run-discovery` | ambiguity-resolver → discovery-interview-guide → user-research-synthesis → rice-prioritisation | Discover → Decide |
## Install
```bash
commands/close-the-quarter.md
+17
View File
@@ -0,0 +1,17 @@
---
description: Workflow recipe — turn the quarter's raw numbers into a leadership story and board deck by chaining 4 skills.
argument-hint: [the quarter's metrics, wins, and misses]
---
Run the **Close the Quarter** workflow recipe for: $ARGUMENTS
This is a *chain* of skills. Run each stage in order and **carry every stage's output forward as context** for the next. Open with a one-line plan of the 4 stages, then ask once for any essential missing inputs (the key numbers, the audience, the period). Don't re-ask between stages.
Run each stage under a clear `## Stage N — <name>` heading:
1. **Map what moved** — apply the `metrics-framework` skill to organise the numbers into a metric tree and identify what actually changed and why.
2. **Explain retention** — apply the `churn-analysis` skill to separate avoidable from unavoidable churn and surface the headline retention story.
3. **Brief leadership** — apply the `executive-update` skill, using the findings above, to write a tight leadership briefing for the period.
4. **Build the board story** — apply the `board-deck-narrative` skill to turn that briefing into a slide-by-slide board deck storyline.
Do not invent numbers — work only with what is given and flag any gaps. End with a 4-bullet **"What you now have"** recap.
commands/launch-a-product.md
+18
View File
@@ -0,0 +1,18 @@
---
description: Workflow recipe — go from competitive landscape to a fully checklisted launch and press release by chaining 5 skills.
argument-hint: [the product and who it's for]
---
Run the **Launch a Product** workflow recipe for: $ARGUMENTS
This is a *chain* of skills. Run each stage in order and **carry every stage's output forward as context** for the next. Open with a one-line plan of the 5 stages, then ask once for any essential missing inputs (the product, target customer, key competitors, launch date). Don't re-ask between stages.
Run each stage under a clear `## Stage N — <name>` heading:
1. **Map the field** — apply the `competitor-teardown` skill to map competitors and find the positioning gap to exploit.
2. **Position it** — apply the `product-positioning-doc` skill, using that gap, to define positioning, value props, and messaging pillars.
3. **Plan the GTM** — apply the `go-to-market` skill to turn the messaging into an audience-and-channel launch plan.
4. **Make it launch-ready** — apply the `product-launch-checklist` skill to produce an owner-by-owner readiness checklist.
5. **Announce it** — apply the `press-release` skill to draft the announcement, consistent with the positioning above.
Do not invent facts, dates, or competitor claims — flag assumptions. End with a 5-bullet **"What you now have"** recap.
commands/rescue-an-account.md
+17
View File
@@ -0,0 +1,17 @@
---
description: Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
argument-hint: [the account and what's going wrong]
---
Run the **Rescue an Account** workflow recipe for: $ARGUMENTS
This is a *chain* of skills. Run each stage in order and **carry every stage's output forward as context** for the next. Open with a one-line plan of the 4 stages, then ask once for any essential missing inputs (ARR, renewal date, usage signals, the trigger). Don't re-ask between stages.
Run each stage under a clear `## Stage N — <name>` heading:
1. **Score the risk** — apply the `cs-health-scorecard` skill to produce a health score and the specific risk drivers.
2. **Find the cause** — apply the `churn-analysis` skill to identify the root cause and whether the risk is avoidable.
3. **Escalate it** — apply the `cs-escalation-brief` skill to write the internal brief and resolution plan.
4. **Plan the renewal** — apply the `renewal-playbook` skill to build the renewal strategy and negotiation plan.
Do not invent account facts — work only with what is given. End with a 4-bullet **"What you now have"** recap.
commands/run-discovery.md
+17
View File
@@ -0,0 +1,17 @@
---
description: Workflow recipe — go from a vague opportunity to validated insight and a prioritised next step by chaining 4 skills.
argument-hint: [the opportunity or fuzzy question]
---
Run the **Run Discovery** workflow recipe for: $ARGUMENTS
This is a *chain* of skills. Run each stage in order and **carry every stage's output forward as context** for the next. Open with a one-line plan of the 4 stages, then ask once for any essential missing inputs (who the users are, what's prompting this, any constraints). Don't re-ask between stages.
Run each stage under a clear `## Stage N — <name>` heading:
1. **Frame it** — apply the `ambiguity-resolver` skill to turn the fuzzy opportunity into a one-page problem brief with a scoped question.
2. **Plan the research** — apply the `discovery-interview-guide` skill to build a screener and discussion guide for user interviews.
3. **Synthesise** — apply the `user-research-synthesis` skill to turn findings into themes and validated insights. (If no real findings exist yet, produce a synthesis template to fill in after interviews.)
4. **Decide what's next** — apply the `rice-prioritisation` skill to rank the resulting opportunities into a defensible next step.
Do not invent research findings — if interviews haven't happened, say so and produce the structure to capture them. End with a 4-bullet **"What you now have"** recap.
commands/ship-a-feature.md
+18
View File
@@ -0,0 +1,18 @@
---
description: Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.
argument-hint: [the feature idea or problem]
---
Run the **Ship a Feature** workflow recipe for: $ARGUMENTS
This is a *chain* of skills. Run each stage in order and **carry every stage's output forward as context** for the next — that shared context is the whole point. Open with a one-line plan of the 5 stages, then ask once for any essential missing inputs (target user, the problem, a rough success metric). Don't re-ask between stages.
Run each stage under a clear `## Stage N — <name>` heading:
1. **Frame the problem** — apply the `ambiguity-resolver` skill to turn the raw idea into a sharp problem statement and scoped boundaries.
2. **Spec it** — apply the `prd-template` skill, using the framed problem, to produce a PRD with goals/non-goals, requirements, and success metrics.
3. **Prioritise it** — apply the `rice-prioritisation` skill to score this work (reach, impact, confidence, effort) so its priority is defensible.
4. **Place it on the roadmap** — apply the `roadmap-narrative` skill to position the work and tell the story around it.
5. **Plan the launch** — apply the `go-to-market` skill to produce audience, messaging, channels, and a launch timeline.
Do not invent metrics, dates, or facts — note assumptions instead. After the last stage, end with a 5-bullet **"What you now have"** recap linking each artifact to the stage that produced it.