trinity-method-sdk 2.0.0

package/dist/templates/work-orders/INVESTIGATION-TEMPLATE.md.template

@@ -0,0 +1,206 @@
+# ORCHESTRATOR WORK ORDER #XXX
+## Type: INVESTIGATION
+## [Investigation Title]
+
+---
+
+## AUTHORIZATION
+
+```
+TRINITY COUNCIL APPROVAL:
+☑ LUKA: APPROVED - [Approval reason]
+☑ TRINITY: APPROVED - [Technical justification]
+☑ CC: PENDING - Awaiting your acknowledgment
+
+STATUS: APPROVED FOR EXECUTION
+```
+
+---
+
+## MISSION OBJECTIVE
+
+[Clear, single paragraph describing what needs to be investigated and why]
+
+**Investigation Focus:** [Specific area/component/pattern to investigate]
+**Trigger:** [What prompted this investigation - prior findings, issues, etc.]
+
+---
+
+## INVESTIGATION SCOPE
+
+### Primary Questions to Answer
+1. [Specific question #1]
+2. [Specific question #2]
+3. [Specific question #3]
+
+### Areas to Examine
+- **[Component/Area 1]:** [What to look for]
+- **[Component/Area 2]:** [What to look for]
+- **[Component/Area 3]:** [What to look for]
+
+### Mobile-First Investigation Requirements
+**MANDATORY for all UI-related investigations:**
+- [ ] **Mobile Viewport Testing** - Test on mobile device emulation
+- [ ] **Touch Interaction Verification** - Ensure touch events work correctly
+- [ ] **Mobile Browser Compatibility** - Test iOS Safari, Chrome Mobile, Android browsers
+- [ ] **Dynamic Viewport Handling** - Test with browser UI showing/hiding
+- [ ] **Mobile Performance Impact** - Check loading times and responsiveness
+- [ ] **Mobile-Specific Issues** - Look for desktop-only assumptions
+
+### Data to Collect
+- [ ] [Metric/Count #1]
+- [ ] [Metric/Count #2]
+- [ ] [Pattern instances]
+- [ ] [File lists]
+- [ ] Mobile-specific metrics (if UI investigation)
+
+---
+
+## INVESTIGATION METHODOLOGY
+
+### Phase 1: Discovery
+- [Specific discovery action]
+- [Search/scan parameters]
+- [Initial data gathering]
+
+### Phase 2: Analysis
+- [How to analyze findings]
+- [Patterns to identify]
+- [Correlations to make]
+
+### Phase 3: Documentation
+- [How to structure findings]
+- [Required evidence format]
+- [Conclusion requirements]
+
+---
+
+## DELIVERABLE REQUIREMENTS
+
+### Document Format
+**Filename:** `[TYPE]-INVESTIGATION-[TIMESTAMP].md`
+**Location:** `${PROJECT_REPORTS}/` (Project-specific Reports folder)
+
+### Required Sections
+1. **Executive Summary** - Key findings in 2-3 paragraphs
+2. **Investigation Results** - Detailed findings with evidence
+3. **Pattern Analysis** - Recurring issues identified
+4. **Root Cause Analysis** - Underlying causes discovered
+5. **Impact Assessment** - Scope and severity of findings
+6. **Mobile Compatibility Assessment** - Mobile-specific findings (if applicable)
+7. **Recommendations** - Specific next steps proposed
+8. **Supporting Evidence** - File paths, line numbers, counts
+
+### Metrics to Include
+- Total files/components examined
+- Issue counts by category
+- Pattern frequency data
+- Impact multipliers (1 cause : X symptoms)
+- Mobile compatibility scores (if applicable)
+
+---
+
+## ✅ AFTER COMPLETION
+
+### ⚠️ CRITICAL: Complete ALL Steps Below - NO EXCEPTIONS
+
+**Step 1: Create Completion Report** ✅
+   - [ ] Investigation deliverable created in `${PROJECT_REPORTS}/`
+   - [ ] Follow format: `[TYPE]-INVESTIGATION-[TIMESTAMP].md`
+   - [ ] JUNO audit report generated automatically (if applicable)
+   - [ ] All deliverables include required sections listed above
+
+**Step 2: 🚨 MOVE THIS WORK ORDER FILE 🚨** ✅
+   - [ ] **IMMEDIATELY** move this file from `trinity/work-orders/` to `trinity/sessions/`
+   - [ ] **THIS STEP IS MANDATORY** - Work orders left in trinity/work-orders/ are considered incomplete
+
+   **Execute this exact command:**
+   ```bash
+   mv trinity/work-orders/{{workOrderFilename}} trinity/sessions/
+   ```
+
+**Step 3: Verify File Locations** ✅
+   - [ ] This work order file NOW EXISTS in: `trinity/sessions/{{workOrderFilename}}`
+   - [ ] Completion report exists in: `${PROJECT_REPORTS}/[TYPE]-INVESTIGATION-[TIMESTAMP].md`
+   - [ ] This work order NO LONGER EXISTS in: `trinity/work-orders/`
+
+   **If any verification fails, the work order is NOT complete. Fix immediately.**
+
+**Step 4: Session Cleanup (when entire session complete):**
+   - [ ] When session is complete, run `/trinity-end`
+   - [ ] trinity-end will archive ALL files from `trinity/sessions/` and `${PROJECT_REPORTS}/`
+   - [ ] Next session starts with empty sessions/ and reports/ folders
+
+**Archive Destination (via trinity-end):**
+- Work order → `trinity/archive/work-orders/YYYY-MM-DD/`
+- Completion report → `trinity/archive/reports/YYYY-MM-DD/`
+- JUNO audit report → `trinity/archive/reports/YYYY-MM-DD/` (if applicable)
+- Session summary → `trinity/archive/sessions/YYYY-MM-DD/`
+
+---
+
+## SUCCESS CRITERIA
+
+The investigation is complete when:
+- [ ] All specified areas have been examined
+- [ ] All questions have been answered with evidence
+- [ ] Patterns have been identified and documented
+- [ ] Root causes have been determined where possible
+- [ ] Mobile compatibility verified (if UI investigation)
+- [ ] Clear recommendations have been provided
+- [ ] Investigation report submitted to project Reports folder
+
+---
+
+## ⚠️ CRITICAL RESTRICTIONS - GIT OPERATIONS FORBIDDEN
+
+**INVESTIGATIONS ARE READ-ONLY OPERATIONS:**
+ALL team members (CC, TRINITY, specialists) are PERMANENTLY FORBIDDEN from performing ANY git operations during investigations:
+
+- [ ] **git add** - FORBIDDEN - Only LUKA has permission
+- [ ] **git commit** - FORBIDDEN - Only LUKA has permission
+- [ ] **git push** - FORBIDDEN - Only LUKA has permission
+- [ ] **git pull** - FORBIDDEN - Only LUKA has permission
+- [ ] **git merge** - FORBIDDEN - Only LUKA has permission
+- [ ] **git checkout -b** - FORBIDDEN - Only LUKA has permission
+- [ ] **git branch** - FORBIDDEN - Only LUKA has permission
+- [ ] **git tag** - FORBIDDEN - Only LUKA has permission
+- [ ] **Any git operation that modifies repository state**
+
+**INVESTIGATION PROTOCOL:**
+1. Investigate and analyze files in current state
+2. Document all findings and recommendations
+3. Report investigation results to LUKA
+4. No file modifications during investigation phase
+5. If fixes are needed, LUKA will issue separate implementation work order
+
+---
+
+## CONTEXT FROM PREVIOUS WORK
+
+[Include relevant findings from prior work orders that inform this investigation]
+
+**Related Work Orders:** [#XXX, #XXX]
+**Prior Findings:** [Brief summary of relevant discoveries]
+
+---
+
+## PRIORITY LEVEL
+
+**Analysis Scope:** [COMPREHENSIVE/STANDARD/FOCUSED]
+**Completeness Required:** 100% - Full analysis must be completed
+**Reasoning:** [Why this priority]
+**Time Expectation:** [Estimated hours/scope]
+
+---
+
+## SPECIAL INSTRUCTIONS
+
+[Any specific tools, techniques, or constraints for this investigation]
+
+---
+
+**Remember:** Focus on discovering patterns and root causes, not just symptoms. Your investigation will guide our next strategic decisions. Investigations are read-only - no file modifications or git operations.
+
+*Trinity Method v2.0 - Investigation Work Order Template*
+*Project-Isolated Architecture with Dynamic Paths*

package/dist/templates/work-orders/PATTERN-TEMPLATE.md.template

@@ -0,0 +1,320 @@
+# ORCHESTRATOR WORK ORDER #XXX
+## Type: PATTERN
+## [Pattern Extraction/Implementation Title]
+
+---
+
+## AUTHORIZATION
+
+```
+TRINITY COUNCIL APPROVAL:
+☑ LUKA: APPROVED - [Pattern work justification]
+☑ TRINITY: APPROVED - [Pattern approach validation]
+☑ CC: PENDING - Awaiting your acknowledgment
+
+STATUS: APPROVED FOR EXECUTION
+```
+
+---
+
+## MISSION OBJECTIVE
+
+[Clear statement about pattern work - either extracting patterns from issues or implementing pattern-based fixes]
+
+**Pattern Goal:** [Extract patterns OR Apply pattern fixes]
+**Impact Potential:** [Estimated issues resolved by this pattern work]
+
+---
+
+## PATTERN SCOPE
+
+### For Pattern EXTRACTION:
+
+#### Source Material
+- Previous work orders: [#XXX, #XXX, #XXX]
+- Issue categories: [Types of issues to analyze]
+- Components: [Which parts of codebase]
+- Time range: [Period to analyze]
+
+#### Pattern Categories to Identify
+1. **Code Patterns**
+   - Repeated code structures
+   - Common anti-patterns
+   - Recurring bugs
+
+2. **Architecture Patterns**
+   - Design issues
+   - Coupling problems
+   - Scaling bottlenecks
+
+3. **Process Patterns**
+   - Development workflow issues
+   - Testing gaps
+   - Deployment problems
+
+4. **Mobile-Specific Patterns**
+   - Responsive design anti-patterns
+   - Touch interaction issues
+   - Viewport handling problems
+   - Mobile performance bottlenecks
+
+### For Pattern APPLICATION:
+
+#### Pattern to Apply
+**Pattern Name:** [Identified pattern]
+**Pattern Source:** [Where this pattern was identified]
+**Fix Template:**
+```language
+// Standard fix approach
+[Code template or approach]
+```
+
+#### Target Files
+```yaml
+High_Confidence_Matches:
+  - file: [path/file.ext]
+    instances: [X]
+    lines: [specific lines]
+
+  - file: [path/file.ext]
+    instances: [X]
+    lines: [specific lines]
+
+Probable_Matches:
+  - file: [path/file.ext]
+    instances: [X]
+    review_needed: true
+```
+
+---
+
+## PATTERN METHODOLOGY
+
+### For EXTRACTION:
+
+#### Step 1: Collection
+- [ ] Gather all relevant issues/reports
+- [ ] Categorize by component and type
+- [ ] Create frequency analysis
+- [ ] Include mobile-specific issue analysis
+
+#### Step 2: Analysis
+- [ ] Identify recurring elements
+- [ ] Group similar issues
+- [ ] Calculate occurrence rates
+- [ ] Analyze mobile vs desktop pattern differences
+
+#### Step 3: Pattern Definition
+- [ ] Document pattern characteristics
+- [ ] Create detection criteria
+- [ ] Develop fix templates
+- [ ] Include mobile-specific pattern templates
+
+### For APPLICATION:
+
+#### Step 1: Pattern Matching
+- [ ] Scan codebase for pattern instances
+- [ ] Verify matches against criteria
+- [ ] Prioritize by confidence level
+- [ ] Test patterns on mobile devices
+
+#### Step 2: Batch Implementation
+- [ ] Apply fixes to high-confidence matches
+- [ ] Review and fix probable matches
+- [ ] Test after each batch
+- [ ] Verify mobile compatibility after fixes
+
+#### Step 3: Validation
+- [ ] Verify all fixes applied correctly
+- [ ] Run tests for affected components
+- [ ] Document any exceptions
+- [ ] Confirm mobile compatibility maintained
+
+---
+
+## DELIVERABLE REQUIREMENTS
+
+### Document Format
+**Filename:** `PATTERN-[EXTRACTION/APPLICATION]-[TIMESTAMP].md`
+**Location:** `${PROJECT_REPORTS}/` (Project-specific Reports folder)
+
+### For Pattern EXTRACTION Report:
+1. **Executive Summary** - Patterns found and their impact
+2. **Pattern Catalog** - Detailed pattern descriptions
+3. **Frequency Analysis** - How often each pattern occurs
+4. **Mobile-Specific Patterns** - Mobile-unique pattern findings (if applicable)
+5. **Impact Multipliers** - Issues resolved per pattern fix
+6. **Fix Templates** - How to fix each pattern
+7. **Priority Matrix** - Which patterns to fix first
+8. **Implementation Plan** - How to apply fixes
+
+### For Pattern APPLICATION Report:
+1. **Executive Summary** - Fixes applied and results
+2. **Application Statistics** - Files changed, instances fixed
+3. **Confidence Levels** - High/medium/low confidence fixes
+4. **Mobile Compatibility Verification** - Mobile testing results (if applicable)
+5. **Exceptions** - Instances that couldn't be fixed
+6. **Test Results** - Validation of fixes
+7. **Remaining Work** - What still needs manual attention
+8. **Metrics** - Before/after comparison
+
+---
+
+## ✅ AFTER COMPLETION
+
+### ⚠️ CRITICAL: Complete ALL Steps Below - NO EXCEPTIONS
+
+**Step 1: Create Completion Report** ✅
+   - [ ] Pattern deliverable created in `${PROJECT_REPORTS}/`
+   - [ ] Follow format: `PATTERN-[NAME]-[TIMESTAMP].md`
+   - [ ] JUNO audit report generated automatically (if applicable)
+   - [ ] All deliverables include required sections listed above
+
+**Step 2: 🚨 MOVE THIS WORK ORDER FILE 🚨** ✅
+   - [ ] **IMMEDIATELY** move this file from `trinity/work-orders/` to `trinity/sessions/`
+   - [ ] **THIS STEP IS MANDATORY** - Work orders left in trinity/work-orders/ are considered incomplete
+
+   **Execute this exact command:**
+   ```bash
+   mv trinity/work-orders/{{workOrderFilename}} trinity/sessions/
+   ```
+
+**Step 3: Verify File Locations** ✅
+   - [ ] This work order file NOW EXISTS in: `trinity/sessions/{{workOrderFilename}}`
+   - [ ] Completion report exists in: `${PROJECT_REPORTS}/PATTERN-[NAME]-[TIMESTAMP].md`
+   - [ ] This work order NO LONGER EXISTS in: `trinity/work-orders/`
+
+   **If any verification fails, the work order is NOT complete. Fix immediately.**
+
+**Step 4: Session Cleanup (when entire session complete):**
+   - [ ] When session is complete, run `/trinity-end`
+   - [ ] trinity-end will archive ALL files from `trinity/sessions/` and `${PROJECT_REPORTS}/`
+   - [ ] Next session starts with empty sessions/ and reports/ folders
+
+**Archive Destination (via trinity-end):**
+- Work order → `trinity/archive/work-orders/YYYY-MM-DD/`
+- Completion report → `trinity/archive/reports/YYYY-MM-DD/`
+- JUNO audit report → `trinity/archive/reports/YYYY-MM-DD/` (if applicable)
+- Session summary → `trinity/archive/sessions/YYYY-MM-DD/`
+
+---
+
+## SUCCESS CRITERIA
+
+### For Pattern EXTRACTION:
+- [ ] Minimum 3 significant patterns identified
+- [ ] Impact multipliers calculated for each
+- [ ] Fix templates created and validated
+- [ ] Mobile patterns identified (if UI work)
+- [ ] Priority recommendations provided
+- [ ] Pattern library updated
+
+### For Pattern APPLICATION:
+- [ ] All high-confidence matches fixed
+- [ ] Probable matches reviewed and fixed
+- [ ] No regressions introduced
+- [ ] Mobile compatibility verified (if UI patterns)
+- [ ] Tests pass for affected code
+- [ ] Exceptions documented
+
+---
+
+## ⚠️ CRITICAL RESTRICTIONS - GIT OPERATIONS FORBIDDEN
+
+**PATTERN WORK MAY INVOLVE FILE MODIFICATIONS - BUT NO GIT OPERATIONS:**
+ALL team members (CC, TRINITY, specialists) are PERMANENTLY FORBIDDEN from performing ANY git operations:
+
+- [ ] **git add** - FORBIDDEN - Only LUKA has permission
+- [ ] **git commit** - FORBIDDEN - Only LUKA has permission
+- [ ] **git push** - FORBIDDEN - Only LUKA has permission
+- [ ] **git pull** - FORBIDDEN - Only LUKA has permission
+- [ ] **git merge** - FORBIDDEN - Only LUKA has permission
+- [ ] **git checkout -b** - FORBIDDEN - Only LUKA has permission
+- [ ] **git branch** - FORBIDDEN - Only LUKA has permission
+- [ ] **git tag** - FORBIDDEN - Only LUKA has permission
+- [ ] **git rebase** - FORBIDDEN - Only LUKA has permission
+- [ ] **git reset** - FORBIDDEN - Only LUKA has permission
+- [ ] **git revert** - FORBIDDEN - Only LUKA has permission
+- [ ] **git stash** - FORBIDDEN - Only LUKA has permission
+- [ ] **Any git operation that modifies repository state**
+
+**PATTERN WORK PROTOCOL:**
+1. Make all local file changes as specified
+2. Test thoroughly in local environment
+3. Report completion to LUKA with summary of changes
+4. LUKA will handle ALL git operations (add, commit, push, etc.)
+
+---
+
+## PATTERN QUALITY REQUIREMENTS
+
+### Valid Pattern Criteria
+A pattern must have:
+- Minimum frequency: [X occurrences]
+- Clear identification: [Unambiguous detection]
+- Consistent fix: [Same solution works for all instances]
+- Measurable impact: [Quantifiable improvement]
+
+### Pattern Documentation Standard
+Each pattern needs:
+```markdown
+## Pattern: [Name]
+**Frequency:** X instances across Y files
+**Detection:** [How to identify]
+**Root Cause:** [Why this occurs]
+**Fix Template:** [Standard solution]
+**Mobile Considerations:** [Mobile-specific variations if applicable]
+**Impact:** Resolves ~X issues
+**Risk:** [LOW/MEDIUM/HIGH]
+**Automation:** [Possible/Partial/Manual]
+```
+
+---
+
+## AUTOMATION POTENTIAL
+
+### For Future Automation
+Document patterns suitable for automation:
+- Detection rules that could be scripted
+- Fix approaches that could be automated
+- Testing that could verify fixes
+
+### Current Manual Requirements
+Note what must remain manual:
+- Context-dependent fixes
+- Architectural decisions
+- Complex refactoring
+
+---
+
+## CONTEXT FROM SESSION
+
+**Pattern Sources:** [Which investigations revealed patterns]
+**Previous Pattern Work:** [Build on Work Order #XXX if applicable]
+**Known Patterns:** [Already documented patterns to consider]
+
+---
+
+## PRIORITY & EFFICIENCY
+
+**Analysis Scope:** [COMPREHENSIVE/STANDARD/FOCUSED]
+**Completeness Required:** 100% - Full analysis must be completed
+**Efficiency Factor:** [1:X - one fix resolves X issues]
+**Time Investment:** [Estimated hours]
+**ROI:** [High/Medium/Low based on impact vs effort]
+
+---
+
+## SPECIAL CONSIDERATIONS
+
+- Edge cases: [Unusual instances to watch for]
+- False positives: [What might look like pattern but isn't]
+- Dependencies: [Order of fixes if patterns are related]
+- Mobile-specific considerations: [Mobile testing requirements]
+
+---
+
+**Remember:** Pattern work is about maximizing impact through systematic fixes. One pattern fix can resolve dozens of issues. Document patterns thoroughly for future reuse. Report all changes to LUKA for git operations.
+
+*Trinity Method v2.0 - Pattern Work Order Template*
+*Project-Isolated Architecture with Dynamic Paths*