Product & Planning

tricentis Bundle

Creates an automated test case in Tosca Cloud from a description, reusing modules. Module discovery via toscactl; scaffold via tn (CLI gap). Does NOT cover manual-only tests or UI module scanning.

aethrox Bundle

Classify and prioritize an incoming bug report or feature request using Impact × Urgency, and route it to the right next step. Use when the user wants a backlog triaged, an issue prioritized, or asks whether something is worth working on now versus later.

chris-mcnulty Skill

Prepare a two-minute stakeholder briefing from recent email and Teams history. Reviews the last 90 days of communications with a specific person and produces a structured snapshot of commitments made, open/unresolved items, and observable communication patterns — based only on visible signals, no inferred intent. Use when user asks: "prep me for my meeting with [person]", "brief me on [person]", "stakeholder context for [person]", "what's my history with [person]", "relationship history with [person]", "get me up to speed on [person] before our meeting", "what have I committed to [person]", "what's open with [person]", "stakeholder briefing", "two-minute brief on [person]". Do NOT use for: scheduling meetings (use schedule-meeting), preparing for a specific meeting's agenda from a transcript (use meeting-intel), or drafting messages to the person (use stakeholder-comms).

shipshitdev Skill

Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

shipshitdev Skill

PRD completeness validation — required sections for pipeline entry

thiientv Bundle

Grounds version-sensitive engineering decisions in authoritative current sources by detecting the installed stack, retrieving official documentation or source, reconciling conflicts, and recording citations and confidence. Use for framework APIs, dependency behavior, standards, compatibility, migrations, or technical recommendations that may have changed. Not for stable project-local logic or broad product discovery.

valorisa Bundle

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into GitHub issues.

shawnclybor Skill

Run the deterministic verification gate against a PRD's success criteria. Every criterion must map to a check that returns a green/red signal. Use after ralph-implement completes and before the quality-review evaluation stage. Triggers — "verify against the PRD", "run the verification", "check success criteria", "did we hit all the gates", "verify [feature]". Hand-waving green checks is the most common way to ship the wrong thing.

shawnclybor Skill

Capture what you're building BEFORE writing it. Question-driven discovery that locks the target, success criteria, anchor case (one concrete example with expected outcome), and out-of-scope BEFORE any code, plan, or scaffolding. Output is `.claude/PRPs/{slug}/prd.md`. Use when starting a new skill, plugin, scorer, integration, deliverable template, or any artifact where "done" needs a verifiable definition. Triggers — "PRD for X", "spec out X", "let's plan a new skill/plugin", "build pipeline for X", "what are we actually building", or before any non-trivial build where you've caught yourself about to write code without a target. Pairs with build-probe (next), build-validate, build-plan, build-execute, build-evaluate.

shawnclybor Skill

Decompose a PRD into a sequenced checkbox task list. Each task is small enough to complete in one focused pass and tied to one or more PRD success criteria. Use after the PRD is accepted and before implementation begins. Triggers — "plan from the PRD", "break this into tasks", "task list for [feature]", "decompose [PRD]", "give me a plan".

shawnclybor Skill

Decompose a build PRD into an implementation plan. Names mandatory reading with file paths and line ranges, identifies the mirror target to copy structure from, lists step-by-step tasks, and specifies the acceptance test that build-evaluate will run. Plan only — no implementation code is written. Output is `.claude/PRPs/{slug}/plan.md`. Use after build-validate, before build-estimate. Triggers — "plan the build", "decompose the PRD", "implementation plan for X", "/build plan", or any time a PRD exists but no plan does.

shawnclybor Skill

Write a PRD (product requirements doc) for a new feature or non-trivial change. Output is a markdown file with problem statement, binary success criteria, in/out of scope, dependencies, and risks. Use at the start of any work that warrants a quality gate before implementation. Triggers — "write a PRD", "draft a PRD for X", "start with a PRD", "PRD for [feature]", "spec out [feature]". The success criteria written here become the verification gates downstream — they must be binary (yes/no answerable), not vibes.

shawnclybor Bundle

Turn a PRD's asserted facts into EMITTED facts. Writes one executable probe per measured claim in the PRD — each prints a single value — plus a lockfile pinning every source the PRD cites. PASS = every probe runs and prints exactly what the PRD says, and no cited source has moved. Runs after build-prd and before build-validate, and re-runs in seconds at every later stage as the drift detector. Use when a PRD asserts a number, a count, a filename, a line reference, or an "every X / none of X" claim. Triggers — "probe the PRD", "prove the anchors", "are the numbers still true", "recheck the sources", "/build probe".

shawnclybor Skill

Verify a completed build against the PRD's anchor case and success criteria. Runs the acceptance test and anchor-case check (serial across drivers sharing a write root), fans out 2-3 read-only cold-read agents (fresh-eyes, anti-scope-creep, drift-vs-mirror). On FAIL, auto-invokes five-whys for root-cause. On PASS with novel patterns, invokes insight-promotion to codify learnings. Read-only against the built artifact, idempotent — safe to re-run. Use after build-execute reports success. Triggers — "evaluate the build", "did it work", "verify the build", "acceptance test", "is it actually done". Outputs `.claude/PRPs/{slug}/evaluate.md` with a binary verdict.

shawnclybor Bundle

Coordinated three-lens adversarial review of any target — a PRD, a build plan, a validation report, code, or a freeform proposal. Spawns chaos-engineer, simplifier and adversarial-reviewer in parallel against non-overlapping questions, grades every finding against a rubric fixed BEFORE the agents run, defers the machine-decidable classes to a mechanical checker, and tracks the review process's own drift across runs so it cannot ratchet indefinitely. Use when a proposal, plan or document needs adversarial scrutiny before it is committed to. Triggers — "adversarial review", "review this plan", "tear this apart", "what's wrong with this", "review before I commit", "/adversarial-review". Do NOT use for a routine code diff (use code-review) or a build plan's pre-execution gate (use build-validate, which this complements rather than replaces).

jh941213 Skill

Codex용 자율 개발 루프. PRD 항목을 하나씩 처리하며 명시적 검증과 커밋 후보 로그를 남긴다. 트리거: "autodev", "자율 개발", "밤새 돌려", "/goal", "goal 기반 자동 개발", "자동 개발" 안티-트리거: "직접 구현해", "한번만 해", "수동"

jh941213 Skill

Codex 병렬 자율 개발 루프. 명시적으로 허용된 sub-agents가 worktree에서 동시에 PRD 항목을 처리한다. 트리거: "병렬 실험", "autodev parallel", "동시에 실험", "워크트리 실험", "/goal 병렬" 안티-트리거: "순차 실험", "하나씩"

harrychuang Bundle

Create or update PRD-led Storybook product prototypes under src/pages/prototypes with docs, typed route and transition metadata, deterministic fixtures, intuitive UI Flow review data, draggable Storybook UI Flow viewers with animated dashed arrow connections, Figma-exportable flow stories, and prototype Storybook stories. Use when building a new product prototype, turning a product idea into PRD plus UI Flow, standardizing prototype docs, updating an existing prototype flow, or preparing a Storybook prototype flow for JSON import into Figma with storybook-to-figma.

harrychuang Bundle

Create PRD-led Storybook product prototypes and frontend implementation handoff docs for web or app development, with deterministic fixtures, typed UI Flow route and transition metadata, API/data contracts, interactive prototype stories, template-compatible Static Flow export stories, and an optional Prototype Inspector runtime for Story/Docs/UI Flow/Data review. Use after design-system-to-storybook or independently when turning a product idea into PRD, UI Flow, Data Spec, Production Handoff, Acceptance Criteria, and a clickable Storybook prototype; when scaffolding a prototype folder; when preparing engineer or AI collaboration from design to frontend implementation; when documenting API/data contracts without real data wiring; when aligning UI Flow with the design-system-to-storybook storybook-template contract; when installing a Storybook UI Flow viewer; or when validating prototype and handoff docs across React Storybook projects.

harrychuang Bundle

Implement framework-agnostic frontend products and production features from PRD, UI Flow, UI Spec, Data Spec, Acceptance, Implementation Guide, and PRODUCTION_HANDOFF docs. Use when building a web or app frontend from 0 to 1, adding a route, screen, interface, or feature to an existing product, translating Storybook prototype handoff docs into production code, creating typed route/component/data-adapter work, or continuing after storybook-product-prototype. Resolve the target root and runtime architecture before greenfield scaffolding, inherit a clear existing stack without re-asking, ask when targets conflict or a migration is implied, and follow framework-native conventions rather than assuming React. Always follow design-system-governance: discover tokens, grid, motion, i18n, and shared components first; reuse existing components; stop for approval before creating missing tokens or shared components. When the target has no token system and the user approves establishing one, follow the token-bootstrap refe

harrychuang Bundle

Create PRD-led product prototypes in Storybook with docs, deterministic data, typed UI Flow route and transition metadata, and prototype stories. Use when turning a product idea into PRD, UI Flow, Data Spec, Acceptance Criteria, and a clickable Storybook prototype; when scaffolding a new prototype folder; or when validating prototype docs and metadata across React Storybook projects.

tricentis Bundle

Explains what a Tosca Cloud test case does in plain language. Uses toscactl for discovery and tn for Builder step-tree read (CLI gap). Read-only. Does NOT cover execution failure diagnosis (use tosca-analyzing-execution-results).

harpreetsingh Skill

Quickly capture an interesting insight, pattern, or discovery from the current session for future blog posts or content

richlander Skill

How to fetch a NuGet package's own authoritative docs with the dotnet-inspect CLI before writing or editing code against it. Use whenever a task requires calling or implementing against a NuGet package's API — especially a package you are not fully confident about. The key rule: run `dotnet-inspect package <id>@<version> --readme`, which returns the package's best shipped doc, and prefer it over guessing or relying on training memory. This is a discovery directive only; it contains no package-specific API content.

crozzbite Skill

Acts as a Product Manager to define MVP, User Stories, Backlog, and Roadmap for SaaS products.

crozzbite Skill

Socratic MVP Discovery (Phylactery Lich)

ryzhakar Skill

Write a trace — a dated note of one event, an event being a happening of a kind schema-resolution names, fixed once written — into the journal, where traces accumulate and stand unchanged, in the same stretch of work the event happens. A decision is made, a discovery lands, a failure is diagnosed, a commitment is entered, a delegation is issued, content arrives from elsewhere, the working text is condensed, a stretch of work starts or ends, "log this", "note what happened", "record that", "write it down".

ryzhakar Skill

Extracts implicit product decisions from stakeholders into durable artifacts through systematic gap detection and constrained questioning. Triggers: analyzing incomplete specs, stakeholder interviews, finding documentation gaps, "what questions should I ask", extracting product requirements, defining MVP scope. Produces separated artifacts (spec, personas, stories).

ryzhakar Skill

Writes user stories as value negotiation units, not template-filling exercises. Triggers: writing user stories, acceptance criteria, backlog items, story splitting, evaluating story quality, INVEST criteria application. Use when creating or refining Agile artifacts that capture work units.

zxremail Bundle

Use when 用户要画项目推进时间计划表、任务计划时间表、阶段路线图、 季度/月份泳道 roadmap、多阶段排期、重要时间节点横条、菱形里程碑、 嵌套能力分组、或阶梯式开放时间线，或对照左栏阶段 + 顶栏季度的计划图。 不要用 Mermaid gantt。

iamneilroberts Bundle

Use when the user invokes /sitrep — an occasional "state of the union" re-orientation sweep. Verifies what has actually shipped versus what handoffs, specs, memory, and chat history claim shipped (across git in one or more repos, handoff docs, specs, optional chat-history/memory MCPs, and open issues), surfaces loose ends and loss-risk (unpushed commits, stale/stray worktrees & branches, unchecked plan boxes, never-closed handoff pending sections), then resets what matters next as a milestone-anchored list plus a bounded off-roadmap-drift section. Writes a report to docs/digests/ and proposes (never applies) a roadmap diff. Triggers on /sitrep, "state of play", "what's actually shipped", "what did I leave hanging", "re-orient me on this project".

magnus919 Bundle

CPO methodology — product vision and strategy (North Star, product principles), competitive analysis and positioning, roadmap prioritization (RICE, Kano, OST), product-market fit frameworks (Sean Ellis test, retention curves), market sizing (TAM/SAM/SOM), platform strategy, product lifecycle management.

magnus919 Bundle

Product management frameworks embedded in references/: RICE, MoSCoW, Opportunity Solution Trees, customer interviews, spec template, stakeholder communication, decision log. All output is organized as an artifact pyramid with full SOURCES navigation at every layer.

diegosouzapw Bundle

Pattern Description

diegosouzapw Bundle

Local-first backlog workflow. Use when planning work, creating/updating backlog items, writing ADRs, enforcing Ready gate, generating views, or maintaining derived indexes (SQLite/FTS/embeddings).

luokai0 Bundle

AI以为自己工作了 discovery skill for VeriClaw 爪印. Use when the intent is AI以为自己工作了, AI工作幻觉, AI未做却说做了, AI装作自己做完了, or fake completion diagnosis after a model claims the work is done.