From supervibe
Use BEFORE building any user-facing feature to write a Product Requirements Document framing problem, users, solution, success metrics, and out-of-scope. Triggers: 'PRD', 'продуктовая спецификация', 'product requirements', 'оформи PRD'.
npx claudepluginhub vtrka/supervibe --plugin supervibeThis skill is limited to using the following tools:
BEFORE building any user-facing feature with explicit business value. Use when product-manager or systems-analyst agent is involved.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
BEFORE building any user-facing feature with explicit business value. Use when product-manager or systems-analyst agent is involved.
NOT for: internal refactors, infra changes, dev tooling.
Follow docs/references/skill-expert-operating-standard.md: start from source of truth, preserve retrieval evidence, apply scope safety, use real producers with runtime receipts for durable delegated outputs, verify before completion claims, and keep confidence below gate when evidence is partial.
.supervibe/artifacts/prd/ for prior PRDs (numbering, format).supervibe/artifacts/specs/Feature scope?
├─ Single user-facing change → lightweight PRD (1 page)
├─ Multi-screen flow → full PRD (2-4 pages) with user journey diagram
└─ New product area → comprehensive PRD with market context, competitive analysis
.supervibe/artifacts/prd/.supervibe/artifacts/prd/NNNN-<feature>.md:
# PRD-NNNN: <Feature Name>
**Status:** DRAFT | REVIEW | APPROVED | IMPLEMENTED
**Date:** YYYY-MM-DD
**Author:** <product-manager>
**Stakeholders:** <list>
## Problem
<whose problem, when, what's the cost of inaction>
## Users
- Primary persona: <who, JTBD>
- Secondary personas: <if any>
## Solution
<what we're building, key flows>
## Success metrics
- Quantitative: <metric + target + timeframe>
- Qualitative: <user feedback signals>
## Out-of-scope
- <explicitly NOT building this>
## Risks
- <risk + mitigation>
## Dependencies
- <other teams / systems / decisions>
## Open questions
- <unresolved items, owner>
supervibe:confidence-scoring artifact-type=requirements-specsupervibe:brainstorming (technical design) once APPROVEDReturns: PRD file with all sections filled, success metrics measurable, out-of-scope explicit.
.supervibe/artifacts/prd/NNNN-<feature>.mdsupervibe:brainstorming — technical design after PRD approvedproduct-manager agent — primary authorsupervibe:prd — for technical decisions referenced in SolutionA PRD without user evidence is product-by-vibes. Required input:
If no research exists: explicitly state "No research conducted; PRD is hypothesis-mode" and add user-research as Phase 0 of the implementation plan.
Each requirement gets ≥1 acceptance criterion in Given/When/Then form:
Given a user with verified email
When they request password reset
Then they receive an email within 30 seconds with a single-use token
And the token expires after 15 minutes
And reusing the token returns 410 Gone
Vague ACs ("should work well") fail rubric scoring.
PRD must define how we'll know it worked:
| Metric | Baseline | Target | Measurement | Trigger if missed |
|---|---|---|---|---|
≥3 metrics. At least one is a leading indicator (early signal), one is a lagging indicator (business impact).
If the PRD adds a feature that replaces an existing one:
If no deprecation: explicitly state "No deprecation — additive feature only".
Before launch (Phase N+1 of plan), verify:
What events do we emit? What dashboards do we add? Required input from supervibe:_product:analytics-implementation:
If feature is non-instrumented: explicitly state "No instrumentation needed" with reason.
Same format as plans:
≥3 risks. ≥1 must be product/UX risk (not just technical).
Save PRDs to .supervibe/artifacts/specs/YYYY-MM-DD-<feature>-prd.md. Use template at docs/templates/PRD-template.md.
Required sections (in order):
.supervibe/artifacts/specs/YYYY-MM-DD-<feature>-prd.mdrequirements; score ≥ 9supervibe:requirements-intake — predecessor (intake → research → PRD)supervibe:writing-plans — consumer (PRD → implementation plan)supervibe:prd — design decisions called out separately from PRDsupervibe:_product:product-manager — primary authorsupervibe:_product:systems-analyst — collaborator on ACssupervibe:_product:analytics-implementation — collaborator on instrumentation