trinity-method-sdk 2.0.0

package/dist/templates/shared/claude-commands/trinity-verify.md.template

@@ -0,0 +1,453 @@
+---
+description: Verify Trinity Method installation completeness
+---
+
+Verify that Trinity Method is properly installed in this project.
+
+Check for:
+1. **Trinity Core Structure (14 directories):**
+   - trinity/knowledge-base/
+   - trinity/reports/
+   - trinity/sessions/
+   - trinity/investigations/
+   - trinity/investigations/plans/
+   - trinity/patterns/
+   - trinity/work-orders/
+   - trinity/templates/
+   - trinity/templates/work-orders/
+   - trinity/templates/investigations/
+   - trinity/archive/work-orders/
+   - trinity/archive/investigations/
+   - trinity/archive/reports/
+   - trinity/archive/sessions/
+
+2. **CLAUDE.md Context Files:**
+   - Root CLAUDE.md (behavioral hierarchy)
+   - trinity/CLAUDE.md (Trinity-specific context)
+
+3. **Agent Organization (19 agents in 5 subdirectories):**
+   - .claude/agents/leadership/ (3 agents: ALY, AJ MAESTRO, AJ CC)
+   - .claude/agents/deployment/ (4 agents: TAN, ZEN, INO, EIN)
+   - .claude/agents/audit/ (1 agent: JUNO)
+   - .claude/agents/planning/ (4 agents: MON, ROR, TRA, EUS)
+   - .claude/agents/aj-team/ (7 agents: KIL, BAS, DRA, APO, BON, CAP, URO)
+
+4. **Slash Commands (20 commands in 6 categories):**
+   - .claude/commands/ (all Trinity slash commands)
+   - Session: start, continue, end
+   - Planning: requirements, design, plan, decompose
+   - Execution: orchestrate, audit, readme, docs, changelog
+   - Investigation: create-investigation, plan-investigation, investigate-templates
+   - Infrastructure: init
+   - Utility: verify, agents, workorder
+
+5. **Templates (13 total):**
+   - Work Orders: 6 templates in trinity/templates/work-orders/
+   - Investigations: 5 templates in trinity/templates/investigations/
+   - Documentation: 2 templates in trinity/templates/documentation/
+
+6. **Knowledge Base Files (9 files):**
+   - ARCHITECTURE.md, Trinity.md, To-do.md, ISSUES.md, Technical-Debt.md
+   - CODING-PRINCIPLES.md, TESTING-PRINCIPLES.md
+   - AI-DEVELOPMENT-GUIDE.md, DOCUMENTATION-CRITERIA.md
+
+7. **CI/CD Workflows (if deployed):**
+   - .github/workflows/ci.yml (BAS 6-phase quality gates)
+   - .github/workflows/cd.yml (Deployment pipeline)
+
+Report:
+- ✅ Installed components
+- ❌ Missing components
+- Deployment completeness percentage
+- Next steps if incomplete
+
+---
+
+## Example Verification Reports
+
+### Example 1: Complete Installation (100%)
+
+```markdown
+# Trinity v2.0 Verification Report
+
+**Project**: MyApp
+**Date**: 2025-12-18
+**Trinity Version**: v2.0.0
+
+## Verification Results: ✅ 100% COMPLETE
+
+### 1. Directory Structure ✅
+- ✅ .claude/
+- ✅ .claude/agents/ (5 subdirectories)
+- ✅ .claude/commands/
+- ✅ trinity/knowledge-base/
+- ✅ trinity/work-orders/
+- ✅ trinity/sessions/
+- ✅ trinity/planning/
+- ✅ trinity/reports/
+
+### 2. Agent Deployment ✅ (19/19)
+**Leadership** (3/3):
+- ✅ aly-cto.md (2.4 KB)
+- ✅ aj-maestro.md (18.2 KB)
+- ✅ aj-cc.md (12.1 KB)
+
+**Deployment** (4/4):
+- ✅ tan-structure.md (8.5 KB)
+- ✅ zen-knowledge.md (6.2 KB)
+- ✅ ino-context.md (5.8 KB)
+- ✅ ein-cicd.md (7.1 KB)
+
+**Planning** (4/4):
+- ✅ mon-requirements.md (9.3 KB)
+- ✅ ror-design.md (11.2 KB)
+- ✅ tra-planner.md (8.7 KB)
+- ✅ eus-decomposer.md (7.4 KB)
+
+**AJ Team** (7/7):
+- ✅ kil-task-executor.md (10.5 KB)
+- ✅ bas-quality-gate.md (14.8 KB)
+- ✅ dra-code-reviewer.md (9.6 KB)
+- ✅ apo-documentation-specialist.md (6.9 KB)
+- ✅ bon-dependency-manager.md (7.2 KB)
+- ✅ cap-configuration-specialist.md (6.5 KB)
+- ✅ uro-refactoring-specialist.md (7.8 KB)
+
+**Audit** (1/1):
+- ✅ juno-auditor.md (12.3 KB)
+
+### 3. Slash Commands ✅ (15/15)
+- ✅ trinity-init.md
+- ✅ trinity-verify.md
+- ✅ trinity-start.md
+- ✅ trinity-agents.md
+- ✅ trinity-requirements.md
+- ✅ trinity-design.md
+- ✅ trinity-plan.md
+- ✅ trinity-decompose.md
+- ✅ trinity-continue.md
+- ✅ trinity-end.md
+- ✅ trinity-workorder.md
+- ✅ trinity-create-investigation.md
+- ✅ trinity-plan-investigation.md
+- ✅ trinity-investigate-templates.md
+- ✅ trinity-orchestrate.md
+
+### 4. Knowledge Base ✅ (9/9)
+- ✅ ARCHITECTURE.md (populated)
+- ✅ Trinity.md (populated)
+- ✅ To-do.md (populated)
+- ✅ ISSUES.md (populated)
+- ✅ Technical-Debt.md (populated)
+- ✅ CODING-PRINCIPLES.md (populated)
+- ✅ TESTING-PRINCIPLES.md (populated)
+- ✅ AI-DEVELOPMENT-GUIDE.md (populated)
+- ✅ DOCUMENTATION-CRITERIA.md (populated)
+
+### 5. CI/CD Workflows ✅ (Optional)
+- ✅ .github/workflows/ci.yml (BAS 6-phase gates)
+- ✅ .github/workflows/cd.yml (Deployment pipeline)
+
+## Summary
+**Status**: ✅ FULLY DEPLOYED
+**Completeness**: 100%
+**Next Steps**: Trinity v2.0 is ready to use. Run `/trinity-start` to begin your first workflow.
+```
+
+---
+
+### Example 2: Incomplete Installation (82%)
+
+```markdown
+# Trinity v2.0 Verification Report
+
+**Project**: PartialApp
+**Date**: 2025-12-18
+**Trinity Version**: v2.0.0
+
+## Verification Results: ⚠️ 82% INCOMPLETE
+
+### 1. Directory Structure ⚠️
+- ✅ .claude/
+- ✅ .claude/agents/ (5 subdirectories)
+- ✅ .claude/commands/
+- ✅ trinity/knowledge-base/
+- ❌ trinity/work-orders/ (MISSING)
+- ✅ trinity/sessions/
+- ✅ trinity/planning/
+- ❌ trinity/reports/ (MISSING)
+
+### 2. Agent Deployment ⚠️ (17/19)
+**Leadership** (3/3):
+- ✅ aly-cto.md
+- ✅ aj-maestro.md
+- ✅ aj-cc.md
+
+**Deployment** (2/4):
+- ✅ tan-structure.md
+- ✅ zen-knowledge.md
+- ❌ ino-context.md (MISSING)
+- ❌ ein-cicd.md (MISSING)
+
+**Planning** (4/4):
+- ✅ All present
+
+**AJ Team** (7/7):
+- ✅ All present
+
+**Audit** (1/1):
+- ✅ juno-auditor.md
+
+### 3. Slash Commands ✅ (15/15)
+- ✅ All present
+
+### 4. Knowledge Base ⚠️ (7/9)
+- ✅ ARCHITECTURE.md (populated)
+- ✅ Trinity.md (populated)
+- ✅ To-do.md (EMPTY - needs population)
+- ✅ ISSUES.md (EMPTY - needs population)
+- ✅ Technical-Debt.md (populated)
+- ✅ CODING-PRINCIPLES.md (populated)
+- ✅ TESTING-PRINCIPLES.md (populated)
+- ❌ AI-DEVELOPMENT-GUIDE.md (MISSING)
+- ❌ DOCUMENTATION-CRITERIA.md (MISSING)
+
+### 5. CI/CD Workflows ❌
+- ❌ Not deployed (optional - not affecting score)
+
+## Issues Found
+
+**Critical** (Blocking deployment):
+- Missing 2 deployment agents (INO, EIN)
+- Missing 2 knowledge base files
+
+**Warning** (Should fix):
+- 2 empty knowledge base files (To-do.md, ISSUES.md)
+- Missing work-orders and reports directories
+
+## Summary
+**Status**: ⚠️ INCOMPLETE DEPLOYMENT
+**Completeness**: 82%
+**Blocking Issues**: 4 critical components missing
+
+**Next Steps**:
+1. Re-run `/trinity-init` to deploy missing components
+2. Populate empty knowledge base files
+3. Create missing directories manually if needed
+```
+
+---
+
+## Troubleshooting Common Issues
+
+### Issue 1: Missing Directories
+
+**Symptom**:
+```
+❌ trinity/work-orders/ not found
+❌ trinity/reports/ not found
+```
+
+**Cause**: Incomplete `trinity deploy` or TAN agent failure
+
+**Fix**:
+```bash
+# Manually create missing directories
+mkdir -p trinity/work-orders
+mkdir -p trinity/reports
+mkdir -p trinity/sessions
+mkdir -p trinity/planning
+
+# Verify creation
+ls -la trinity/
+```
+
+**Verification**:
+```bash
+# Should show all directories
+trinity/
+├── work-orders/
+├── reports/
+├── sessions/
+├── planning/
+└── knowledge-base/
+```
+
+---
+
+### Issue 2: Missing Agent Files
+
+**Symptom**:
+```
+❌ .claude/agents/deployment/ino-context.md not found
+❌ .claude/agents/deployment/ein-cicd.md not found
+```
+
+**Cause**: Partial deployment or TAN agent error during agent file creation
+
+**Fix**:
+```bash
+# Re-run Trinity initialization
+/trinity-init
+
+# OR manually deploy specific agents
+trinity deploy --agents-only
+
+# OR reinstall Trinity SDK
+npm install @trinity-method/sdk@latest
+```
+
+**Verification**:
+```bash
+# Count agent files (should be 19)
+find .claude/agents -name "*.md" | wc -l
+
+# List all agents
+find .claude/agents -name "*.md" -type f
+```
+
+---
+
+### Issue 3: Empty Knowledge Base Files
+
+**Symptom**:
+```
+⚠️ ISSUES.md exists but is empty (0 bytes)
+⚠️ To-do.md exists but is empty (0 bytes)
+```
+
+**Cause**: ZEN agent created files but did not populate with template content
+
+**Fix**:
+```bash
+# Re-populate knowledge base
+/trinity-init
+
+# OR manually populate files
+# ISSUES.md should contain:
+echo "# Known Issues\n\nNo issues currently tracked." > trinity/knowledge-base/ISSUES.md
+
+# To-do.md should contain:
+echo "# Project To-Do List\n\nNo tasks currently tracked." > trinity/knowledge-base/To-do.md
+```
+
+**Verification**:
+```bash
+# Check file sizes (should be >0 bytes)
+ls -lh trinity/knowledge-base/*.md
+
+# Verify content
+cat trinity/knowledge-base/ISSUES.md
+cat trinity/knowledge-base/To-do.md
+```
+
+---
+
+### Issue 4: Wrong CLAUDE.md Locations
+
+**Symptom**:
+```
+❌ CLAUDE.md found in project root (should be in .claude/)
+❌ .claude/CLAUDE.md not found
+```
+
+**Cause**: INO agent did not create proper CLAUDE.md hierarchy
+
+**Fix**:
+```bash
+# Remove incorrect CLAUDE.md
+rm CLAUDE.md  # if in wrong location
+
+# Re-run INO agent via /trinity-init
+/trinity-init
+
+# OR manually create hierarchy
+# .claude/CLAUDE.md (global)
+# .claude/agents/CLAUDE.md (agent-specific)
+```
+
+**Verification**:
+```bash
+# Verify CLAUDE.md hierarchy
+find .claude -name "CLAUDE.md"
+
+# Expected output:
+# .claude/CLAUDE.md
+# .claude/agents/CLAUDE.md
+```
+
+---
+
+### Issue 5: Slash Commands Not Working
+
+**Symptom**:
+```
+Command '/trinity-start' not found
+Command '/trinity-verify' not recognized
+```
+
+**Cause**: Slash command files not deployed to .claude/commands/
+
+**Fix**:
+```bash
+# Verify commands directory exists
+ls -la .claude/commands/
+
+# If missing, re-deploy
+/trinity-init
+
+# OR manually install commands
+trinity deploy --commands-only
+
+# Restart Claude Code (reload window)
+```
+
+**Verification**:
+```bash
+# Count command files (should be 15)
+ls .claude/commands/*.md | wc -l
+
+# Test a command
+/trinity-verify
+```
+
+---
+
+### Issue 6: CI/CD Workflows Missing (Normal vs Issue)
+
+**Symptom**:
+```
+ℹ️ .github/workflows/ not found
+```
+
+**This is NORMAL if**:
+- You did not request CI/CD integration
+- EIN agent was not invoked
+- Project doesn't use GitHub Actions
+
+**This is an ISSUE if**:
+- You explicitly requested CI/CD setup
+- EIN agent was supposed to run but failed
+
+**Fix (if needed)**:
+```bash
+# Deploy CI/CD workflows
+/trinity-init  # with EIN option
+
+# OR manually create workflows
+mkdir -p .github/workflows
+# Copy workflow templates from Trinity SDK
+```
+
+**Verification**:
+```bash
+# Check if workflows exist
+ls -la .github/workflows/
+
+# Expected (if CI/CD requested):
+# ci.yml
+# cd.yml
+```
+
+---
+

package/dist/templates/shared/claude-commands/trinity-workorder.md.template

@@ -0,0 +1,249 @@
+---
+description: Create Trinity Method work orders interactively
+---
+
+# Trinity Work Orders
+
+## What Are Work Orders?
+
+Work orders are structured task documents that provide clear objectives, task breakdown, progress tracking, context preservation, and quality assurance.
+
+**Purpose**: Bridge gap between user requests and systematic implementation.
+
+---
+
+## When to Use Work Orders
+
+**Use For**: Medium/Large tasks (3+ files), session-spanning work, team collaboration, audit trail needed
+
+**Skip For**: Small tasks (1-2 files), one-off experiments, trivial changes
+
+---
+
+## Work Order Naming
+
+**Format**: `WO-XXX-{brief-title}.md`
+
+Examples: WO-042-jwt-refresh-implementation.md
+
+---
+
+## Direct Work Order Creation
+
+When `/trinity-workorder` is invoked, the agent will:
+
+1. **Analyze user's request** to determine:
+   - Work order type (Investigation/Implementation/Analysis/Audit/Pattern/Verification)
+   - Task description and objectives
+   - Deliverables and acceptance criteria
+   - Priority and estimated effort
+
+2. **Select appropriate template** from `trinity/templates/work-orders/`:
+   - **Investigation:** Research and analysis tasks
+   - **Implementation:** Feature development tasks
+   - **Analysis:** Code analysis and review tasks
+   - **Audit:** Quality and compliance audits
+   - **Pattern:** Pattern detection and analysis
+   - **Verification:** Verification and validation tasks
+
+3. **Create work order file** in `trinity/work-orders/WO-XXX-{task-name}.md`
+
+4. **Populate template** with:
+   - Clear mission objective
+   - Implementation scope and affected files
+   - Deliverable requirements
+   - Success criteria
+   - After completion instructions
+
+5. **Report completion** to user with work order file path
+
+**No Interactive Wizard:** The agent proceeds directly without asking questions. All necessary information is inferred from the user's request or filled with reasonable defaults.
+
+**User Override:** If specific details are needed, the agent may ask clarifying questions, but default is to proceed autonomously.
+
+**Example Usage:**
+```bash
+# Agent analyzes request and creates WO-043-implement-dark-mode.md
+/trinity-workorder "Implement dark mode toggle in application settings"
+
+# Then execute:
+/trinity-orchestrate @WO-043-implement-dark-mode.md
+```
+
+---
+
+## Orchestration
+
+Once work order is created in `trinity/work-orders/`, execute it:
+
+```bash
+/trinity-orchestrate @WO-001-example-task.md
+```
+
+**AJ MAESTRO** picks up the work order from `trinity/work-orders/` and orchestrates the 19-agent team to complete the task following Trinity Method workflows.
+
+---
+
+## Complete Example
+
+See WO-042 example in work order files showing full structure with objectives, implementation plan, testing strategy, and progress tracking.
+
+---
+
+## Available Templates
+
+Work order templates are located in `trinity/templates/work-orders/`:
+- **INVESTIGATION-TEMPLATE.md** - Research and analysis tasks
+- **IMPLEMENTATION-TEMPLATE.md** - Feature development tasks
+- **ANALYSIS-TEMPLATE.md** - Code analysis and review tasks
+- **AUDIT-TEMPLATE.md** - Quality and compliance audits
+- **PATTERN-TEMPLATE.md** - Pattern detection and analysis
+- **VERIFICATION-TEMPLATE.md** - Verification and validation tasks
+
+---
+
+## Real-World Examples
+
+### Example 1: Implementation Work Order
+**Work Order:** WO-042-jwt-refresh-implementation
+**Template:** Implementation
+**Priority:** High
+**Estimated Time:** 2 days
+
+**Objectives:**
+1. Implement automatic JWT token refresh
+2. Handle edge cases (expired tokens, race conditions)
+3. Add comprehensive test coverage
+
+**Deliverables:**
+- Token refresh middleware
+- Unit tests (≥80% coverage)
+- Integration tests for refresh flow
+- API documentation update
+
+**Outcome:**
+- Completed in 1.5 days
+- Test coverage: 92%
+- All acceptance criteria met
+- Zero production incidents post-deployment
+
+---
+
+### Example 2: Investigation Work Order
+**Work Order:** WO-015-database-performance-analysis
+**Template:** Investigation
+**Priority:** Critical
+**Estimated Time:** 1 day
+
+**Objectives:**
+1. Identify cause of 300% increase in query times
+2. Analyze database query patterns
+3. Recommend optimization strategy
+
+**Deliverables:**
+- Performance analysis report
+- Query execution plan analysis
+- Optimization recommendations with effort estimates
+
+**Outcome:**
+- Root cause: Missing indexes on new user_metadata table
+- Recommended 3 compound indexes
+- Created follow-up work order WO-016 for implementation
+
+---
+
+### Example 3: Audit Work Order
+**Work Order:** WO-023-security-dependency-audit
+**Template:** Audit
+**Priority:** Medium
+**Estimated Time:** 4 hours
+
+**Objectives:**
+1. Audit all npm dependencies for vulnerabilities
+2. Assess CVSS scores and exploitability
+3. Create remediation plan
+
+**Deliverables:**
+- Dependency vulnerability report
+- Risk assessment (Critical/High/Medium/Low)
+- Upgrade path for vulnerable packages
+
+**Outcome:**
+- 12 vulnerabilities found (3 critical, 5 high, 4 medium)
+- All critical issues resolved immediately
+- Documented upgrade blockers for 2 high-severity issues
+
+---
+
+### Example 4: Analysis Work Order
+**Work Order:** WO-031-codebase-complexity-analysis
+**Template:** Analysis
+**Priority:** Low
+**Estimated Time:** 1 day
+
+**Objectives:**
+1. Analyze codebase complexity metrics
+2. Identify refactoring candidates
+3. Prioritize technical debt reduction
+
+**Deliverables:**
+- Complexity metrics report (cyclomatic complexity, coupling)
+- Top 10 files needing refactoring
+- Technical debt reduction roadmap
+
+**Outcome:**
+- Identified 8 files with cyclomatic complexity >15
+- Created 4 follow-up work orders for refactoring
+- Established baseline metrics for future tracking
+
+---
+
+### Example 5: Verification Work Order
+**Work Order:** WO-050-production-deployment-verification
+**Template:** Verification
+**Priority:** Critical
+**Estimated Time:** 2 hours
+
+**Objectives:**
+1. Verify payment processing deployment to production
+2. Validate all smoke tests pass
+3. Confirm monitoring and alerts operational
+
+**Deliverables:**
+- Deployment verification checklist (completed)
+- Smoke test results (all passing)
+- Rollback plan (if needed)
+
+**Outcome:**
+- All 24 smoke tests passed
+- Monitoring confirmed normal operation
+- No rollback required
+- Payment processing 100% operational
+
+---
+
+## Template Selection Guide
+
+**Use this decision tree:**
+
+```
+Do you need to implement new code or features?
+  → YES: Use Implementation Template
+
+Do you need to research or investigate something?
+  → YES: Use Investigation Template
+
+Do you need to analyze code, architecture, or metrics?
+  → YES: Use Analysis Template
+
+Do you need to audit quality, security, or compliance?
+  → YES: Use Audit Template
+
+Do you need to identify or document patterns?
+  → YES: Use Pattern Template
+
+Do you need to verify deployment or validate results?
+  → YES: Use Verification Template
+```
+
+---