@comfanion/workflow 3.0.0

package/src/opencode/commands/help.md

@@ -0,0 +1,139 @@
+---
+description: Analyze project state and suggest next steps (context-aware guidance)
+agent: workflow-orchestrator
+---
+
+# Help Command
+
+## Arguments
+$ARGUMENTS
+
+- Empty: General guidance based on project state
+- "[question]": Specific guidance for a question
+- "blockers": Show blocking issues
+- "quick-wins": Show easy improvements
+
+## Analyze Current State
+
+### Check All Documents
+!`ls -la docs/requirements/requirements.md 2>/dev/null && echo "EXISTS" || echo "MISSING"`
+!`ls -la docs/prd.md 2>/dev/null && echo "EXISTS" || echo "MISSING"`
+!`ls -la docs/architecture.md 2>/dev/null && echo "EXISTS" || echo "MISSING"`
+!`ls docs/coding-standards/*.md 2>/dev/null | wc -l | xargs echo "Coding Standards files:"`
+!`ls docs/modules/*/README.md 2>/dev/null | wc -l | xargs echo "Module docs:"`
+!`ls docs/sprint-artifacts/*/epic-*.md 2>/dev/null | wc -l | xargs echo "Epics:"`
+!`cat docs/sprint-artifacts/sprint-status.yaml 2>/dev/null | head -20 || echo "No sprint status"`
+
+### Check Document Sizes
+!`wc -l docs/prd.md 2>/dev/null || echo "0"`
+!`wc -l docs/architecture.md 2>/dev/null || echo "0"`
+
+### Check for Stale Documents
+!`ls -lt docs/*.md docs/**/*.md 2>/dev/null | head -10`
+
+### Check Active Changes
+!`ls docs/changes/*/proposal.md 2>/dev/null | wc -l | xargs echo "Active change proposals:"`
+
+## Your Task
+
+1. **Determine Project Scale**
+   - L0: Hotfix (single file)
+   - L1: Small (< 5 requirements)
+   - L2: Medium (5-20 requirements)
+   - L3: Large (20-50 requirements)
+   - L4: Enterprise (50+ requirements)
+
+2. **Identify Current Phase**
+   - Requirements gathering
+   - Standards definition
+   - PRD creation
+   - Architecture design
+   - Module documentation
+   - Sprint planning
+   - Implementation
+
+3. **Detect Issues**
+   - Missing prerequisites
+   - Stale documents
+   - Size overflows (> 2000 lines)
+   - Validation gaps
+   - Conflicting information
+
+4. **Generate Recommendations**
+   - Required next steps
+   - Optional improvements
+   - Quick wins
+
+## Response Format
+
+```markdown
+## 🎯 Project Status
+
+**Scale:** L[N] ([type])
+**Phase:** [current phase]
+**Health:** [Good/Warning/Critical]
+
+---
+
+### 📊 Document Status
+
+| Document | Status | Lines | Issues |
+|----------|--------|-------|--------|
+| Requirements | ✅/⚠️/❌ | N | [issue] |
+| ...
+
+---
+
+### 🚨 Issues Found
+
+[List any issues with severity and fix command]
+
+---
+
+### 📋 Recommended Next Steps
+
+#### Required
+1. [Step with command]
+
+#### Optional  
+1. [Improvement with command]
+
+#### Quick Wins
+1. [Easy improvement]
+
+---
+
+### 💡 Context-Specific Tips
+
+[Based on user's question if provided]
+```
+
+## Scale-Adaptive Suggestions
+
+### L0 (Hotfix)
+```
+Skip full workflow. Just:
+1. Document the change
+2. Implement
+3. Test
+```
+
+### L1 (Small)
+```
+Minimal workflow:
+1. Brief requirements
+2. Implement
+3. Basic tests
+```
+
+### L2-L4 (Medium to Enterprise)
+```
+Full workflow with appropriate depth
+```
+
+## After Help
+
+User can:
+- Follow suggested commands
+- Ask for clarification
+- Request different approach

package/src/opencode/commands/jira-sync.md

@@ -0,0 +1,58 @@
+---
+description: Synchronize epics and stories with Jira
+agent: sm
+model: anthropic/claude-sonnet-4-20250514
+---
+
+# Jira Synchronization
+
+## Arguments
+$ARGUMENTS
+
+- `full` or empty: Full sync (create missing, update existing)
+- `status`: Sync status only
+- `epic [id]`: Sync specific epic
+
+## Prerequisites
+
+**Config:** @.opencode/jira-config.yaml
+
+**Environment:**
+```bash
+JIRA_USER=your-email@company.com
+JIRA_API_TOKEN=your-api-token
+```
+
+## Task
+
+1. Load skill: `jira-integration`
+2. Read jira-config.yaml for settings
+3. Based on mode:
+
+### Full Sync
+- Find all epics/stories without `jira_id`
+- Create in Jira
+- Store `jira_id` in files
+- Update status for existing items
+- Generate sync report
+
+### Status Sync
+- For items with `jira_id`
+- Compare local vs Jira status
+- Update whichever is behind
+
+### Epic Sync
+- Sync specific epic and its stories
+
+## Output
+
+- Updated epic/story files with Jira metadata
+- Sync report: `docs/sprint-artifacts/jira-sync-report.md`
+
+## Sync Report
+
+Shows:
+- Created issues
+- Updated statuses
+- Errors encountered
+- Next actions

package/src/opencode/commands/module-docs.md

@@ -0,0 +1,158 @@
+---
+description: Create detailed documentation for a module in docs/architecture/[module]/
+agent: module-docs
+---
+
+# Module Documentation
+
+## Arguments
+$ARGUMENTS
+
+- `[module-name]`: Create docs for specified module
+- `list`: List existing modules
+- `[module] add [type]`: Add specific file to module (api, events, scenarios, flows)
+
+## Module Location
+
+All modules live in `docs/architecture/[module-name]/`
+
+## Prerequisites Check
+
+1. **Main Architecture** - @docs/architecture.md (REQUIRED)
+2. **PRD** - @docs/prd.md (REQUIRED)
+
+!`ls -la docs/architecture.md 2>/dev/null || echo "ARCHITECTURE MISSING"`
+!`ls -la docs/prd.md 2>/dev/null || echo "PRD MISSING"`
+
+## Check Existing Modules
+
+!`ls -la docs/architecture/ 2>/dev/null || echo "No modules yet"`
+
+## Input Context
+
+Load:
+- @docs/architecture.md (REQUIRED)
+- @docs/prd.md (REQUIRED)
+- @docs/architecture-db.md (if exists)
+- @docs/coding-standards/README.md
+
+## Your Task
+
+### Create Mode: `/module-docs [module-name]`
+
+Create module directory and files:
+
+```
+docs/architecture/[module-name]/
+├── index.md                 # Overview (ALWAYS)
+├── architecture.md          # Module architecture (ALWAYS)
+├── prd.md                   # Module requirements (if needed)
+├── data-model.md            # DB schema (if has DB)
+├── domain.md                # Domain model (if DDD)
+```
+
+**Step by step:**
+
+1. Create directory `docs/architecture/[module-name]/`
+
+2. **index.md** (ALWAYS)
+   - Overview, purpose
+   - Quick links to other files
+   - Dependencies (depends on / depended by)
+   - Key metrics
+
+3. **architecture.md** (ALWAYS)
+   - Context diagram (ASCII)
+   - Layers (domain, application, infrastructure)
+   - Boundaries (owns vs references)
+   - Use cases table
+   - Communication (inbound/outbound)
+
+4. **prd.md** (if module has own requirements)
+   - Module-specific FRs
+   - Module-specific NFRs
+   - Subset of main PRD
+
+5. **data-model.md** (if module has database)
+   - Schema diagram (ASCII)
+   - Tables with columns
+   - Indexes
+   - Relationships
+   - Migrations list
+
+6. **domain.md** (if using DDD)
+   - Aggregates with diagrams
+   - State machines
+   - Value objects
+   - Domain services
+   - Domain events
+
+### Add Mode: `/module-docs [module] add [type]`
+
+Add subdirectory to existing module:
+
+| Type | Creates |
+|------|---------|
+| `api` | `api/index.md`, `api/openapi.yaml` |
+| `events` | `events/index.md` |
+| `scenarios` | `scenarios/` directory |
+| `flows` | `flows/` directory |
+| `integrations` | `integrations/` directory |
+| `decisions` | `decisions/adr-001.md` |
+
+### List Mode: `/module-docs list`
+
+Show all existing modules and their files.
+
+## Writing Rules
+
+1. **NO code** - Architecture and specs only
+2. **ASCII diagrams** - Box drawing characters
+3. **< 2000 lines** - Per file
+4. **Cross-references** - Link to main architecture (`../../architecture.md`)
+5. **Tables** - Structured, scannable
+
+## Output Structure
+
+```
+docs/architecture/[module]/
+├── index.md                 # Overview
+├── architecture.md          # Design
+├── prd.md                   # Requirements
+├── data-model.md            # DB schema
+├── domain.md                # DDD model
+│
+├── api/                     # If has API
+│   ├── index.md
+│   └── openapi.yaml
+│
+├── events/                  # If event-driven
+│   └── index.md
+│
+├── scenarios/               # Use case scenarios
+│   └── [scenario].md
+│
+├── flows/                   # Flow diagrams
+│   └── [flow].md
+│
+└── integrations/            # External integrations
+    └── [system].md
+```
+
+## Validation
+
+After creating, verify:
+- [ ] index.md and architecture.md present
+- [ ] Each file < 2000 lines
+- [ ] No code examples
+- [ ] ASCII diagrams present
+- [ ] Cross-references work (../../architecture.md)
+- [ ] Aligns with main architecture
+
+## After Completion
+
+Suggest:
+- `/validate module [name]` - Cascading validation
+- `/module-docs [name] add api` - Add API docs
+- `/module-docs [name] add events` - Add events docs
+- `/diagram [module] c4-component` - Component diagram

package/src/opencode/commands/prd.md

@@ -0,0 +1,63 @@
+---
+description: Create or update the Product Requirements Document
+agent: pm
+model: anthropic/claude-sonnet-4-20250514
+---
+
+# PRD Creation/Update
+
+## Arguments
+$ARGUMENTS
+
+- `create` or empty: Create new PRD
+- `edit`: Edit existing PRD
+
+## Prerequisites
+
+**Required:**
+- @docs/requirements/requirements.md - Must exist
+
+**Check:**
+!`ls -la docs/requirements/requirements.md 2>/dev/null && echo "EXISTS" || echo "MISSING - Run /requirements first"`
+
+## Task
+
+**Create Mode:**
+1. Load skill: `prd-writing`
+2. Review all requirements from requirements.md
+3. Collaborate to define:
+   - Project classification
+   - Success criteria
+   - MVP/Growth/Vision scope
+4. Structure into PRD sections
+5. Load skill: `acceptance-criteria` for writing AC
+6. Save to `docs/prd.md`
+
+**Edit Mode:**
+1. Load existing @docs/prd.md
+2. Ask what sections need updates
+3. Make targeted edits
+4. Update version in frontmatter
+5. Save updated PRD
+
+## Validation Before Save
+
+- All FRs from requirements.md addressed
+- All NFRs from requirements.md addressed
+- Success criteria are measurable
+- Scope boundaries clear
+
+## Output
+
+Save to: `docs/prd.md`
+
+## QA Reminder
+
+After PRD is complete, create QA artifact:
+`docs/prd-acceptance-criteria.md`
+
+Use template: `@.opencode/templates/prd-acceptance-criteria-template.md`
+
+## Next Step
+
+After completion, suggest: `/validate prd`

package/src/opencode/commands/quick.md

@@ -0,0 +1,166 @@
+---
+description: Quick mode for small changes - minimal documentation workflow
+agent: workflow-orchestrator
+---
+
+# Quick Mode
+
+## Purpose
+
+Skip the full workflow for small changes (L0-L1 scale):
+- Bug fixes
+- Minor features
+- Configuration changes
+- Small refactors
+
+## Arguments
+$ARGUMENTS
+
+Description of the change to make.
+
+Example:
+```
+/quick Fix login button not working on mobile
+/quick Add dark mode toggle to settings
+/quick Update API endpoint for user service
+```
+
+## Quick Mode Criteria
+
+Automatically used when:
+- Single file or < 5 files affected
+- No new requirements needed
+- No architecture changes
+- Estimated time < 2 hours
+
+## Quick Workflow
+
+```
+┌────────────────────┐
+│ 1. Quick Doc       │  Create minimal change doc
+│    (2-5 min)       │
+└────────┬───────────┘
+         │
+         ▼
+┌────────────────────┐
+│ 2. Implement       │  Make the change
+│    (varies)        │
+└────────┬───────────┘
+         │
+         ▼
+┌────────────────────┐
+│ 3. Test & Verify   │  Verify it works
+│    (5-10 min)      │
+└────────┬───────────┘
+         │
+         ▼
+┌────────────────────┐
+│ 4. Done            │  Log in change history
+└────────────────────┘
+```
+
+## Quick Doc Format
+
+Create `docs/changes/quick/[date]-[slug].md`:
+
+```markdown
+# Quick Change: [Title]
+
+**Date:** YYYY-MM-DD
+**Type:** Bug Fix | Minor Feature | Config | Refactor
+**Author:** [name]
+
+## Summary
+
+[One paragraph description]
+
+## Changes Made
+
+- [File 1]: [change]
+- [File 2]: [change]
+
+## Testing
+
+- [ ] [Test 1]
+- [ ] [Test 2]
+
+## Notes
+
+[Any additional context]
+```
+
+## Your Task
+
+1. **Analyze the request**
+   - Is this truly a quick change?
+   - What files will be affected?
+
+2. **If quick change appropriate:**
+   - Create quick doc
+   - Proceed with implementation guidance
+
+3. **If NOT quick change:**
+   - Explain why full workflow is needed
+   - Suggest appropriate command
+
+## Scale Check
+
+Before proceeding, verify:
+
+```
+IF affects > 5 files → Use full workflow
+IF adds new requirements → /requirements first
+IF changes architecture → /architecture edit
+IF affects multiple modules → /change new
+```
+
+## Quick Doc Location
+
+```
+docs/changes/quick/
+├── 2026-01-23-fix-mobile-login.md
+├── 2026-01-22-add-dark-mode.md
+└── ...
+```
+
+## Output
+
+For valid quick changes:
+
+```markdown
+## Quick Change: [Title]
+
+**Scale:** L0 (Hotfix) / L1 (Small)
+**Estimated Time:** [X] minutes/hours
+
+### Files to Modify
+
+1. `path/to/file.go` - [what to change]
+2. `path/to/test.go` - [add test]
+
+### Implementation Steps
+
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+### Testing Checklist
+
+- [ ] Manual test: [description]
+- [ ] Unit test added/updated
+- [ ] No regressions
+
+### Quick Doc Created
+
+`docs/changes/quick/YYYY-MM-DD-[slug].md`
+
+---
+
+Ready to implement? I can guide you through each step.
+```
+
+## After Quick Mode
+
+- Quick doc serves as change log
+- No need to update main docs
+- If pattern emerges, consider documenting in main docs

package/src/opencode/commands/requirements.md

@@ -0,0 +1,49 @@
+---
+description: Gather and document FR/NFR requirements through stakeholder interview
+agent: analyst
+model: anthropic/claude-sonnet-4-20250514
+---
+
+# Requirements Gathering
+
+## Arguments
+$ARGUMENTS
+
+Topic or area to focus requirements gathering (optional).
+
+## Prerequisites
+
+Check for existing context:
+- @docs/prd.md (if exists - for context)
+- @docs/architecture.md (if exists - for context)
+- @CLAUDE.md (project standards)
+
+## Task
+
+**If `docs/requirements/requirements.md` exists:**
+1. Review existing requirements
+2. Ask if user wants to ADD new requirements or EDIT existing
+3. Continue discovery from where it left off
+
+**If starting fresh:**
+1. Load skill: `requirements-gathering`
+2. Begin stakeholder interview
+3. Discover functional requirements (FR-XXX)
+4. Discover non-functional requirements (NFR-XXX)
+5. Structure into requirements.md
+
+## Validation Before Save
+
+Load skill: `requirements-validation`
+- All requirements have IDs
+- All requirements have acceptance criteria
+- No ambiguous language
+- Priorities are assigned
+
+## Output
+
+Save to: `docs/requirements/requirements.md`
+
+## Next Step
+
+After completion, suggest: `/validate requirements`