RyanAlberts
- 20 skills
- 0 followers
- 6 hours ago last updated
- ▌ Pmstack Prd · ryanalbertsTurn a raw customer signal (quote, support ticket, feature request, exec ask) into a structured Product Requirements Document. Use when a PM mentions a customer quote and wants a spec, when "let's write a PRD" comes up, when a vague feature request needs scoping, or when the user asks for a problem statement, MoSCoW prioritization, success metrics, or PRD template.
- ▌ Pmstack Voc · ryanalbertsSynthesize 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.
- ▌
- ▌ Pmstack Lint · ryanalbertsWalks the pmstack skill graph against the outputs/ directory to find graph gaps (missing downstream artifacts), cross-artifact drift (PRD-metrics-eval misalignment), and stale candidates (superseded files). Each finding includes a one-line "do this" recommendation. Trigger when the user says "lint my workspace," "graph check," "find drift," "tidy up outputs," "what's stale," or asks for a workspace audit. Run weekly on schedule, or before any review.
- ▌ Pmstack Brief · ryanalbertsDraft a stakeholder brief on a topic, tailored to executive, engineering, customer, or board audience. Use when a PM asks for a "brief", "update", "readout", "exec summary", "eng comms", "customer announcement", or "board update", or when they need to communicate a status / decision / change to a specific audience and need help adapting the framing.
- ▌ Pmstack Sprint · ryanalbertsFull 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.
- ▌ Pmstack Weekly · ryanalbertsA Monday-morning self-snapshot for PMs. Three sections only — decisions made, open loops aging out, and one required "thing I changed my mind about." Anti-vanity by design. Trigger when the user says "weekly memo," "weekly recap," "Monday status," "what changed this week," "weekly self-check," or asks to summarize last week's PM activity. Run weekly on schedule, or on demand to catch up.
- ▌ Pmstack Compare · ryanalbertsFeature-by-feature comparison of two or more products with built-in eval design and runnable execution. Use when the PM wants to compare specific features across products (e.g., "compare GitHub Copilot vs Cursor", "how does our pricing stack up against X and Y", "evaluate these two AI coding tools head-to-head"). Use pmstack-competitive instead for market-positioning analysis (audience, value prop, white space).
- ▌ Pmstack Metrics · ryanalbertsDesign a measurement framework for an AI product or feature with North Star, supporting metrics, counter-metrics, and AI-specific quality / latency / cost metrics. Use when a PM asks "how do we measure this", "what's the North Star for X", "how would we know X is winning", or mentions instrumentation, OKRs, KPIs, or success criteria for an AI feature.
- ▌ Pmstack Run Eval · ryanalbertsExecute an evaluation YAML produced by pmstack-eval against a real target system, running n_trials per task and reporting both pass@k and pass^k. Implements the running side of Anthropic's eval framework. HARD-STOPS with educative errors if no target is configured, no tasks are present, or required env vars are missing — never simulates results. Use when the user asks to "run", "execute", or "score" an eval, or wants real metrics from an existing eval design. Requires a runtime that can execute Python and the `claude` CLI (Claude Code, sandboxed code-exec on web, or local terminal).
- ▌ Pmstack Eval Self · ryanalbertsRun the pmstack self-eval suite to score every pmstack skill against canonical scenarios, with regression check vs the locked golden baseline. Use when the user wants to test pmstack itself, check skill quality after a model upgrade or prompt change, or verify pmstack still works before recommending it to others.
- ▌ Pmstack Premortem · ryanalbertsRun a Klein-style pre-mortem on a draft PRD before launch — simulates 3 plausible failure stories 6 months in the future, names leading indicators and mitigations, then offers to mutate the PRD's Risks section. Trigger when the user says "pre-mortem," "what could go wrong," "risk pass," "imagine this fails," "stress test the spec," or asks to harden a PRD before review. Use after /prd, before launch.
- ▌
- ▌ Pmstack Eval Drift · ryanalbertsRe-runs an existing eval suite, diffs against the prior baseline, and writes a release-blocker memo if anything regressed. Use weekly on a schedule, or on demand before a release. Trigger when the user mentions "did my AI feature get worse," "eval drift," "model regression," "eval over time," "weekly eval," "release-blocker check," "is this still working," or asks to re-run /eval-self / /run-eval and compare to last time. Designed for repeated runs — produces durable, dated artifacts.
- ▌
- ▌ Pmstack Onboarding · ryanalbertsAn 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."
- ▌ Pmstack Competitive · ryanalbertsGenerate a structured competitive landscape analysis for a market or product category. Use when a PM mentions "competitive analysis", "market positioning", "white space", "where do we wedge in", asks who else is in a space, or wants to size up rivals before strategy/launch. Focus is on market positioning (audience, value prop, white space) — for feature-by-feature parity, use pmstack-compare instead.
- ▌
- ▌ Pmstack Launch Readiness · ryanalbertsPre-launch verifier. Aggregates PRD, metrics, eval design, eval run, premortem, eval-drift, and brief evidence into a single GO/NO-GO/CONDITIONAL verdict with each item showing pass/fail/missing plus the file that proves it. Trigger when the user says "are we ready to ship," "launch readiness," "release check," "pre-launch review," "ship it?" or asks to gate a release. Run before any launch.
- ▌ Pmstack Transcript Review · ryanalbertspmstack /transcript-review — model mistake, grader mistake, or task error?