opencode-metis 0.1.0

package/opencode/skill/requirements-analysis/template.md

@@ -0,0 +1,177 @@
+---
+title: "[NEEDS CLARIFICATION: Feature title]"
+status: draft
+version: "1.0"
+---
+
+# Product Requirements Document
+
+## Validation Checklist
+
+### CRITICAL GATES (Must Pass)
+
+- [ ] All required sections are complete
+- [ ] No [NEEDS CLARIFICATION] markers remain
+- [ ] Problem statement is specific and measurable
+- [ ] Every feature has testable acceptance criteria (Gherkin format)
+- [ ] No contradictions between sections
+
+### QUALITY CHECKS (Should Pass)
+
+- [ ] Problem is validated by evidence (not assumptions)
+- [ ] Context → Problem → Solution flow makes sense
+- [ ] Every persona has at least one user journey
+- [ ] All MoSCoW categories addressed (Must/Should/Could/Won't)
+- [ ] Every metric has corresponding tracking events
+- [ ] No feature redundancy (check for duplicates)
+- [ ] No technical implementation details included
+- [ ] A new team member could understand this PRD
+
+---
+
+## Product Overview
+
+### Vision
+[NEEDS CLARIFICATION: What is the one-sentence vision for this feature? What future state are we creating for users?]
+
+### Problem Statement
+[NEEDS CLARIFICATION: What specific problem are users facing today? Why is this painful for them? What are the consequences of not solving this?]
+
+### Value Proposition
+[NEEDS CLARIFICATION: Why will users choose this solution over alternatives? What unique value does it provide? How does it make their life better?]
+
+## User Personas
+
+### Primary Persona: [NEEDS CLARIFICATION: persona name]
+- **Demographics:** [Age range, role/occupation, technical expertise level]
+- **Goals:** [What are they trying to accomplish? What does success look like for them?]
+- **Pain Points:** [What frustrates them about current solutions? What obstacles do they face?]
+
+### Secondary Personas
+[NEEDS CLARIFICATION: Are there other user types? If yes, define them. If no, remove this section]
+
+## User Journey Maps
+
+### Primary User Journey: [NEEDS CLARIFICATION: Journey name]
+1. **Awareness:** [How do users discover they have this need?]
+2. **Consideration:** [What alternatives do they evaluate? What criteria matter to them?]
+3. **Adoption:** [What convinces them to try this solution?]
+4. **Usage:** [What are the key steps in using the feature?]
+5. **Retention:** [What keeps them coming back?]
+
+### Secondary User Journeys
+[NEEDS CLARIFICATION: Are there other user journeys? If yes, define them. If no, remove this section]
+
+## Feature Requirements
+
+### Must Have Features
+[NEEDS CLARIFICATION: What are the absolute minimum features needed for this to be valuable to users?]
+
+#### Feature 1: [NEEDS CLARIFICATION: Feature name]
+- **User Story:** As a [user type], I want to [action] so that [benefit]
+- **Acceptance Criteria (Gherkin Format):**
+
+  Use the Given/When/Then structure for each criterion:
+  - `Given` [precondition or initial state]
+  - `When` [user action or system event]
+  - `Then` [expected observable outcome]
+  - `And` [additional outcomes if needed]
+
+  **Good Example:**
+  - [ ] Given the user has entered valid credentials, When they submit the login form, Then they are redirected to the dashboard within 2 seconds
+
+  **Bad Example:**
+  - [ ] User can log in _(vague, not testable)_
+
+  Criteria:
+  - [ ] Given [state], When [action], Then [outcome]
+  - [ ] Given [state], When [action], Then [outcome]
+  - [ ] Given [edge case], When [action], Then [correct behavior]
+
+#### Feature 2: [NEEDS CLARIFICATION: Feature name]
+[Repeat structure as needed]
+
+### Should Have Features
+[NEEDS CLARIFICATION: What would significantly improve the experience but isn't critical for launch?]
+
+### Could Have Features
+[NEEDS CLARIFICATION: What nice-to-haves could we add if time and resources permit?]
+
+### Won't Have (This Phase)
+[NEEDS CLARIFICATION: What is explicitly out of scope for this phase? What are we NOT building?]
+
+## Detailed Feature Specifications
+
+### Feature: [NEEDS CLARIFICATION: Pick the most complex feature from above]
+**Description:** [Detailed explanation of how this feature works]
+
+**User Flow:**
+1. User [First action]
+2. System [Response]
+3. User [Next action]
+
+**Business Rules:**
+- Rule 1: [Specification - When X happens, then Y should occur]
+- Rule X: ...
+
+**Edge Cases:**
+- Scenario 1: [What could go wrong?] → Expected: [How should system handle it?]
+- Scenario X: ...
+
+## Success Metrics
+
+### Key Performance Indicators
+[NEEDS CLARIFICATION: How will we measure if this feature is successful?]
+
+- **Adoption:** [Target number/percentage of users who try the feature]
+- **Engagement:** [Target frequency of use or actions per user]
+- **Quality:** [Target error rate, success rate, or satisfaction score]
+- **Business Impact:** [Revenue, retention, or other business metric]
+
+### Tracking Requirements
+[NEEDS CLARIFICATION: What user actions and data points must we track to validate our success metrics and make informed product decisions?]
+
+| Event | Properties | Purpose |
+|-------|------------|---------|
+| [User action] | [What data to capture] | [Why we track this] |
+
+---
+
+## Constraints and Assumptions
+
+### Constraints [NEEDS CLARIFICATION: What are limiting factors]
+- [Budget, timeline, or resource limitations]
+- [Technical or platform constraints]
+- [Legal or compliance requirements]
+
+### Assumptions [NEEDS CLARIFICATION: What are we assuming that is not explicitly defined]
+- [What are we assuming about users?]
+- [What are we assuming about the market?]
+- [What dependencies are we assuming will be available?]
+
+## Risks and Mitigations
+[NEEDS CLARIFICATION: What are potential risks? How do we intend to tackle them?]
+
+| Risk | Impact | Likelihood | Mitigation |
+|------|--------|------------|------------|
+| [Risk description] | [High/Medium/Low] | [High/Medium/Low] | [How to prevent or handle] |
+
+## Open Questions
+[NEEDS CLARIFICATION: What requires more external input? What decisions do we need to continue?]
+
+- [ ] [Question that needs stakeholder input]
+- [ ] [Decision that needs to be made]
+- [ ] [Information that needs to be gathered]
+
+---
+
+## Supporting Research
+
+### Competitive Analysis
+[NEEDS CLARIFICATION: How do competitors solve this problem? What can we learn from them?]
+
+### User Research
+[NEEDS CLARIFICATION: What user research has been done? Key findings?]
+
+### Market Data
+[NEEDS CLARIFICATION: Any relevant market size, trends, or data points?]

package/opencode/skill/requirements-analysis/validation.md

@@ -0,0 +1,69 @@
+# PRD Validation Checklist
+
+Use this checklist to validate PRD completeness before proceeding to SDD.
+
+## Structure Validation
+
+- [ ] **All required sections are complete** - No empty or placeholder sections
+- [ ] **No [NEEDS CLARIFICATION] markers remain** - All markers replaced with content
+- [ ] **Template structure preserved** - No sections added, removed, or reorganized
+
+## Content Quality
+
+### Problem Definition
+- [ ] **Problem statement is specific and measurable** - Clear metrics for problem impact
+- [ ] **Problem is validated by evidence** - Data, user research, or market analysis (not assumptions)
+- [ ] **Context → Problem → Solution flow makes sense** - Logical narrative
+
+### User Understanding
+- [ ] **Every persona has demographics** - Age, role, technical expertise
+- [ ] **Every persona has goals** - What success looks like for them
+- [ ] **Every persona has pain points** - Current frustrations
+- [ ] **Every persona has at least one user journey** - End-to-end flow
+
+### Requirements Quality
+- [ ] **All MoSCoW categories addressed** - Must/Should/Could/Won't all defined
+- [ ] **Every feature has a user story** - As a [user], I want [action] so that [benefit]
+- [ ] **Every feature has testable acceptance criteria** - Specific, verifiable conditions
+- [ ] **No feature redundancy** - Check for duplicates or overlapping features
+- [ ] **No contradictions between sections** - Consistent throughout
+
+### Success Criteria
+- [ ] **KPIs defined for adoption** - User acquisition/activation targets
+- [ ] **KPIs defined for engagement** - Usage frequency/depth targets
+- [ ] **KPIs defined for quality** - Error rate, satisfaction targets
+- [ ] **KPIs defined for business impact** - Revenue, retention targets
+- [ ] **Every metric has corresponding tracking events** - How to measure
+
+### Constraints & Risks
+- [ ] **Constraints identified** - Budget, timeline, technical, compliance
+- [ ] **Assumptions documented** - Explicit about what we're assuming
+- [ ] **Risks identified with mitigations** - What could go wrong and how to handle
+
+## Boundary Validation
+
+- [ ] **No technical implementation details included** - No code, architecture, or database design
+- [ ] **No API specifications** - Belongs in SDD
+- [ ] **Focus on WHAT and WHY, not HOW** - Business requirements only
+
+## Clarity Validation
+
+- [ ] **A new team member could understand this PRD** - Self-contained and clear
+- [ ] **Jargon is defined** - Domain terms explained
+- [ ] **Acronyms are expanded** - First use includes full form
+
+## Cross-Section Consistency
+
+Run these checks across the entire document:
+- [ ] **User personas match user journeys** - All personas have journeys
+- [ ] **Features align with user goals** - Each feature maps to a persona goal
+- [ ] **Metrics map to features** - Success measured for key features
+- [ ] **Risks relate to requirements** - Identified risks are relevant
+
+## Completion Criteria
+
+✅ **PRD is complete when:**
+- All checklist items pass
+- User has reviewed and approved content
+- No open questions remain
+- Ready for technical specification (SDD)