@comfanion/workflow 3.0.0

package/src/opencode/checklists/requirements-checklist.md

@@ -0,0 +1,86 @@
+# Requirements Validation Checklist
+
+Use this checklist to validate requirements before proceeding to PRD creation.
+
+## Completeness Check
+
+### Functional Requirements
+- [ ] All major user workflows covered
+- [ ] Each FR has unique identifier (FR-XXX)
+- [ ] Each FR has priority assigned (P0/P1/P2)
+- [ ] Each FR has scope assigned (MVP/Growth/Vision)
+- [ ] No duplicate requirements
+
+### Non-Functional Requirements
+- [ ] Performance requirements defined with measurable targets
+- [ ] Security requirements identified
+- [ ] Scalability targets specified
+- [ ] Reliability/availability targets set
+- [ ] Compliance requirements listed (if applicable)
+
+### Coverage
+- [ ] All stakeholder needs addressed
+- [ ] All user personas have requirements
+- [ ] Edge cases and error scenarios considered
+- [ ] Integration points identified
+
+## SMART Criteria (Each FR must pass)
+
+### Specific
+- [ ] Requirement is clear and unambiguous
+- [ ] No vague terms like "fast", "user-friendly", "easy"
+- [ ] Scope is well-defined
+
+### Measurable
+- [ ] Has quantifiable acceptance criteria
+- [ ] Can be tested/verified
+- [ ] Success conditions are clear
+
+### Attainable
+- [ ] Technically feasible
+- [ ] Within project constraints (time, budget, resources)
+- [ ] Dependencies are available or planned
+
+### Relevant
+- [ ] Aligns with business objectives
+- [ ] Addresses user needs
+- [ ] Supports project goals
+
+### Traceable
+- [ ] Source is identified (stakeholder, research, etc.)
+- [ ] Can be traced to user journey or business objective
+- [ ] Will map to implementation artifacts
+
+## Quality Check
+
+### Consistency
+- [ ] No conflicting requirements
+- [ ] Terminology is consistent
+- [ ] Priority levels are logical
+
+### Structure
+- [ ] Requirements are properly categorized
+- [ ] Naming convention followed
+- [ ] Document structure is complete
+
+### Dependencies
+- [ ] Dependencies between requirements identified
+- [ ] No circular dependencies
+- [ ] External dependencies documented
+
+## Validation Summary
+
+| Category | Pass | Fail | Notes |
+|----------|------|------|-------|
+| Completeness | | | |
+| SMART Criteria | | | |
+| Quality | | | |
+
+**Overall Status:** PASS / NEEDS REVISION
+
+**Action Items:**
+1. [Item if any]
+2. [Item if any]
+
+**Validated By:** {{user_name}}
+**Date:** {{date}}

package/src/opencode/checklists/story-checklist.md

@@ -0,0 +1,137 @@
+# Story Validation Checklist
+
+Use this checklist to validate stories before marking them "ready-for-dev".
+
+## Story Structure
+
+### Required Sections
+- [ ] Story ID and Epic reference
+- [ ] Status clearly indicated
+- [ ] Priority and Estimate assigned
+- [ ] User Story format (As a... I want... So that...)
+- [ ] Acceptance Criteria (Given/When/Then)
+- [ ] Tasks/Subtasks defined
+- [ ] Dev Notes section
+- [ ] Definition of Done
+
+### Metadata
+- [ ] Created date
+- [ ] Last updated date
+
+## User Story Quality
+
+### Format
+- [ ] Follows "As a [persona], I want [capability], So that [benefit]"
+- [ ] Persona is valid (from PRD)
+- [ ] Capability is specific and actionable
+- [ ] Benefit is clear and valuable
+
+### Scope
+- [ ] Story is right-sized (1-3 days of work)
+- [ ] Not too large (split if needed)
+- [ ] Not too small (merge if needed)
+- [ ] Single focus - does one thing well
+
+## Acceptance Criteria Quality
+
+### Format
+- [ ] Uses Given/When/Then format
+- [ ] Each AC is independent
+- [ ] Each AC is testable
+
+### Coverage
+- [ ] Happy path covered
+- [ ] Error scenarios covered
+- [ ] Edge cases considered
+- [ ] Validation rules clear
+
+### Testability
+- [ ] Can write automated test for each AC
+- [ ] Expected outcomes are specific
+- [ ] No ambiguous terms
+
+## Tasks/Subtasks Quality
+
+### Structure
+- [ ] Tasks are in logical order
+- [ ] Each task is atomic (single action)
+- [ ] Subtasks break down complex tasks
+- [ ] Red-green-refactor cycle applicable
+
+### Completeness
+- [ ] Implementation tasks present
+- [ ] Test writing tasks present
+- [ ] Documentation tasks (if needed)
+- [ ] Integration tasks (if needed)
+
+### Clarity
+- [ ] Each task is actionable
+- [ ] File paths indicated where relevant
+- [ ] Dependencies between tasks clear
+
+## Dev Notes Quality
+
+### Context Provided
+- [ ] Architecture requirements noted
+- [ ] Related files/modules listed
+- [ ] Patterns to follow specified
+- [ ] Previous learnings documented
+
+### Technical Guidance
+- [ ] API/Interface definitions clear
+- [ ] Data model considerations noted
+- [ ] Integration points identified
+- [ ] Test scenarios suggested
+
+## Traceability
+
+### Backward Tracing
+- [ ] Maps to Epic
+- [ ] Maps to FR(s) from PRD
+- [ ] Maps to user journey
+
+### Forward Tracing
+- [ ] Can map to implementation files
+- [ ] Can map to test files
+
+## Definition of Done
+
+### Standard DoD Items
+- [ ] All AC implemented and verified
+- [ ] All tasks/subtasks complete
+- [ ] Unit tests written and passing
+- [ ] Integration tests (if required)
+- [ ] Code follows CLAUDE.md patterns
+- [ ] Code reviewed
+- [ ] No linting errors
+- [ ] Documentation updated
+- [ ] PR merged
+
+## Dependencies
+
+- [ ] Dependencies on other stories identified
+- [ ] External dependencies noted
+- [ ] Blockers documented (if any)
+
+## Validation Summary
+
+| Category | Pass | Fail | Notes |
+|----------|------|------|-------|
+| Story Structure | | | |
+| User Story Quality | | | |
+| AC Quality | | | |
+| Tasks Quality | | | |
+| Dev Notes | | | |
+| Traceability | | | |
+| DoD | | | |
+
+**Status:** READY-FOR-DEV / NEEDS REVISION
+
+**Issues Found:**
+1. [Issue if any]
+2. [Issue if any]
+
+**Ready for Dev:** YES / NO
+
+**Validated By:** {{user_name}}
+**Date:** {{date}}

package/src/opencode/commands/architecture.md

@@ -0,0 +1,68 @@
+---
+description: Create or update the Architecture document
+agent: architect
+model: anthropic/claude-sonnet-4-20250514
+---
+
+# Architecture Creation/Update
+
+## Arguments
+$ARGUMENTS
+
+- `create` or empty: Create new architecture
+- `edit`: Edit existing architecture
+
+## Prerequisites
+
+**Required:**
+- @docs/prd.md - Must exist and be validated
+
+**Reference:**
+- @CLAUDE.md - Coding standards (CRITICAL)
+
+**Check:**
+!`ls -la docs/prd.md 2>/dev/null && echo "PRD EXISTS" || echo "PRD MISSING - Run /prd first"`
+
+## Task
+
+**Create Mode:**
+1. Load skill: `architecture-design`
+2. Analyze PRD requirements
+3. Review existing codebase patterns (CLAUDE.md)
+4. Design:
+   - Module/service boundaries
+   - Data ownership
+   - Integration patterns
+5. Load skill: `adr-writing` for decisions
+6. Ensure NFR compliance
+7. Save to `docs/architecture.md`
+
+**Edit Mode:**
+1. Load existing @docs/architecture.md
+2. Identify change trigger (new requirement? issue?)
+3. Make targeted updates
+4. Update affected ADRs
+5. Check for ripple effects
+6. Save updated architecture
+
+## Alignment Checks
+
+- Follows hexagonal architecture (CLAUDE.md)
+- Matches existing code structure
+- NFRs have architectural support
+
+## Output
+
+- Architecture: `docs/architecture.md`
+- ADRs: `docs/architecture/adr/`
+
+## QA Reminder
+
+After architecture is complete, create QA artifact:
+`docs/architecture-integration-tests.md`
+
+Use template: `@.opencode/templates/integration-tests-template.md`
+
+## Next Step
+
+After completion, suggest: `/validate architecture`

package/src/opencode/commands/archive.md

@@ -0,0 +1,146 @@
+---
+description: Archive outdated documents while preserving history
+agent: archivist
+---
+
+# Archive Command
+
+## Arguments
+$ARGUMENTS
+
+Format: `[action] [path]`
+
+**Actions:**
+- "move [path]" - Archive a specific document
+- "sprint [sprint-N]" - Archive completed sprint
+- "list" - Show archive contents
+- "find [query]" - Search archive
+
+**Examples:**
+- `/archive move docs/research/technical/old-topic.md`
+- `/archive sprint sprint-0`
+- `/archive list`
+- `/archive find authentication`
+
+## Archive Policy
+
+**CRITICAL RULES:**
+1. Documents are NEVER deleted, only archived
+2. Every archived doc gets metadata (date, reason, superseded_by)
+3. References to archived docs must be updated
+4. Archive index must be updated
+
+## Current Archive State
+
+!`tree docs/archive/ 2>/dev/null || echo "Archive empty"`
+
+## Your Task
+
+### Archive Document (move)
+
+1. **Verify document exists**:
+   !`ls -la $1`
+
+2. **Ask for archive reason**:
+   - Superseded by new version?
+   - No longer relevant?
+   - Merged into another doc?
+
+3. **Add archive metadata** to document:
+   ```markdown
+   ---
+   archived: true
+   archived_date: YYYY-MM-DD
+   archived_reason: "[reason]"
+   superseded_by: "[path]"  # if applicable
+   original_path: "[original path]"
+   ---
+   
+   # [Title] (ARCHIVED)
+   
+   > **ARCHIVED:** This document was archived on YYYY-MM-DD.
+   > **Reason:** [reason]
+   > **Current Version:** [link] (if superseded)
+   ```
+
+4. **Determine archive path**:
+   - `docs/research/x.md` → `docs/archive/research/x-YYYY-MM-DD.md`
+   - `docs/prd.md` → `docs/archive/prd/prd-vX.Y-YYYY-MM-DD.md`
+   - `docs/architecture.md` → `docs/archive/architecture/architecture-vX.Y-YYYY-MM-DD.md`
+
+5. **Move document**:
+   ```bash
+   mkdir -p docs/archive/[type]/
+   mv [source] docs/archive/[type]/[name]-YYYY-MM-DD.md
+   ```
+
+6. **Update references**:
+   - Find docs that link to archived doc
+   - Update links or add "archived" notes
+
+7. **Update archive index**:
+   - Add entry to `docs/archive/README.md`
+
+### Archive Sprint
+
+1. **Verify sprint is complete**:
+   - All stories done
+   - Retrospective completed
+
+2. **Move entire sprint folder**:
+   ```bash
+   mv docs/sprint-artifacts/sprint-N docs/archive/sprint-artifacts/sprint-N
+   ```
+
+3. **Update sprint-status.yaml**:
+   - Mark sprint as archived
+   - Remove from active sprints
+
+4. **Update archive index**
+
+### List Archive
+
+Show contents organized by:
+- Type (research, prd, architecture, etc.)
+- Date (most recent first)
+- Status
+
+### Find in Archive
+
+Search archive by:
+- Document name
+- Content keywords
+- Date range
+
+## Archive Structure
+
+```
+docs/archive/
+├── README.md                    # Archive index
+├── research/
+│   └── [topic]-YYYY-MM-DD.md
+├── prd/
+│   └── prd-vX.Y-YYYY-MM-DD.md
+├── architecture/
+│   └── architecture-vX.Y-YYYY-MM-DD.md
+├── modules/
+│   └── [module]/
+├── coding-standards/
+│   └── [file]-YYYY-MM-DD.md
+└── sprint-artifacts/
+    └── sprint-N/
+```
+
+## Validation
+
+Before archiving:
+- [ ] Archive reason documented
+- [ ] Superseding doc exists (if applicable)
+- [ ] Archive metadata added
+- [ ] Target archive path correct
+
+After archiving:
+- [ ] Document moved successfully
+- [ ] References updated
+- [ ] Archive index updated
+- [ ] No broken links

package/src/opencode/commands/change.md

@@ -0,0 +1,169 @@
+---
+description: Manage change proposals for modifying existing documentation
+agent: change-manager
+---
+
+# Change Management
+
+## Arguments
+$ARGUMENTS
+
+**Actions:**
+- `new [name]` - Create new change proposal
+- `delta [change] [doc]` - Create delta for a document
+- `list` - List active change proposals
+- `show [name]` - Show change details
+- `review [name]` - Review for conflicts
+- `approve [name]` - Approve change
+- `reject [name] [reason]` - Reject change
+- `merge [name]` - Apply and archive
+
+## When to Use Change Proposals
+
+Use `/change` instead of direct edits when:
+- Changing > 10 lines
+- Affecting > 1 section
+- Changing multiple documents
+- Need stakeholder review
+- Want rollback capability
+
+For small edits, use direct commands like `/prd edit`.
+
+## Check Current Changes
+
+!`ls -la docs/changes/ 2>/dev/null || echo "No changes directory"`
+!`cat docs/changes/README.md 2>/dev/null || echo "No active changes"`
+
+## Actions
+
+### new [name]
+
+Create new change proposal:
+
+1. Create directory: `docs/changes/[name]/`
+2. Create `proposal.md` with template
+3. Ask user for:
+   - Summary
+   - Motivation
+   - Affected documents
+4. Update `docs/changes/README.md`
+
+### delta [change] [doc]
+
+Create delta for specific document:
+
+1. Load current document
+2. Ask what to ADD, MODIFY, REMOVE
+3. Create `docs/changes/[change]/deltas/[doc]-delta.md`
+4. Update proposal.md with affected doc
+
+### list
+
+Show all active change proposals with status.
+
+### show [name]
+
+Display:
+- Proposal summary
+- All deltas
+- Affected documents
+- Current status
+
+### review [name]
+
+Check for:
+1. **Parallel Changes** - Other proposals affecting same docs?
+2. **Stale Deltas** - Source docs changed since delta created?
+3. **Missing Deltas** - All affected docs have deltas?
+4. **Conflicts** - Any conflicting changes?
+
+Output review report with PASS/WARN/FAIL.
+
+### approve [name]
+
+1. Verify review passed
+2. Change status to "Approved"
+3. Update proposal.md
+4. Notify ready for merge
+
+### reject [name] [reason]
+
+1. Change status to "Rejected"
+2. Add rejection reason
+3. Move to `docs/archive/changes/`
+
+### merge [name]
+
+1. Verify status is "Approved"
+2. For each delta:
+   - Backup current document
+   - Apply changes
+   - Update version
+3. Update `docs/document-status.yaml`
+4. Archive change to `docs/archive/changes/`
+5. Update `docs/changes/README.md`
+
+## Directory Structure
+
+```
+docs/changes/
+├── README.md                    # Active changes index
+├── add-oauth/
+│   ├── proposal.md
+│   ├── tasks.md
+│   └── deltas/
+│       ├── requirements-delta.md
+│       ├── prd-delta.md
+│       └── architecture-delta.md
+└── refactor-auth/
+    ├── proposal.md
+    └── deltas/
+        └── architecture-delta.md
+```
+
+## Delta Format
+
+```markdown
+# Delta: PRD
+
+**Target:** docs/prd.md
+**Change:** add-oauth
+
+---
+
+## ADDED
+
+### OAuth2 Authentication
+
+New requirement for OAuth2 support with Google and GitHub providers.
+
+---
+
+## MODIFIED
+
+### Authentication Section
+
+**Before:**
+Users authenticate via email/password only.
+
+**After:**
+Users authenticate via email/password or OAuth2 (Google, GitHub).
+
+**Rationale:**
+User research shows 60% prefer social login.
+
+---
+
+## REMOVED
+
+(none)
+```
+
+## Validation
+
+Before merge:
+- [ ] All affected docs have deltas
+- [ ] No conflicting changes
+- [ ] Deltas not stale
+- [ ] Review completed
+- [ ] Approval granted