trinity-method-sdk 2.0.9 → 2.2.0

package/dist/templates/{shared/claude-commands → .claude/commands/maintenance}/trinity-readme.md.template

@@ -1,10 +1,14 @@
 # Trinity README Management
 
-**Purpose:** Launch APO (Documentation Specialist) to ensure 100% CLAUDE.md → README.md coverage with accurate, up-to-date content.
+**Command:** `/execution:trinity-readme`
+**Purpose:** Launch APO (Documentation Specialist) to ensure 100% CLAUDE.md → README.md coverage with accurate content
+**Architecture:** APO 5-phase process (Discovery → Audit → Update → Create → Report)
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
 
 **Use Case:** Create missing READMEs, update existing READMEs with current codebase reality, fix inaccuracies.
 
-**Deliverable:** README audit report in `trinity/reports/README-AUDIT-{date}.md`
+**Deliverable:** README audit report in `.claude/trinity/reports/README-AUDIT-{date}.md`
 
 ---
 
@@ -75,7 +79,7 @@ The `/trinity-readme` command invokes APO (Documentation Specialist) to manage R
 
 Before finalizing any README, verify:
 
-- [ ] No trinity/ directory in file tree
+- [ ] No .claude/trinity/ directory in file tree
 - [ ] No .claude/ directory in file tree
 - [ ] No Trinity commands documented (unless project IS Trinity Method)
 - [ ] No references to Trinity agents (MON, ROR, KIL, etc.)
@@ -85,7 +89,7 @@ Before finalizing any README, verify:
 **Verification Command:**
 ```bash
 # Check for forbidden Trinity references in README
-grep -i "trinity/" README.md && echo "❌ VIOLATION: Documents trinity/ directory"
+grep -i ".claude/trinity/" README.md && echo "❌ VIOLATION: Documents .claude/trinity/ directory"
 grep -i "\.claude/" README.md && echo "❌ VIOLATION: Documents .claude/ directory"
 grep -i "/trinity-" README.md && echo "❌ VIOLATION: Documents Trinity commands"
 ```
@@ -329,7 +333,7 @@ filtered_directories = []
 
 for each directory in all_directories:
   # ALWAYS skip Trinity infrastructure
-  if directory.includes("trinity/") or directory.includes(".claude/"):
+  if directory.includes(".claude/trinity/") or directory.includes(".claude/"):
     echo "SKIP: $directory (Trinity infrastructure - never document)"
     continue
 
@@ -347,23 +351,23 @@ done
 
 **Trinity Detection Warning:**
 
-If you detect trinity/ or .claude/ directories during Phase 1:
+If you detect .claude/trinity/ or .claude/ directories during Phase 1:
 
-1. **Acknowledge detection:** "Detected Trinity Method infrastructure (trinity/ directory found)"
-2. **Skip documentation:** Do NOT include trinity/ in file tree or README content
+1. **Acknowledge detection:** "Detected Trinity Method infrastructure (.claude/trinity/ directory found)"
+2. **Skip documentation:** Do NOT include .claude/trinity/ in file tree or README content
 3. **Skip template:** Do NOT use Trinity-specific templates
 4. **Continue normally:** Process other directories (backend/, frontend/, etc.)
 
 **Example Output:**
 ```
-✓ Detected directories: backend/, frontend/, docs/, trinity/
+✓ Detected directories: backend/, frontend/, docs/, .claude/trinity/
 ✓ Filtering Trinity infrastructure and gitignored directories...
-  - trinity/ (Trinity infrastructure) → SKIP
+  - .claude/trinity/ (Trinity infrastructure) → SKIP
   - .claude/ (Trinity infrastructure) → SKIP
 ✓ Final directories to document: backend/, frontend/, docs/
 ```
 
-**Rule:** Trinity infrastructure (trinity/, .claude/) is ALWAYS excluded from user-facing READMEs, even if not gitignored.
+**Rule:** Trinity infrastructure (.claude/trinity/, .claude/) is ALWAYS excluded from user-facing READMEs, even if not gitignored.
 
 **Step 5: Report Complete Inventory (Using Validated Count)**
 
@@ -420,7 +424,7 @@ APO MUST answer ALL checklist items:
 
 6. **Project Structure Sanity:**
    - For project with backend/, frontend/, database/, do I expect nested CLAUDE.md files? ✅ YES | ❌ NO
-   - Do I see trinity/ or .claude/ directories? ⚠️ IGNORE (methodology infrastructure, not project code)
+   - Do I see .claude/trinity/ or .claude/ directories? ⚠️ IGNORE (methodology infrastructure, not project code)
    - If YES but none found: Re-run Glob with explicit paths
 
 **Self-Verification Action:**
@@ -434,7 +438,7 @@ IF any critical item = ❌ NO:
     - lib/**/CLAUDE.md
   Merge results and re-validate
 
-**Note:** Do NOT include trinity/ or .claude/ patterns - these are methodology infrastructure.
+**Note:** Do NOT include .claude/trinity/ or .claude/ patterns - these are methodology infrastructure.
 
 **Checklist Completion:** ✅ 6/6 items verified
 ```
@@ -621,7 +625,7 @@ Check all documentation links in root README.md work:
 
 If JUNO audit report exists, cross-reference root README.md claims:
 
-1. Read `trinity/reports/CODEBASE-AUDIT-{latest}.md`
+1. Read `.claude/trinity/reports/CODEBASE-AUDIT-{latest}.md`
 2. Extract actual counts (files, components, tests, etc.)
 3. Use audit findings as source of truth for root README.md
 4. Identify inaccuracies in root README.md for Phase 2.5 commitment
@@ -1835,7 +1839,7 @@ All directories with CLAUDE.md have README.md files.
 
 ### Phase 7: README Audit Report
 
-**APO Generates:** `trinity/reports/README-AUDIT-{date}.md`
+**APO Generates:** `.claude/trinity/reports/README-AUDIT-{date}.md`
 
 **CRITICAL: Report MUST document COMPLETED work, not future recommendations.**
 
@@ -2023,7 +2027,7 @@ OR
 ---
 
 **Report Generated:** {timestamp}
-**Report Location:** trinity/reports/README-AUDIT-{date}.md
+**Report Location:** .claude/trinity/reports/README-AUDIT-{date}.md
 ```
 
 ---
@@ -2086,7 +2090,7 @@ If Phase 6 validation shows coverage < 100%, status = ❌ FAILED even if Phase 4
 
 **After `/trinity-readme` completes, verify:**
 
-1. ✅ Check final report in `trinity/reports/README-AUDIT-{date}.md`
+1. ✅ Check final report in `.claude/trinity/reports/README-AUDIT-{date}.md`
 2. ✅ Verify coverage = 100% in report
 3. ✅ Verify all Phase 2.5 fixes show "✅ FIXED" status
 4. ✅ Verify all checkpoints show "✅ PASSED"
@@ -2098,6 +2102,3 @@ If Phase 6 validation shows coverage < 100%, status = ❌ FAILED even if Phase 4
 - Re-run command if failures detected
 
 ---
-
-** Trinity Version:** 2.0.9
-**Last Updated:** 2026-01-12

package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-decompose.md.template

@@ -1,9 +1,11 @@
----
-description: Decompose work into atomic tasks using EUS (Task Decomposer)
----
-
 # Trinity Task Decomposition - EUS
 
+**Command:** `/planning:trinity-decompose`
+**Purpose:** Decompose work into atomic tasks using EUS (Task Decomposer)
+**Architecture:** EUS task breakdown → Atomic task validation → TDD cycle planning
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 **Agent:** EUS (Task Decomposer)
 **Role:** Break work into atomic tasks following "1 task = 1 commit" rule
 

package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-design.md.template

@@ -1,9 +1,11 @@
----
-description: Create technical design using ROR (Design Architect)
----
-
 # Trinity Technical Design - ROR
 
+**Command:** `/planning:trinity-design`
+**Purpose:** Create technical design using ROR (Design Architect)
+**Architecture:** ROR design doc creation → ADR generation → Architecture definition
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 **Agent:** ROR (Design Architect)
 **Role:** Technical design, ADRs, and Design Doc creation
 

package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-plan.md.template

@@ -1,9 +1,11 @@
----
-description: Create implementation plan using TRA (Work Planner)
----
-
 # Trinity Work Planning - TRA
 
+**Command:** `/planning:trinity-plan`
+**Purpose:** Create implementation plan using TRA (Work Planner)
+**Architecture:** TRA implementation sequencing → BAS quality gates → Timeline estimation
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 **Agent:** TRA (Work Planner)
 **Role:** Implementation sequencing, BAS quality gates, and timeline estimation
 
@@ -153,7 +155,7 @@ Tasks must be sequential if:
 Sequential (WRONG):
 ```
 1. Create auth service → 2 hours
-2. Create auth middleware → 1 hour  
+2. Create auth middleware → 1 hour
 3. Add types → 30 min
 4. Write tests → 2 hours
 Total: 5.5 hours

package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-requirements.md.template

@@ -1,9 +1,11 @@
----
-description: Analyze requirements using MON (Requirements Analyst)
----
-
 # Trinity Requirements Analysis - MON
 
+**Command:** `/planning:trinity-requirements`
+**Purpose:** Analyze requirements using MON (Requirements Analyst)
+**Architecture:** MON requirements analysis → Scale determination → Acceptance criteria definition
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 **Agent:** MON (Requirements Analyst)
 **Role:** Scale determination, acceptance criteria, and requirements documentation
 

package/dist/templates/{shared/claude-commands → .claude/commands/session}/trinity-continue.md.template

@@ -1,5 +1,11 @@
----
-description: Resume work after interruption (ALY reviews state)
+# Trinity Continue
+
+**Command:** `/session:trinity-continue`
+**Purpose:** Resume work after interruption (ALY reviews state)
+**Architecture:** ALY session state review → Context restoration → Work resumption
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
 
 Resume Trinity Method workflow after interruption.
@@ -7,16 +13,16 @@ Resume Trinity Method workflow after interruption.
 **Context:** User experienced a crash or is returning to an existing session with incomplete work.
 
 **When to use:**
-- Work orders in trinity/work-orders/ haven't been completed
-- Reports in trinity/reports/ haven't been analyzed
-- Session files in trinity/sessions/ need review
+- Work orders in .claude/trinity/work-orders/ haven't been completed
+- Reports in .claude/trinity/reports/ haven't been analyzed
+- Session files in .claude/trinity/sessions/ need review
 - User needs to pick up where they left off
 
 **Process:**
 1. **ALY (CTO)** reviews all current work:
-   - Check trinity/sessions/ for active session files
-   - Review trinity/work-orders/ for incomplete work orders
-   - Analyze trinity/reports/ for unprocessed reports
+   - Check .claude/trinity/sessions/ for active session files
+   - Review .claude/trinity/work-orders/ for incomplete work orders
+   - Analyze .claude/trinity/reports/ for unprocessed reports
 
 2. **ALY provides session summary:**
    - Last known state of work
@@ -46,7 +52,7 @@ git log --oneline -5
 
 2. **Work Order Checking**:
 ```bash
-cat trinity/work-orders/WO-042-jwt-refresh-implementation.md
+cat .claude/trinity/work-orders/WO-042-jwt-refresh-implementation.md
 # Status: IN PROGRESS
 # **Last Updated**: 2 hours ago
 # Progress: Task 3/7
@@ -54,14 +60,14 @@ cat trinity/work-orders/WO-042-jwt-refresh-implementation.md
 
 3. **Session File Reading**:
 ```bash
-cat trinity/sessions/SESSION-2025-12-18-14-30.md
+cat .claude/trinity/sessions/SESSION-2025-12-18-14-30.md
 # Last entry: "Implementing middleware integration (50% complete)"
 # Interrupted: Context window limit reached
 ```
 
 4. **Knowledge Base Review**:
 ```bash
-cat trinity/knowledge-base/To-do.md
+cat .claude/trinity/knowledge-base/To-do.md
 # Shows 4 remaining tasks for JWT implementation
 ```
 
@@ -203,7 +209,7 @@ The previous session (3 days ago) was completed successfully:
 - Or create new work order with `/trinity-workorder`
 
 **Option 2: Review Backlog**
-- Check trinity/work-orders/ for pending work orders
+- Check .claude/trinity/work-orders/ for pending work orders
 - Prioritize and select next task
 - Begin implementation
 
@@ -400,13 +406,13 @@ git diff HEAD
 ### 2. Work Order Checking
 ```bash
 # List all work orders
-ls -lt trinity/work-orders/
+ls -lt .claude/trinity/work-orders/
 
 # Find IN PROGRESS work orders
-grep -r "Status: IN PROGRESS" trinity/work-orders/
+grep -r "Status: IN PROGRESS" .claude/trinity/work-orders/
 
 # Read most recent work order
-cat trinity/work-orders/WO-042-*.md
+cat .claude/trinity/work-orders/WO-042-*.md
 ```
 
 **Information Gathered**:
@@ -418,10 +424,10 @@ cat trinity/work-orders/WO-042-*.md
 ### 3. Session File Reading
 ```bash
 # Find most recent session file
-ls -lt trinity/sessions/ | head -1
+ls -lt .claude/trinity/sessions/ | head -1
 
 # Read session log
-cat trinity/sessions/SESSION-2025-12-18-14-30.md
+cat .claude/trinity/sessions/SESSION-2025-12-18-14-30.md
 ```
 
 **Information Gathered**:
@@ -433,13 +439,13 @@ cat trinity/sessions/SESSION-2025-12-18-14-30.md
 ### 4. Knowledge Base Review
 ```bash
 # Check active tasks
-cat trinity/knowledge-base/To-do.md
+cat .claude/trinity/knowledge-base/To-do.md
 
 # Review known issues
-cat trinity/knowledge-base/ISSUES.md
+cat .claude/trinity/knowledge-base/ISSUES.md
 
 # Check recent decisions
-tail -20 trinity/knowledge-base/ARCHITECTURE.md
+tail -20 .claude/trinity/knowledge-base/ARCHITECTURE.md
 ```
 
 **Information Gathered**:
@@ -489,7 +495,7 @@ git log origin/main..HEAD --oneline
 - Terminal history
 - In-memory variables
 
-**Persisted In**: `trinity/sessions/SESSION-{timestamp}.md`
+**Persisted In**: `.claude/trinity/sessions/SESSION-{timestamp}.md`
 
 ### Work Order State
 **What**: Progress on specific task
@@ -497,7 +503,7 @@ git log origin/main..HEAD --oneline
 - Current phase
 - Blockers/issues
 
-**Persisted In**: `trinity/work-orders/WO-XXX-{title}.md`
+**Persisted In**: `.claude/trinity/work-orders/WO-XXX-{title}.md`
 
 ### Key Difference
 
@@ -536,12 +542,12 @@ git log origin/main..HEAD --oneline
 **/trinity-continue**:
 - Analyzes current state (git, work orders, sessions)
 - Provides recovery options
-- Resumes with AJ MAESTRO or AJ CC
+- Resumes with AJ MAESTRO
 
 **/trinity-end**:
 - Creates session summary
 - Updates knowledge base
-- Archives work to trinity/archive/
+- Archives work to .claude/trinity/archive/
 - Clears session state
 
 **Don't Use /trinity-end** if you're just taking a break - context will be lost!