@su-record/vibe 2.9.32 → 2.9.34

package/skills/create-prd/orchestrator.md

@@ -1,70 +1,70 @@
----
-name: create-prd-orchestrator
-type: orchestrator
-agents: [researcher, edge-case-finder, requirements-writer, prioritizer, reviewer]
----
-
-# Create-PRD Orchestrator
-
-## Workflow
-
-### Phase 1: Gather Context
-- **Agent**: researcher, edge-case-finder
-- **Input**: Feature idea or problem statement + codebase context
-- **Output**: researcher → existing patterns, prior art, constraints; edge-case-finder → edge cases, failure modes, user scenarios
-- **Parallel**: yes — researcher and edge-case-finder run simultaneously
-
-### Phase 2: Draft User Stories
-- **Agent**: requirements-writer
-- **Input**: Context and edge cases from Phase 1
-- **Output**: User stories in `As a / I want / So that` format with acceptance criteria
-- **Parallel**: no — sequential synthesis of Phase 1 outputs
-
-### Phase 3: Prioritize
-- **Agent**: prioritizer
-- **Input**: User stories from Phase 2
-- **Output**: RICE-scored stories with recommended MoSCoW classification (Must/Should/Could/Won't)
-- **Parallel**: no — requires full story set for relative scoring
-
-### Phase 4: Review
-- **Agent**: reviewer
-- **Input**: Prioritized stories + RICE scores from Phase 3
-- **Output**: Completeness verdict — missing sections, ambiguous requirements, scope concerns
-- **Parallel**: no
-
-### Phase 5: Output PRD
-- **Agent**: orchestrator (self)
-- **Input**: All phase outputs
-- **Output**: Structured PRD document using `templates/prd.md` format
-- **Parallel**: no
-
-## DAG (Dependency Graph)
-
-```mermaid
-graph TD
-    A[Phase 1a: Researcher] --> C[Phase 2: Requirements-Writer]
-    B[Phase 1b: Edge-Case-Finder] --> C
-    C --> D[Phase 3: Prioritizer]
-    D --> E[Phase 4: Reviewer]
-    E --> F[Phase 5: PRD Output]
-```
-
-## Error Handling
-
-| Phase | Failure Mode | Strategy |
-|-------|-------------|----------|
-| Phase 1 | researcher returns no prior art | Proceed — note "greenfield feature" in PRD |
-| Phase 1 | edge-case-finder times out | Continue with researcher output only, flag limited edge-case coverage |
-| Phase 2 | Problem statement too vague | Pause, prompt user with clarifying questions before continuing |
-| Phase 3 | RICE data unavailable (no metrics) | Use relative scoring (High/Medium/Low), note data gaps |
-| Phase 4 | Reviewer finds critical gaps | Return to Phase 2 with gap list (max 1 retry) |
-| Phase 4 | Retry still incomplete after 1 pass | Flag gaps as `needs-clarification`, output partial PRD |
-| Phase 5 | PRD template missing | Output raw structured markdown without template |
-
-## Scalability Modes
-
-| Mode | When | Agents Used |
-|------|------|-------------|
-| Full | Normal operation | All 5 agents |
-| Reduced | Time pressure | researcher + requirements-writer + reviewer only |
-| Single | Quick story draft | requirements-writer only — draft without research or scoring |
+---
+name: create-prd-orchestrator
+type: orchestrator
+agents: [researcher, edge-case-finder, requirements-writer, prioritizer, reviewer]
+---
+
+# Create-PRD Orchestrator
+
+## Workflow
+
+### Phase 1: Gather Context
+- **Agent**: researcher, edge-case-finder
+- **Input**: Feature idea or problem statement + codebase context
+- **Output**: researcher → existing patterns, prior art, constraints; edge-case-finder → edge cases, failure modes, user scenarios
+- **Parallel**: yes — researcher and edge-case-finder run simultaneously
+
+### Phase 2: Draft User Stories
+- **Agent**: requirements-writer
+- **Input**: Context and edge cases from Phase 1
+- **Output**: User stories in `As a / I want / So that` format with acceptance criteria
+- **Parallel**: no — sequential synthesis of Phase 1 outputs
+
+### Phase 3: Prioritize
+- **Agent**: prioritizer
+- **Input**: User stories from Phase 2
+- **Output**: RICE-scored stories with recommended MoSCoW classification (Must/Should/Could/Won't)
+- **Parallel**: no — requires full story set for relative scoring
+
+### Phase 4: Review
+- **Agent**: reviewer
+- **Input**: Prioritized stories + RICE scores from Phase 3
+- **Output**: Completeness verdict — missing sections, ambiguous requirements, scope concerns
+- **Parallel**: no
+
+### Phase 5: Output PRD
+- **Agent**: orchestrator (self)
+- **Input**: All phase outputs
+- **Output**: Structured PRD document using `templates/prd.md` format
+- **Parallel**: no
+
+## DAG (Dependency Graph)
+
+```mermaid
+graph TD
+    A[Phase 1a: Researcher] --> C[Phase 2: Requirements-Writer]
+    B[Phase 1b: Edge-Case-Finder] --> C
+    C --> D[Phase 3: Prioritizer]
+    D --> E[Phase 4: Reviewer]
+    E --> F[Phase 5: PRD Output]
+```
+
+## Error Handling
+
+| Phase | Failure Mode | Strategy |
+|-------|-------------|----------|
+| Phase 1 | researcher returns no prior art | Proceed — note "greenfield feature" in PRD |
+| Phase 1 | edge-case-finder times out | Continue with researcher output only, flag limited edge-case coverage |
+| Phase 2 | Problem statement too vague | Pause, prompt user with clarifying questions before continuing |
+| Phase 3 | RICE data unavailable (no metrics) | Use relative scoring (High/Medium/Low), note data gaps |
+| Phase 4 | Reviewer finds critical gaps | Return to Phase 2 with gap list (max 1 retry) |
+| Phase 4 | Retry still incomplete after 1 pass | Flag gaps as `needs-clarification`, output partial PRD |
+| Phase 5 | PRD template missing | Output raw structured markdown without template |
+
+## Scalability Modes
+
+| Mode | When | Agents Used |
+|------|------|-------------|
+| Full | Normal operation | All 5 agents |
+| Reduced | Time pressure | researcher + requirements-writer + reviewer only |
+| Single | Quick story draft | requirements-writer only — draft without research or scoring |

package/skills/create-prd/rubrics/completeness.md

@@ -1,58 +1,58 @@
-# PRD Completeness Checklist
-
-## Section 1 — Summary
-
-- [ ] Describes what the document is about in 2-3 sentences
-- [ ] Readable by a non-technical stakeholder
-- [ ] Status clearly marked (Draft / Review / Approved)
-
-## Section 2 — Contacts
-
-- [ ] Product Manager named as owner
-- [ ] Engineering Lead included
-- [ ] Designer included (if UI/UX involved)
-- [ ] Key decision-maker or sponsor listed
-
-## Section 3 — Background
-
-- [ ] "Why this?" answered — clear context given
-- [ ] "Why now?" answered — trigger or change identified
-- [ ] No assumed knowledge — first-time reader can understand
-
-## Section 4 — Objective
-
-- [ ] Goal statement is outcome-oriented (not feature-oriented)
-- [ ] At least one measurable Key Result with baseline, target, and timeframe
-- [ ] Linked to company strategy or OKR (even briefly)
-
-## Section 5 — Market Segments
-
-- [ ] Primary audience defined by problem or job-to-be-done (not just demographics)
-- [ ] Constraints explicitly stated (who this is NOT for)
-
-## Section 6 — Value Propositions
-
-- [ ] Customer jobs listed (what users are trying to accomplish)
-- [ ] Gains (benefits) distinguished from pains (problems removed)
-- [ ] Competitive differentiation stated — why us, why better
-
-## Section 7 — Solution
-
-- [ ] 7.1: Prototype link or key screen descriptions included
-- [ ] 7.2: Features table includes priority (Must / Should / Could)
-- [ ] 7.4: At least 2 assumptions listed with validation method
-- [ ] No feature described without a corresponding user job or pain from Section 6
-
-## Section 8 — Release
-
-- [ ] MVP scope defined — what is in V1 vs. later
-- [ ] Out-of-scope items explicitly listed (prevents scope creep)
-- [ ] Relative timeframes used — no hard dates in V1 unless confirmed
-
-## Overall Quality
-
-- [ ] Jargon-free — a new team member can understand without asking
-- [ ] No sections left as placeholder ("TBD" without owner + due date)
-- [ ] Assumptions are flagged, not buried as facts
-- [ ] Document length proportional to initiative size (not bloated)
-- [ ] Open questions have owners and due dates
+# PRD Completeness Checklist
+
+## Section 1 — Summary
+
+- [ ] Describes what the document is about in 2-3 sentences
+- [ ] Readable by a non-technical stakeholder
+- [ ] Status clearly marked (Draft / Review / Approved)
+
+## Section 2 — Contacts
+
+- [ ] Product Manager named as owner
+- [ ] Engineering Lead included
+- [ ] Designer included (if UI/UX involved)
+- [ ] Key decision-maker or sponsor listed
+
+## Section 3 — Background
+
+- [ ] "Why this?" answered — clear context given
+- [ ] "Why now?" answered — trigger or change identified
+- [ ] No assumed knowledge — first-time reader can understand
+
+## Section 4 — Objective
+
+- [ ] Goal statement is outcome-oriented (not feature-oriented)
+- [ ] At least one measurable Key Result with baseline, target, and timeframe
+- [ ] Linked to company strategy or OKR (even briefly)
+
+## Section 5 — Market Segments
+
+- [ ] Primary audience defined by problem or job-to-be-done (not just demographics)
+- [ ] Constraints explicitly stated (who this is NOT for)
+
+## Section 6 — Value Propositions
+
+- [ ] Customer jobs listed (what users are trying to accomplish)
+- [ ] Gains (benefits) distinguished from pains (problems removed)
+- [ ] Competitive differentiation stated — why us, why better
+
+## Section 7 — Solution
+
+- [ ] 7.1: Prototype link or key screen descriptions included
+- [ ] 7.2: Features table includes priority (Must / Should / Could)
+- [ ] 7.4: At least 2 assumptions listed with validation method
+- [ ] No feature described without a corresponding user job or pain from Section 6
+
+## Section 8 — Release
+
+- [ ] MVP scope defined — what is in V1 vs. later
+- [ ] Out-of-scope items explicitly listed (prevents scope creep)
+- [ ] Relative timeframes used — no hard dates in V1 unless confirmed
+
+## Overall Quality
+
+- [ ] Jargon-free — a new team member can understand without asking
+- [ ] No sections left as placeholder ("TBD" without owner + due date)
+- [ ] Assumptions are flagged, not buried as facts
+- [ ] Document length proportional to initiative size (not bloated)
+- [ ] Open questions have owners and due dates

package/skills/create-prd/templates/prd.md

@@ -1,139 +1,139 @@
-# PRD: {{PRODUCT_OR_FEATURE_NAME}}
-
-> Version: {{VERSION}} | Status: {{STATUS}} (Draft / Review / Approved)
-> Last updated: {{DATE}}
-
----
-
-## 1. Summary
-
-{{2-3 SENTENCES DESCRIBING WHAT THIS DOCUMENT COVERS AND WHY IT EXISTS}}
-
----
-
-## 2. Contacts
-
-| Name | Role | Responsibility |
-|------|------|----------------|
-| {{PM_NAME}} | Product Manager | Owner, final decisions |
-| {{LEAD_ENG_NAME}} | Engineering Lead | Technical feasibility |
-| {{DESIGN_NAME}} | Designer | UX/UI |
-| {{STAKEHOLDER_NAME}} | {{STAKEHOLDER_ROLE}} | {{COMMENT}} |
-
----
-
-## 3. Background
-
-**Context**
-{{WHAT IS THIS INITIATIVE ABOUT? WHAT LED TO IT?}}
-
-**Why now?**
-{{HAS SOMETHING CHANGED? NEW DATA, MARKET SHIFT, REGULATORY REQUIREMENT?}}
-
-**Is this newly possible?**
-{{HAS NEW TECHNOLOGY OR CAPABILITY MADE THIS FEASIBLE NOW?}}
-
----
-
-## 4. Objective
-
-**Goal**
-{{WHAT ARE WE TRYING TO ACHIEVE AND WHY DOES IT MATTER?}}
-
-**Strategic alignment**
-{{HOW DOES THIS ALIGN WITH COMPANY VISION AND CURRENT STRATEGY?}}
-
-**Key Results (SMART OKRs)**
-
-| Metric | Baseline | Target | Timeframe |
-|--------|----------|--------|-----------|
-| {{METRIC_1}} | {{BASELINE}} | {{TARGET}} | {{TIMEFRAME}} |
-| {{METRIC_2}} | {{BASELINE}} | {{TARGET}} | {{TIMEFRAME}} |
-
----
-
-## 5. Market Segments
-
-**Primary segment**
-{{WHO ARE WE BUILDING THIS FOR? DESCRIBE BY PROBLEM/JOB, NOT DEMOGRAPHICS.}}
-
-**Secondary segment (if any)**
-{{OPTIONAL}}
-
-**Constraints**
-- {{CONSTRAINT_1}} (e.g., "Users must be logged in")
-- {{CONSTRAINT_2}}
-
----
-
-## 6. Value Propositions
-
-**Customer jobs we address**
-- {{JOB_1}}: {{CONTEXT}}
-- {{JOB_2}}: {{CONTEXT}}
-
-**Gains (what customers get)**
-- {{GAIN_1}}
-- {{GAIN_2}}
-
-**Pains we eliminate**
-- {{PAIN_1}}
-- {{PAIN_2}}
-
-**Competitive advantage**
-{{HOW DO WE SOLVE THIS BETTER THAN ALTERNATIVES? WHAT IS OUR UNIQUE EDGE?}}
-
----
-
-## 7. Solution
-
-### 7.1 UX / Prototypes
-
-{{LINK TO FIGMA OR WIREFRAMES, OR DESCRIBE KEY SCREENS/FLOWS}}
-
-Key user flows:
-1. {{FLOW_1_NAME}}: {{BRIEF DESCRIPTION}}
-2. {{FLOW_2_NAME}}: {{BRIEF DESCRIPTION}}
-
-### 7.2 Key Features
-
-| Feature | Description | Priority |
-|---------|-------------|----------|
-| {{FEATURE_1}} | {{DESCRIPTION}} | Must |
-| {{FEATURE_2}} | {{DESCRIPTION}} | Should |
-| {{FEATURE_3}} | {{DESCRIPTION}} | Could |
-
-### 7.3 Technology (optional)
-
-{{ONLY INCLUDE IF TECH CHOICES HAVE PRODUCT IMPLICATIONS — e.g., real-time, offline support}}
-
-### 7.4 Assumptions
-
-| # | Assumption | How to Validate | Risk if Wrong |
-|---|-----------|-----------------|---------------|
-| 1 | {{ASSUMPTION_1}} | {{VALIDATION_METHOD}} | {{RISK}} |
-| 2 | {{ASSUMPTION_2}} | {{VALIDATION_METHOD}} | {{RISK}} |
-
----
-
-## 8. Release Plan
-
-**Scope approach**: {{PHASED / BIG BANG / GRADUAL ROLLOUT}}
-
-| Phase | What's Included | Estimated Timeline |
-|-------|----------------|-------------------|
-| V1 (MVP) | {{MVP_SCOPE}} | {{RELATIVE_TIME}} |
-| V2 | {{V2_SCOPE}} | {{RELATIVE_TIME}} |
-| Future | {{FUTURE_ITEMS}} | TBD |
-
-**Out of scope (V1)**
-- {{OUT_OF_SCOPE_1}}
-- {{OUT_OF_SCOPE_2}}
-
----
-
-## Open Questions
-
-| # | Question | Owner | Due |
-|---|----------|-------|-----|
-| 1 | {{QUESTION_1}} | {{OWNER}} | {{DATE}} |
+# PRD: {{PRODUCT_OR_FEATURE_NAME}}
+
+> Version: {{VERSION}} | Status: {{STATUS}} (Draft / Review / Approved)
+> Last updated: {{DATE}}
+
+---
+
+## 1. Summary
+
+{{2-3 SENTENCES DESCRIBING WHAT THIS DOCUMENT COVERS AND WHY IT EXISTS}}
+
+---
+
+## 2. Contacts
+
+| Name | Role | Responsibility |
+|------|------|----------------|
+| {{PM_NAME}} | Product Manager | Owner, final decisions |
+| {{LEAD_ENG_NAME}} | Engineering Lead | Technical feasibility |
+| {{DESIGN_NAME}} | Designer | UX/UI |
+| {{STAKEHOLDER_NAME}} | {{STAKEHOLDER_ROLE}} | {{COMMENT}} |
+
+---
+
+## 3. Background
+
+**Context**
+{{WHAT IS THIS INITIATIVE ABOUT? WHAT LED TO IT?}}
+
+**Why now?**
+{{HAS SOMETHING CHANGED? NEW DATA, MARKET SHIFT, REGULATORY REQUIREMENT?}}
+
+**Is this newly possible?**
+{{HAS NEW TECHNOLOGY OR CAPABILITY MADE THIS FEASIBLE NOW?}}
+
+---
+
+## 4. Objective
+
+**Goal**
+{{WHAT ARE WE TRYING TO ACHIEVE AND WHY DOES IT MATTER?}}
+
+**Strategic alignment**
+{{HOW DOES THIS ALIGN WITH COMPANY VISION AND CURRENT STRATEGY?}}
+
+**Key Results (SMART OKRs)**
+
+| Metric | Baseline | Target | Timeframe |
+|--------|----------|--------|-----------|
+| {{METRIC_1}} | {{BASELINE}} | {{TARGET}} | {{TIMEFRAME}} |
+| {{METRIC_2}} | {{BASELINE}} | {{TARGET}} | {{TIMEFRAME}} |
+
+---
+
+## 5. Market Segments
+
+**Primary segment**
+{{WHO ARE WE BUILDING THIS FOR? DESCRIBE BY PROBLEM/JOB, NOT DEMOGRAPHICS.}}
+
+**Secondary segment (if any)**
+{{OPTIONAL}}
+
+**Constraints**
+- {{CONSTRAINT_1}} (e.g., "Users must be logged in")
+- {{CONSTRAINT_2}}
+
+---
+
+## 6. Value Propositions
+
+**Customer jobs we address**
+- {{JOB_1}}: {{CONTEXT}}
+- {{JOB_2}}: {{CONTEXT}}
+
+**Gains (what customers get)**
+- {{GAIN_1}}
+- {{GAIN_2}}
+
+**Pains we eliminate**
+- {{PAIN_1}}
+- {{PAIN_2}}
+
+**Competitive advantage**
+{{HOW DO WE SOLVE THIS BETTER THAN ALTERNATIVES? WHAT IS OUR UNIQUE EDGE?}}
+
+---
+
+## 7. Solution
+
+### 7.1 UX / Prototypes
+
+{{LINK TO FIGMA OR WIREFRAMES, OR DESCRIBE KEY SCREENS/FLOWS}}
+
+Key user flows:
+1. {{FLOW_1_NAME}}: {{BRIEF DESCRIPTION}}
+2. {{FLOW_2_NAME}}: {{BRIEF DESCRIPTION}}
+
+### 7.2 Key Features
+
+| Feature | Description | Priority |
+|---------|-------------|----------|
+| {{FEATURE_1}} | {{DESCRIPTION}} | Must |
+| {{FEATURE_2}} | {{DESCRIPTION}} | Should |
+| {{FEATURE_3}} | {{DESCRIPTION}} | Could |
+
+### 7.3 Technology (optional)
+
+{{ONLY INCLUDE IF TECH CHOICES HAVE PRODUCT IMPLICATIONS — e.g., real-time, offline support}}
+
+### 7.4 Assumptions
+
+| # | Assumption | How to Validate | Risk if Wrong |
+|---|-----------|-----------------|---------------|
+| 1 | {{ASSUMPTION_1}} | {{VALIDATION_METHOD}} | {{RISK}} |
+| 2 | {{ASSUMPTION_2}} | {{VALIDATION_METHOD}} | {{RISK}} |
+
+---
+
+## 8. Release Plan
+
+**Scope approach**: {{PHASED / BIG BANG / GRADUAL ROLLOUT}}
+
+| Phase | What's Included | Estimated Timeline |
+|-------|----------------|-------------------|
+| V1 (MVP) | {{MVP_SCOPE}} | {{RELATIVE_TIME}} |
+| V2 | {{V2_SCOPE}} | {{RELATIVE_TIME}} |
+| Future | {{FUTURE_ITEMS}} | TBD |
+
+**Out of scope (V1)**
+- {{OUT_OF_SCOPE_1}}
+- {{OUT_OF_SCOPE_2}}
+
+---
+
+## Open Questions
+
+| # | Question | Owner | Due |
+|---|----------|-------|-----|
+| 1 | {{QUESTION_1}} | {{OWNER}} | {{DATE}} |