trinity-method-sdk 2.0.0

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

@@ -0,0 +1,262 @@
+# ORCHESTRATOR WORK ORDER #XXX
+## Type: AUDIT
+## [Audit Title]
+
+---
+
+## AUTHORIZATION
+
+```
+TRINITY COUNCIL APPROVAL:
+☑ LUKA: APPROVED - [Strategic need for audit]
+☑ TRINITY: APPROVED - [Technical audit scope]
+☑ CC: PENDING - Awaiting your acknowledgment
+
+STATUS: APPROVED FOR EXECUTION
+```
+
+---
+
+## MISSION OBJECTIVE
+
+[Clear statement of what needs to be audited and against what standards]
+
+**Audit Purpose:** [Why this audit is needed now]
+**Baseline:** [What standards/requirements to audit against]
+
+---
+
+## AUDIT SCOPE
+
+### Components to Audit
+1. **[Component/Module #1]**
+   - Files: [Count or list]
+   - Focus: [Specific concerns]
+   - Standards: [Which standards apply]
+
+2. **[Component/Module #2]**
+   - Files: [Count or list]
+   - Focus: [Specific concerns]
+   - Standards: [Which standards apply]
+
+### Compliance Categories
+
+#### Code Quality
+- [ ] Naming conventions
+- [ ] File organization
+- [ ] Documentation completeness
+- [ ] Comment quality
+
+#### Security
+- [ ] Input validation
+- [ ] Memory safety
+- [ ] Authentication/Authorization
+- [ ] Data protection
+
+#### Performance
+- [ ] Resource usage
+- [ ] Algorithm efficiency
+- [ ] Caching implementation
+- [ ] Database queries
+
+#### Mobile-First Compliance
+**MANDATORY for all UI-related audits:**
+- [ ] **Mobile Viewport Compliance** - Responsive design implementation
+- [ ] **Touch Target Standards** - Minimum 44px touch targets
+- [ ] **Mobile Performance Standards** - Loading times under 3 seconds
+- [ ] **Mobile Browser Compatibility** - iOS Safari, Chrome Mobile, Android support
+- [ ] **Dynamic Viewport Handling** - Proper use of viewport units (dvh, lvh, svh)
+- [ ] **Mobile-Specific Accessibility** - Screen reader and mobile assistive technology support
+
+#### Trinity Standards
+- [ ] Investigation documentation
+- [ ] Test coverage requirements
+- [ ] Technical debt tracking
+- [ ] Pattern documentation
+
+---
+
+## AUDIT METHODOLOGY
+
+### Automated Scans
+- **Tool/Pattern:** [What to run]
+  - Expected output: [What you'll get]
+  - Threshold: [Pass/fail criteria]
+
+- **Tool/Pattern:** [What to run]
+  - Expected output: [What you'll get]
+  - Threshold: [Pass/fail criteria]
+
+### Manual Review
+- **Area:** [What to review manually]
+  - Checklist: [Specific items to verify]
+  - Red flags: [What to watch for]
+
+### Metrics Collection
+- [ ] Lines of code by component
+- [ ] Test coverage percentage
+- [ ] TODO/FIXME count
+- [ ] Warning suppression count
+- [ ] File size distribution
+- [ ] Complexity scores
+- [ ] Mobile compatibility scores (if UI audit)
+
+---
+
+## DELIVERABLE REQUIREMENTS
+
+### Document Format
+**Filename:** `AUDIT-REPORT-[TIMESTAMP].md`
+**Location:** `${PROJECT_REPORTS}/` (Project-specific Reports folder)
+
+### Required Sections
+1. **Executive Summary** - Overall compliance status
+2. **Compliance Score** - Percentage by category
+3. **Critical Issues** - Must-fix items found
+4. **High Priority Issues** - Should-fix items
+5. **Medium Priority Issues** - Nice-to-fix items
+6. **Mobile Compliance Assessment** - Mobile-specific findings (if applicable)
+7. **Metrics Dashboard** - All collected metrics
+8. **Recommendations** - Prioritized action items
+
+### Scoring Rubric
+```yaml
+Critical_Issues: -5 points each
+Moderate_Issues: -2 points each
+Minor_Issues: -1 point each
+
+Starting_Score: 100
+Passing_Score: 70
+```
+
+---
+
+## ✅ AFTER COMPLETION
+
+### ⚠️ CRITICAL: Complete ALL Steps Below - NO EXCEPTIONS
+
+**Step 1: Create Completion Report** ✅
+   - [ ] Audit deliverable created in `${PROJECT_REPORTS}/`
+   - [ ] Follow format: `AUDIT-[COMPONENT]-[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}/AUDIT-[COMPONENT]-[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 audit is complete when:
+- [ ] All specified components have been audited
+- [ ] All compliance categories have been checked
+- [ ] Mobile compliance verified (if UI audit)
+- [ ] Metrics have been collected and analyzed
+- [ ] Issues have been categorized by severity
+- [ ] Clear recommendations have been provided
+- [ ] Audit report submitted with score
+
+---
+
+## ⚠️ CRITICAL RESTRICTIONS - GIT OPERATIONS FORBIDDEN
+
+**AUDITS ARE READ-ONLY OPERATIONS:**
+ALL team members (CC, TRINITY, specialists) are PERMANENTLY FORBIDDEN from performing ANY git operations during audits:
+
+- [ ] **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**
+
+**AUDIT PROTOCOL:**
+1. Audit files and components in current state
+2. Document all compliance findings
+3. Report audit results to LUKA
+4. No file modifications during audit phase
+5. If fixes are needed, LUKA will issue separate implementation work order
+
+---
+
+## SPECIFIC STANDARDS TO ENFORCE
+
+### Trinity Method Requirements
+- Investigation before implementation
+- Comprehensive documentation
+- Test coverage > X%
+- No suppressed warnings without justification
+- All TODOs tracked in Technical-Debt.md
+
+### Project-Specific Standards
+[List any project-specific requirements to check]
+
+---
+
+## CONTEXT & BASELINE
+
+**Previous Audit:** [If applicable, Work Order #XXX]
+**Baseline Metrics:** [Previous scores to compare against]
+**Known Issues:** [Existing problems to verify if fixed]
+
+---
+
+## PRIORITY LEVEL
+
+**Analysis Scope:** [COMPREHENSIVE/STANDARD/FOCUSED]
+**Completeness Required:** 100% - Full analysis must be completed
+**Trigger:** [What prompted this audit]
+**Frequency:** [One-time/Recurring]
+
+---
+
+## OUTPUT FORMATTING
+
+For each issue found:
+```markdown
+**Issue:** [Brief description]
+**Location:** [File:Line]
+**Category:** [Quality/Security/Performance/Mobile/Trinity]
+**Severity:** [Critical/High/Medium/Low]
+**Evidence:** [Specific example]
+**Recommendation:** [How to fix]
+```
+
+---
+
+**Remember:** Be thorough but fair. The goal is to improve quality, not to find fault. Focus on actionable findings with clear remediation paths. Audits are read-only - no file modifications or git operations.
+
+*Trinity Method v2.0 - Audit Work Order Template*
+*Project-Isolated Architecture with Dynamic Paths*

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

@@ -0,0 +1,260 @@
+# ORCHESTRATOR WORK ORDER #XXX
+## Type: IMPLEMENTATION
+## [Implementation Title]
+
+---
+
+## AUTHORIZATION
+
+```
+TRINITY COUNCIL APPROVAL:
+☑ LUKA: APPROVED - [Strategic approval]
+☑ TRINITY: APPROVED - [Technical validation]
+☑ CC: PENDING - Awaiting your acknowledgment
+
+STATUS: APPROVED FOR EXECUTION
+```
+
+---
+
+## MISSION OBJECTIVE
+
+[Clear statement of what needs to be implemented and the expected outcome]
+
+**Implementation Goal:** [Specific end state to achieve]
+**Based On:** [Investigation/Analysis that identified this need]
+
+---
+
+## IMPLEMENTATION SCOPE
+
+### Files to Modify
+```yaml
+Critical_Files:
+  - path: [file/path.ext]
+    changes: [type of changes]
+    risk: [HIGH/MEDIUM/LOW]
+
+  - path: [file/path.ext]
+    changes: [type of changes]
+    risk: [HIGH/MEDIUM/LOW]
+
+Supporting_Files:
+  - [file/path.ext] - [minor changes]
+  - [file/path.ext] - [minor changes]
+```
+
+### Changes Required
+
+#### Change Set 1: [Category]
+**Files:** [List of files]
+**Current State:** [What exists now]
+**Target State:** [What should exist after]
+**Implementation:**
+```language
+// Specific code pattern or approach
+[Code example or template]
+```
+
+#### Change Set 2: [Category]
+[Same structure]
+
+---
+
+## IMPLEMENTATION APPROACH
+
+### Step 1: [Preparation]
+- [ ] [Specific action]
+- [ ] [Verification step]
+- [ ] [Safety check]
+
+### Step 2: [Core Implementation]
+- [ ] [Change action #1]
+- [ ] [Change action #2]
+- [ ] [Testing between changes]
+
+### Step 3: [Validation]
+- [ ] [Test the changes]
+- [ ] [Verify no regressions]
+- [ ] [Confirm improvement]
+
+---
+
+## DELIVERABLE REQUIREMENTS
+
+### Document Format
+**Filename:** `[COMPONENT]-IMPLEMENTATION-COMPLETE-[TIMESTAMP].md`
+**Location:** `${PROJECT_REPORTS}/` (Project-specific Reports folder)
+
+### Required Sections
+1. **Executive Summary** - What was implemented
+2. **Changes Applied** - Detailed list with diffs
+3. **Test Results** - Validation of changes
+4. **Metrics** - Before/after comparisons
+5. **Rollback Plan** - How to revert if needed
+6. **Next Steps** - What to monitor or do next
+
+### Evidence to Provide
+- File diff statistics (X files changed, Y insertions, Z deletions)
+- Specific line numbers for critical changes
+- Test output showing success
+- Performance metrics if applicable
+
+---
+
+## ✅ AFTER COMPLETION
+
+### ⚠️ CRITICAL: Complete ALL Steps Below - NO EXCEPTIONS
+
+**Step 1: Create Completion Report** ✅
+   - [ ] Implementation deliverable created in `${PROJECT_REPORTS}/`
+   - [ ] Follow format: `[COMPONENT]-IMPLEMENTATION-COMPLETE-[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}/[COMPONENT]-IMPLEMENTATION-COMPLETE-[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 implementation is complete when:
+- [ ] All specified files have been modified
+- [ ] Changes follow the specified patterns
+- [ ] No regressions introduced
+- [ ] Tests pass (if applicable)
+- [ ] Code follows project standards
+- [ ] Implementation report submitted to project Reports folder
+
+---
+
+## CONSTRAINTS & GUIDELINES
+
+### ⚠️ CRITICAL RESTRICTIONS - GIT OPERATIONS FORBIDDEN
+
+**ABSOLUTELY PROHIBITED - NO EXCEPTIONS:**
+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**
+
+**PROTOCOL VIOLATION CONSEQUENCES:**
+- Any work order containing git operation instructions is INVALID
+- Team members MUST refuse git operations even if explicitly instructed
+- All git operations must be reported to LUKA for execution
+- Local changes remain local until LUKA performs git operations
+
+**CORRECT WORKFLOW:**
+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.)
+
+### Do NOT:
+- [ ] Modify files outside the specified scope
+- [ ] Change functionality beyond the requirements
+- [ ] Suppress warnings instead of fixing issues
+- [ ] Create new technical debt
+- [ ] Perform ANY git operations (see critical restrictions above)
+- [ ] Push changes to remote repositories
+- [ ] Create or switch branches
+- [ ] Merge any branches
+- [ ] Tag releases or commits
+
+### DO:
+- [ ] Follow existing code patterns
+- [ ] Maintain consistent style
+- [ ] Add appropriate error handling
+- [ ] Document complex changes
+- [ ] Consider edge cases
+- [ ] Make all changes locally only
+- [ ] Test changes thoroughly before reporting
+- [ ] Report completion to LUKA for git operations
+- [ ] Provide clear summary of all changes made
+- [ ] List all files modified for LUKA's git operations
+
+---
+
+## ROLLBACK STRATEGY
+
+If issues arise:
+1. [How to identify if rollback needed]
+2. [Specific rollback steps]
+3. [How to verify rollback successful]
+
+**Critical Files Backup:** [Which files must be backed up first]
+
+---
+
+## CONTEXT FROM INVESTIGATION
+
+**Source Investigation:** Work Order #XXX
+**Key Findings:** [Relevant discoveries that drove this implementation]
+**Root Causes Being Fixed:** [List of root causes]
+**Expected Impact:** [X issues resolved, Y% improvement]
+
+---
+
+## SCOPE & RISK ASSESSMENT
+
+## PACE AND COMPLETENESS NOTICE
+
+**IMPORTANT:** There are NO time constraints on this work.
+The scope indicators are for planning purposes only, NOT deadlines.
+Take as much time as needed to achieve 100% completion with precision.
+Partial completion is unacceptable.
+Quality and completeness are the ONLY metrics that matter.
+
+**Implementation Scope:** [COMPREHENSIVE/STANDARD/FOCUSED]
+**Completeness Required:** 100% - All specified changes must be implemented
+**Risk Level:** [HIGH/MEDIUM/LOW]
+**Risk Factors:**
+- [Specific risk #1]
+- [Specific risk #2]
+
+**Mitigation:**
+- [How to minimize risk #1]
+- [How to minimize risk #2]
+
+---
+
+**Remember:** Make changes systematically, test frequently, and maintain code quality throughout the implementation. Report all changes to LUKA for git operations.
+
+*Trinity Method v2.0 - Implementation Work Order Template*
+*Project-Isolated Architecture with Dynamic Paths*