一键在 Manus 中运行任何 Skill

pmstack-sprint

星标8

分支1

更新时间2026年4月25日 04:53

Full PM sprint orchestrator — chains pmstack-prd, pmstack-metrics, pmstack-eval, and pmstack-brief in sequence with explicit user confirmation between each step. Use when the user has a customer signal or feature ask and wants to go end-to-end (problem → spec → metrics → eval design → stakeholder comms) in one guided pass with checkpoints.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

RyanAlberts

RyanAlberts/pmstack

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

PM Sprint Orchestrator

Chain pmstack-prd → pmstack-metrics → pmstack-eval → pmstack-brief, with explicit user confirmation after each step.

Procedure

If the user didn't provide a customer signal, ask for one and stop.
Step 1 — PRD. Invoke pmstack-prd with the signal. Write to outputs/prd-<topic-slug>-<date>.md. Show the path. Ask: "Continue to /metrics? (y/n)"
Step 2 — Metrics. Invoke pmstack-metrics, using the PRD as context. Write to outputs/metrics-<topic-slug>-<date>.md. Show the path. Ask: "Continue to /eval? (y/n)"
Step 3 — Eval design. Invoke pmstack-eval, using PRD + metrics as context. Write to outputs/eval-<topic-slug>-<date>.yaml. Show the path. Ask: "Continue to /brief? (y/n)"
Step 4 — Brief. Invoke pmstack-brief, summarizing PRD + metrics + eval for the user's named audience (default exec). Write to outputs/brief-<topic-slug>-<audience>-<date>.md.
Append one line to decisions-log.md: - YYYY-MM-DD — sprint: <topic> — prd, metrics, eval, brief in outputs/.

Hard rules

Run skills in sequence. Each step's output is the next step's input.
Stop and ask for explicit y/n confirmation after each artifact. Do not collapse steps to "save time."
If the user wants to revise a step, edit the artifact in place and ask again.
Do not auto-invoke pmstack-run-eval. The eval YAML is meant to be reviewed by the user before execution.

Anti-patterns

"It looks fine, let me just continue" — no. The user decides, not you.
Combining steps to fewer artifacts — no. Each artifact is a checkpoint and a deliverable.

同仓库更多 Skills

同仓库

pmstack-eval-report

RyanAlberts/pmstack

Turns a /run-eval result into a single self-contained, shareable HTML report — a verdict hero (pass/conditional/fail), the per-case table with PASS/FAIL color-coding, and the metrics table — that a PM can paste into Slack, a launch doc, LinkedIn, or a PR. The report carries a "run your own eval" backlink to pmstack. Use when the user says "make this eval shareable," "turn my eval run into a report," "export the eval results," "an HTML report of my eval," "share my eval results," or has a /run-eval output directory and wants a presentable artifact. Renders real run data only (from summary.md) — never invents numbers. Runs bin/eval-report.py on a run directory. Output: report.html next to the run's summary.md.

2026-06-248

pmstack-eval-grade

RyanAlberts/pmstack

Grades an eval the user already has against Anthropic's eval-design principles and returns an Eval Report Card — a letter grade A–F, the failures that earned it with the offending line, the single highest-leverage fix, and a shareable verdict card. It is the inverse of /eval (which writes a suite); this checks whether a suite is any good. Use when the user says "grade my eval," "is my eval any good," "review my eval suite," "roast my eval," "what's wrong with this eval," "did I write this eval right," pastes an eval YAML or rubric and asks for feedback, or wants to check an eval against the Anthropic framework before trusting it. Catches grader leakage, missing negative cases, no target, vibes-as-metric, and uncalibrated LLM-as-judge. Accepts a file path, a pasted/attached eval, or a plain-English success metric. Output: outputs/eval-grade-<feature>-<date>.md.

2026-06-208

pmstack-voc

RyanAlberts/pmstack

Synthesize many raw customer signals (support tickets, interview snippets, churn reasons, sales notes, NPS verbatims, app reviews) into a small set of ranked, PRD-ready problems. Use when a PM pastes or attaches a pile of feedback and asks "what's the real problem / what should we build first / what are the themes", when there are too many signals to read one by one, or when someone needs to turn voice-of-customer data into prioritized problem statements before writing a PRD. This is the front-of-funnel step that precedes pmstack-prd.

2026-05-298

pmstack-onboarding

RyanAlberts/pmstack

An interactive 9-step tutorial that walks a new user through every pmstack capability using a realistic AI-code-review scenario. Includes Anthropic's vibe-test (read raw transcripts before formalizing an eval) and transcript-review (diagnose failed trials as model / grader / task errors) rituals. Works in claude.ai web, desktop, and mobile (no terminal needed). Trigger when the user says "I just installed pmstack," "how do I use this," "tutorial," "walk me through pmstack," "getting started," or "show me what pmstack does."

2026-05-058

pmstack-transcript-review

RyanAlberts/pmstack

Walks a PM through Anthropic's Step 6 ritual — reading transcripts from many trials to diagnose every failed eval task as one of three things — model mistake, grader mistake, or task-spec error. Implements the practice Anthropic describes as "critical" — without it, badly-calibrated graders mask real model improvements. Use when the user has a /run-eval result with failures, asks "why did this fail?", says "let's read the transcripts," wants to debug an eval, suspects grader bugs, or mentions Anthropic's transcript-review practice. Accepts a run folder path, pasted summary + cases, or attached files. Output: a markdown memo at outputs/transcript-review-<feature>-<date>.md with verdict counts and per-trial diagnoses.

2026-05-058

pmstack-vibe-test

RyanAlberts/pmstack

Walks a PM through the layer-1 ritual of reading raw transcripts of an AI feature in action — what Anthropic calls "manual testing, dogfooding, and intuition" — before formalizing a structured eval. Surfaces failure patterns, drafts task candidates (including balanced negative cases per Anthropic Step 3), and produces a verdict on whether the feature is ready for /eval. Use when the user says "I want to vibe-test this," "I have transcripts of our AI feature," "before we write evals let's read the data," "we have support tickets / bug reports about this AI feature," or asks how to start an eval from scratch. Accepts pasted transcripts, attached files, or a folder path. Output: a markdown memo at outputs/vibe-test-<feature>-<date>.md.

2026-05-058

name	pmstack-sprint
description	Full PM sprint orchestrator — chains pmstack-prd, pmstack-metrics, pmstack-eval, and pmstack-brief in sequence with explicit user confirmation between each step. Use when the user has a customer signal or feature ask and wants to go end-to-end (problem → spec → metrics → eval design → stakeholder comms) in one guided pass with checkpoints.

PM Sprint Orchestrator

Chain pmstack-prd → pmstack-metrics → pmstack-eval → pmstack-brief, with explicit user confirmation after each step.

Procedure

If the user didn't provide a customer signal, ask for one and stop.
Step 1 — PRD. Invoke pmstack-prd with the signal. Write to outputs/prd-<topic-slug>-<date>.md. Show the path. Ask: "Continue to /metrics? (y/n)"
Step 2 — Metrics. Invoke pmstack-metrics, using the PRD as context. Write to outputs/metrics-<topic-slug>-<date>.md. Show the path. Ask: "Continue to /eval? (y/n)"
Step 3 — Eval design. Invoke pmstack-eval, using PRD + metrics as context. Write to outputs/eval-<topic-slug>-<date>.yaml. Show the path. Ask: "Continue to /brief? (y/n)"
Step 4 — Brief. Invoke pmstack-brief, summarizing PRD + metrics + eval for the user's named audience (default exec). Write to outputs/brief-<topic-slug>-<audience>-<date>.md.
Append one line to decisions-log.md: - YYYY-MM-DD — sprint: <topic> — prd, metrics, eval, brief in outputs/.

Hard rules

Run skills in sequence. Each step's output is the next step's input.
Stop and ask for explicit y/n confirmation after each artifact. Do not collapse steps to "save time."
If the user wants to revise a step, edit the artifact in place and ask again.
Do not auto-invoke pmstack-run-eval. The eval YAML is meant to be reviewed by the user before execution.

Anti-patterns

"It looks fine, let me just continue" — no. The user decides, not you.
Combining steps to fewer artifacts — no. Each artifact is a checkpoint and a deliverable.