trinity-method-sdk 2.0.9 → 2.2.0

package/dist/templates/{shared/claude-commands → .claude/commands/execution}/trinity-orchestrate.md.template

@@ -1,10 +1,10 @@
----
-description: Primary command for executing tasks with AJ MAESTRO orchestration
----
-
 # Trinity Orchestration
 
-**Purpose:** Primary command for executing tasks during development sessions. AJ MAESTRO coordinates the 19-agent team to complete work, with automatic JUNO verification.
+**Command:** `/execution:trinity-orchestrate`
+**Purpose:** Primary command for executing tasks during development sessions with AJ MAESTRO orchestration
+**Architecture:** ALY (CTO) → MON → ROR → TRA → EUS → KIL cycles → BAS gates → JUNO verification
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
 
 **Use throughout your session:** This command is used repeatedly as you work through tasks.
 
@@ -44,18 +44,18 @@ description: Primary command for executing tasks with AJ MAESTRO orchestration
 
 **Workflow:**
 1. Create work order: `/trinity-workorder`
-2. Work order saved to: `trinity/work-orders/WO-XXX-{task-name}.md`
+2. Work order saved to: `.claude/trinity/work-orders/WO-XXX-{task-name}.md`
 3. Execute: `/trinity-orchestrate @WO-042-jwt-refresh.md`
 4. **AJ MAESTRO** selects agents and orchestrates execution
 5. **TWO DELIVERABLES CREATED:**
    a. **Implementation Report** (from work order template):
-      `trinity/reports/[COMPONENT]-IMPLEMENTATION-COMPLETE-{timestamp}.md`
+      `.claude/trinity/reports/[COMPONENT]-IMPLEMENTATION-COMPLETE-{timestamp}.md`
    b. **JUNO Audit Report** (automatic verification):
-      `trinity/reports/AUDIT-WO-042-{date}.md`
-6. 🚨 **CRITICAL: MOVE completed work order** from `trinity/work-orders/` to `trinity/sessions/`
-   - **MANDATORY STEP** - Execute: `mv trinity/work-orders/WO-XXX-*.md trinity/sessions/`
-   - **Verify work order NO LONGER exists in trinity/work-orders/**
-7. **Reports remain** in `trinity/reports/` until session end
+      `.claude/trinity/reports/AUDIT-WO-042-{date}.md`
+6. 🚨 **CRITICAL: MOVE completed work order** from `.claude/trinity/work-orders/` to `.claude/trinity/sessions/`
+   - **MANDATORY STEP** - Execute: `mv .claude/trinity/work-orders/WO-XXX-*.md .claude/trinity/sessions/`
+   - **Verify work order NO LONGER exists in .claude/trinity/work-orders/**
+7. **Reports remain** in `.claude/trinity/reports/` until session end
 8. **Run `/trinity-end`** when session complete to archive all session files
 
 **Example:**
@@ -80,17 +80,17 @@ description: Primary command for executing tasks with AJ MAESTRO orchestration
 
 **Workflow:**
 1. Create investigation: `/trinity-create-investigation`
-2. Investigation saved to: `trinity/investigations/INV-XXX-{title}.md`
+2. Investigation saved to: `.claude/trinity/investigations/INV-XXX-{title}.md`
 3. Execute: `/trinity-orchestrate @INV-015-performance-analysis.md`
 4. **AJ MAESTRO** coordinates READ-ONLY investigation
 5. Findings documented (no code changes)
 6. **Investigation Report Created:**
-   `trinity/reports/INV-015-findings-{date}.md`
+   `.claude/trinity/reports/INV-015-findings-{date}.md`
    (See investigation template for required sections)
-7. 🚨 **CRITICAL: MOVE completed investigation** from `trinity/investigations/` to `trinity/sessions/`
-   - **MANDATORY STEP** - Execute: `mv trinity/investigations/INV-XXX-*.md trinity/sessions/`
-   - **Verify investigation NO LONGER exists in trinity/investigations/**
-8. **Report remains** in `trinity/reports/` until session end
+7. 🚨 **CRITICAL: MOVE completed investigation** from `.claude/trinity/investigations/` to `.claude/trinity/sessions/`
+   - **MANDATORY STEP** - Execute: `mv .claude/trinity/investigations/INV-XXX-*.md .claude/trinity/sessions/`
+   - **Verify investigation NO LONGER exists in .claude/trinity/investigations/**
+8. **Report remains** in `.claude/trinity/reports/` until session end
 9. **Run `/trinity-end`** when session complete to archive all session files
 
 ⚠️ **CRITICAL:** Investigations are READ-ONLY operations. No code changes during investigation phase. Implementation happens separately after investigation is complete.
@@ -244,7 +244,7 @@ When you invoke `/trinity-orchestrate`, here's what happens:
    - Complexity within limits
 
 **JUNO's Audit Report:**
-- Saved to: `trinity/reports/AUDIT-{task-id}-{date}.md`
+- Saved to: `.claude/trinity/reports/AUDIT-{task-id}-{date}.md`
 - Pass/Fail status for each criterion
 - Overall assessment (APPROVED / REQUIRES FIXES)
 - Recommendations for improvements
@@ -337,23 +337,23 @@ Please address WO-043 before marking WO-042 complete.
 **Step 1: Verify Deliverables Created** ✅
 
 **Work Orders:**
-- [ ] Implementation report in `trinity/reports/[COMPONENT]-IMPLEMENTATION-COMPLETE-{timestamp}.md`
-- [ ] JUNO audit report in `trinity/reports/AUDIT-WO-XXX-{date}.md` (if applicable)
+- [ ] Implementation report in `.claude/trinity/reports/[COMPONENT]-IMPLEMENTATION-COMPLETE-{timestamp}.md`
+- [ ] JUNO audit report in `.claude/trinity/reports/AUDIT-WO-XXX-{date}.md` (if applicable)
 
 **Investigations:**
-- [ ] Findings report in `trinity/reports/INV-XXX-findings-{date}.md`
+- [ ] Findings report in `.claude/trinity/reports/INV-XXX-findings-{date}.md`
 - [ ] All required sections completed (summary, findings, root cause, recommendations, evidence)
 
 **Step 2: 🚨 MOVE THE COMPLETED FILE TO SESSIONS/ 🚨** ✅
 
-**THIS STEP IS MANDATORY - Work orders left in trinity/work-orders/ are considered INCOMPLETE.**
+**THIS STEP IS MANDATORY - Work orders left in .claude/trinity/work-orders/ are considered INCOMPLETE.**
 
 ```bash
 # Work Order Example - EXECUTE THIS IMMEDIATELY AFTER CREATING DELIVERABLE
-mv trinity/work-orders/WO-042-jwt-refresh.md trinity/sessions/
+mv .claude/trinity/work-orders/WO-042-jwt-refresh.md .claude/trinity/sessions/
 
 # Investigation Example - EXECUTE THIS IMMEDIATELY AFTER CREATING FINDINGS REPORT
-mv trinity/investigations/INV-015-performance-analysis.md trinity/sessions/
+mv .claude/trinity/investigations/INV-015-performance-analysis.md .claude/trinity/sessions/
 ```
 
 **Step 3: Verify File Locations** ✅
@@ -361,22 +361,22 @@ mv trinity/investigations/INV-015-performance-analysis.md trinity/sessions/
 **CRITICAL VERIFICATION - If this fails, the task is NOT complete:**
 
 **For Work Orders:**
-- [ ] Work order file NOW EXISTS in: `trinity/sessions/WO-XXX-*.md`
-- [ ] Deliverable report exists in: `trinity/reports/[COMPONENT]-IMPLEMENTATION-COMPLETE-*.md`
-- [ ] Work order file NO LONGER EXISTS in: `trinity/work-orders/`
+- [ ] Work order file NOW EXISTS in: `.claude/trinity/sessions/WO-XXX-*.md`
+- [ ] Deliverable report exists in: `.claude/trinity/reports/[COMPONENT]-IMPLEMENTATION-COMPLETE-*.md`
+- [ ] Work order file NO LONGER EXISTS in: `.claude/trinity/work-orders/`
 
 **For Investigations:**
-- [ ] Investigation file NOW EXISTS in: `trinity/sessions/INV-XXX-*.md`
-- [ ] Findings report exists in: `trinity/reports/INV-XXX-findings-*.md`
-- [ ] Investigation file NO LONGER EXISTS in: `trinity/investigations/`
+- [ ] Investigation file NOW EXISTS in: `.claude/trinity/sessions/INV-XXX-*.md`
+- [ ] Findings report exists in: `.claude/trinity/reports/INV-XXX-findings-*.md`
+- [ ] Investigation file NO LONGER EXISTS in: `.claude/trinity/investigations/`
 
 **If any verification fails, STOP and fix immediately before proceeding.**
 
 **Step 4: Continue Working or End Session**
 
 **If continuing work in same session:**
-- Reports remain in `trinity/reports/` (available for reference)
-- Completed WOs/INVs in `trinity/sessions/` (out of active work queue)
+- Reports remain in `.claude/trinity/reports/` (available for reference)
+- Completed WOs/INVs in `.claude/trinity/sessions/` (out of active work queue)
 - Proceed with next task
 
 **If session is complete:**
@@ -385,12 +385,12 @@ mv trinity/investigations/INV-015-performance-analysis.md trinity/sessions/
 ```
 
 This will:
-- Archive ALL files from `trinity/sessions/` → `trinity/archive/sessions/YYYY-MM-DD/`
-- Archive ALL files from `trinity/reports/` → `trinity/archive/reports/YYYY-MM-DD/`
-- Archive completed work orders → `trinity/archive/work-orders/YYYY-MM-DD/`
-- Archive completed investigations → `trinity/archive/investigations/YYYY-MM-DD/`
-- Create session summary in `trinity/archive/sessions/YYYY-MM-DD/`
-- **Result:** Clean `trinity/sessions/` and `trinity/reports/` folders for next session
+- Archive ALL files from `.claude/trinity/sessions/` → `.claude/trinity/archive/sessions/YYYY-MM-DD/`
+- Archive ALL files from `.claude/trinity/reports/` → `.claude/trinity/archive/reports/YYYY-MM-DD/`
+- Archive completed work orders → `.claude/trinity/archive/work-orders/YYYY-MM-DD/`
+- Archive completed investigations → `.claude/trinity/archive/investigations/YYYY-MM-DD/`
+- Create session summary in `.claude/trinity/archive/sessions/YYYY-MM-DD/`
+- **Result:** Clean `.claude/trinity/sessions/` and `.claude/trinity/reports/` folders for next session
 
 ---
 
@@ -398,7 +398,7 @@ This will:
 
 **Active Session:**
 ```
-trinity/
+.claude/trinity/
 ├── work-orders/          # Active work orders (not yet completed)
 ├── investigations/       # Active investigations (not yet completed)
 ├── sessions/            # Completed WOs/INVs (awaiting archival)
@@ -407,7 +407,7 @@ trinity/
 
 **After /trinity-end:**
 ```
-trinity/
+.claude/trinity/
 ├── work-orders/          # EMPTY (all active work complete or in-progress only)
 ├── investigations/       # EMPTY (all active investigations complete or in-progress only)
 ├── sessions/            # EMPTY (all archived)
@@ -433,14 +433,14 @@ trinity/
 **How Trinity Handles Context Loss:**
 
 1. **Documentation Persists:**
-   - Work orders: `trinity/work-orders/WO-XXX.md`
-   - Investigations: `trinity/investigations/INV-XXX.md`
-   - JUNO reports: `trinity/reports/AUDIT-*.md`
-   - Knowledge base: `trinity/knowledge-base/*.md`
+   - Work orders: `.claude/trinity/work-orders/WO-XXX.md`
+   - Investigations: `.claude/trinity/investigations/INV-XXX.md`
+   - JUNO reports: `.claude/trinity/reports/AUDIT-*.md`
+   - Knowledge base: `.claude/trinity/knowledge-base/*.md`
 
 2. **When Context Window Is Exceeded:**
    - Current work is automatically documented
-   - Session state saved to `trinity/sessions/SESSION-{timestamp}.md`
+   - Session state saved to `.claude/trinity/sessions/SESSION-{timestamp}.md`
    - Use `/trinity-continue` to resume
    - AJ MAESTRO reads files to understand current state
    - JUNO reports show what's been completed
@@ -678,7 +678,7 @@ JUNO: Performing comprehensive audit...
 **Overall Assessment: APPROVED ✅**
 
 Audit report saved to:
-`trinity/reports/AUDIT-WO-042-2025-12-19.md`
+`.claude/trinity/reports/AUDIT-WO-042-2025-12-19.md`
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
@@ -837,7 +837,7 @@ JUNO: Auditing investigation completeness...
 ✅ Recommendations: 3 actionable items with effort estimates
 
 **Findings Report:**
-`trinity/reports/INV-015-findings-2025-12-19.md`
+`.claude/trinity/reports/INV-015-findings-2025-12-19.md`
 
 **Follow-Up Work Orders Created:**
 - WO-043-database-index-optimization (HIGH priority, 2 hours)

package/dist/templates/{shared/claude-commands → .claude/commands/infrastructure}/trinity-init.md.template

@@ -1,28 +1,29 @@
+# Trinity Initialization
+
+**Command:** `/infrastructure:trinity-init`
+**Purpose:** Complete Trinity Method integration with comprehensive setup and quality validation
+**Architecture:** TAN structure validation → ZEN knowledge base → INO context → EIN CI/CD → JUNO audit
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
-description: Complete Trinity integration with TAN → ZEN → INO → EIN → JUNO workflow
----
+
 # Quick Start - TL;DR
 
 **Install Trinity in 3 steps**:
 
-1. **Run Init**: `/trinity-init`
-2. **Wait**: ~30 seconds (deploys 19 agents + knowledge base)
-3. **Verify**: `/trinity-verify` (confirm 100% deployment)
+1. **Run Init**: `/infrastructure:trinity-init`
+2. **Wait**: ~30 seconds (deploys 18 agents + knowledge base)
+3. **Verify**: `/utility:trinity-verify` (confirm 100% deployment)
 
 **What You Get**:
-- 19 specialized agents in `.claude/agents/`
+- 18 specialized agents in `.claude/agents/`
 - 20 slash commands in `.claude/commands/` (6 categories)
-- Knowledge base in `trinity/knowledge-base/`
-- Work order system in `trinity/work-orders/`
-- Documentation templates in `trinity/templates/documentation/`
-
-**Next Steps**: Run `/trinity-start` to begin your first workflow
+- Knowledge base in `.claude/trinity/knowledge-base/`
+- Work order system in `.claude/trinity/work-orders/`
+- Documentation templates in `.claude/trinity/templates/documentation/`
 
----
-
-# Trinity Initialization
-
-**Purpose:** Complete Trinity Method integration with comprehensive setup and quality validation.
+**Next Steps**: Run `/session:trinity-start` to begin your first workflow
 
 ## Overview
 
@@ -35,7 +36,7 @@ Trinity initialization populates the Trinity Method infrastructure with:
 
 **Context:** User has run `trinity deploy` and basic Trinity structure exists. Deployment team will now populate and verify all Trinity documents.
 
-**IMPORTANT:** All folders and basic files already exist from deployment. DO NOT attempt to create folders that already exist (trinity/, .claude/, etc.). Focus on POPULATING and VERIFYING content.
+**IMPORTANT:** All folders and basic files already exist from deployment. DO NOT attempt to create folders that already exist (.claude/trinity/, .claude/, etc.). Focus on POPULATING and VERIFYING content.
 
 ## Trinity Method Capabilities
 
@@ -267,7 +268,7 @@ Trinity creates additional CLAUDE.md files when it detects:
 
 ### Configuration Override
 
-You can manually specify CLAUDE.md locations in `trinity/config.json`:
+You can manually specify CLAUDE.md locations in `.claude/trinity/config.json`:
 
 ```json
 {
@@ -372,16 +373,16 @@ Suggestions:
 
 ### Phase 2: ZEN (Knowledge Base Specialist) - Populate Trinity documentation
 - Analyze existing codebase
-- POPULATE trinity/knowledge-base/ARCHITECTURE.md with detailed architecture analysis
-- POPULATE trinity/knowledge-base/ISSUES.md with discovered issues
-- POPULATE trinity/knowledge-base/To-do.md with identified tasks
-- POPULATE trinity/knowledge-base/Technical-Debt.md with technical debt assessment
+- POPULATE .claude/trinity/knowledge-base/ARCHITECTURE.md with detailed architecture analysis
+- POPULATE .claude/trinity/knowledge-base/ISSUES.md with discovered issues
+- POPULATE .claude/trinity/knowledge-base/To-do.md with identified tasks
+- POPULATE .claude/trinity/knowledge-base/Technical-Debt.md with technical debt assessment
 - Update existing Trinity.md if needed
 
 ### Phase 3: INO (Context Specialist) - Establish context hierarchy
 - Analyze codebase context and complexity
 - UPDATE existing CLAUDE.md files with project-specific instructions
-- POPULATE trinity/knowledge-base/ISSUES.md database structure
+- POPULATE .claude/trinity/knowledge-base/ISSUES.md database structure
 - Verify CLAUDE.md hierarchy is complete
 
 ### Phase 4: JUNO (Quality Auditor) - Perform comprehensive audit
@@ -389,7 +390,7 @@ Suggestions:
 - Verify all documentation files are populated (not empty)
 - Validate CLAUDE.md hierarchy completeness
 - Check that knowledge base documents have real content
-- Generate audit report in trinity/reports/
+- Generate audit report in .claude/trinity/reports/
 - Report findings to user with compliance score
 
 ### Phase 5: EIN (CI/CD Specialist) - Review CI/CD and Pre-commit Configuration
@@ -401,7 +402,6 @@ Suggestions:
 1. **Check for GitHub Actions workflows:**
    ```bash
    ls .github/workflows/ci.yml 2>/dev/null && echo "CI FOUND" || echo "CI NOT_FOUND"
-   ls .github/workflows/cd.yml 2>/dev/null && echo "CD FOUND" || echo "CD NOT_FOUND"
    ```
 
 2. **Check for pre-commit configuration:**
@@ -411,7 +411,7 @@ Suggestions:
 
 **Decision Tree:**
 
-- **IF any CI/CD files exist (ci.yml, cd.yml, OR pre-commit config):**
+- **IF any CI/CD files exist (ci.yml OR pre-commit config):**
   - ✅ **Invoke EIN** - Adopt EIN (CI/CD Specialist) persona
   - Continue with "EIN's Responsibilities" below
   - Include EIN's work in JUNO's audit report
@@ -443,15 +443,7 @@ Suggestions:
    - **Validate** triggers are correct (push to main/dev, pull requests)
    - **Confirm** coverage threshold enforcement is configured
 
-**2. GitHub Actions CD Workflow** (if `.github/workflows/cd.yml` exists):
-   - **Read** the deployed cd.yml file
-   - **Verify** deployment stages (CI gate → build → staging → production)
-   - **Validate** CI workflow is called as prerequisite
-   - **Customize** deployment commands for project type
-   - **Confirm** environment protection is documented
-   - **Validate** artifact management (upload/download between jobs)
-
-**3. Pre-commit Hooks** (if `.pre-commit-config.yaml` exists):
+**2. Pre-commit Hooks** (if `.pre-commit-config.yaml` exists):
    - **Read** the deployed .pre-commit-config.yaml file
    - **Verify** all hooks are configured:
      - Standard hooks (trailing whitespace, YAML/JSON validation, etc.)
@@ -475,12 +467,6 @@ After reviewing and customizing CI/CD files, EIN should report:
   - Runtime: {{DETECTED_RUNTIME}}
   - Coverage: ≥80% enforced
 
-- .github/workflows/cd.yml ✅
-  - Status: Ready (deployment commands customized)
-  - Staging: Auto-deploy on main branch
-  - Production: Deploy via version tags (v*)
-  - Environments: Require setup (see instructions below)
-
 - .pre-commit-config.yaml ✅ (if deployed)
   - Status: Ready (customized for {{FRAMEWORK}})
   - Hooks: Linting, type checking, tests
@@ -495,23 +481,15 @@ After reviewing and customizing CI/CD files, EIN should report:
 
 **Activation Instructions:**
 
-📋 **Step 1: Activate GitHub Actions Workflows**
+📋 **Step 1: Activate GitHub Actions Workflow**
 ```bash
-# Workflows are already in place, just commit and push
-git add .github/workflows/ci.yml .github/workflows/cd.yml
-git commit -m "Activate Trinity CI/CD pipelines"
+# Workflow is already in place, just commit and push
+git add .github/workflows/ci.yml
+git commit -m "Activate Trinity CI pipeline"
 git push
 ```
 
-📋 **Step 2: Set Up GitHub Environments** (Required for CD)
-1. Go to: Repository Settings → Environments
-2. Create "staging" environment:
-   - No protection rules needed
-3. Create "production" environment:
-   - ✅ Enable "Required reviewers" (add team members)
-   - ⏱️ Optional: "Wait timer" (e.g., 5 minutes before deploy)
-
-📋 **Step 3: Activate Pre-commit Hooks** (Optional but Recommended)
+📋 **Step 2: Activate Pre-commit Hooks** (Optional but Recommended)
 ```bash
 # Install pre-commit framework
 pip install pre-commit

package/dist/templates/{shared/claude-commands → .claude/commands/investigation}/trinity-create-investigation.md.template

@@ -1,5 +1,11 @@
----
-description: Launch the Investigation Wizard to create structured investigations
+# Trinity Create Investigation
+
+**Command:** `/investigation:trinity-create-investigation`
+**Purpose:** Launch the Investigation Wizard to create structured investigations
+**Architecture:** INO wizard → Template selection → File creation
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
 
 Launch the Trinity Method Investigation Wizard to create a structured investigation interactively.
@@ -45,7 +51,7 @@ Define completion criteria:
 
 **Step 6: Template Selection**
 Offer templates based on investigation type:
-- Standard templates (from trinity/templates/investigations/)
+- Standard templates (from .claude/trinity/templates/investigations/)
 - Custom templates (from user's template library)
 - Generate new template
 
@@ -54,7 +60,7 @@ Show investigation summary and confirm creation.
 
 **Output:**
 Create investigation file at:
-`trinity/investigations/INV-XXX-{title}.md`
+`.claude/trinity/investigations/INV-XXX-{title}.md`
 
 **Post-Creation:**
 Ask if user wants to:
@@ -63,13 +69,13 @@ Ask if user wants to:
 - Schedule for later
 
 **Orchestration:**
-Once investigation is created in `trinity/investigations/`, execute it:
+Once investigation is created in `.claude/trinity/investigations/`, execute it:
 
 ```bash
 /trinity-orchestrate @INV-001-example-investigation.md
 ```
 
-**AJ MAESTRO** picks up the investigation from `trinity/investigations/` and orchestrates the investigation, leaving findings in `trinity/reports/`.
+**AJ MAESTRO** picks up the investigation from `.claude/trinity/investigations/` and orchestrates the investigation, leaving findings in `.claude/trinity/reports/`.
 
 **CRITICAL: Investigation Protocol**
 ⚠️ **INVESTIGATIONS ARE READ-ONLY OPERATIONS**
@@ -106,7 +112,7 @@ INV-012-authentication-flow-review.md
 INV-025-database-query-optimization.md
 ```
 
-**Auto-Numbering**: System scans `trinity/investigations/` and assigns next number
+**Auto-Numbering**: System scans `.claude/trinity/investigations/` and assigns next number
 
 ---
 

package/dist/templates/{shared/claude-commands → .claude/commands/investigation}/trinity-investigate-templates.md.template

@@ -1,10 +1,14 @@
----
-description: Guide to Trinity investigation templates for structured problem-solving
----
-
 # Trinity Investigation Templates
 
-**Purpose:** Guide users through selecting and using investigation templates for structured, comprehensive problem-solving.
+**Command:** `/investigation:trinity-investigate-templates`
+**Purpose:** Guide to Trinity investigation templates for structured problem-solving
+**Architecture:** Documentation reference (no execution)
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
+---
+
+Guide users through selecting and using investigation templates for structured, comprehensive problem-solving.
 
 ## Overview
 
@@ -446,11 +450,11 @@ Is it new functionality?
 
 ```bash
 # Copy template to investigations folder
-cp trinity/templates/investigations/[type].md \
-   trinity/investigations/INV-XXX-[title].md
+cp .claude/trinity/templates/investigations/[type].md \
+   .claude/trinity/investigations/INV-XXX-[title].md
 
 # Fill out investigation
-# Edit: trinity/investigations/INV-XXX-[title].md
+# Edit: .claude/trinity/investigations/INV-XXX-[title].md
 ```
 
 ### 2. Link to Design Doc
@@ -458,7 +462,7 @@ cp trinity/templates/investigations/[type].md \
 Every investigation should reference the Design Doc:
 
 ```markdown
-**Design Doc:** [Link to trinity/design-docs/[name].md]
+**Design Doc:** [Link to .claude/trinity/design-docs/[name].md]
 ```
 
 ### 3. Complete Investigation Thoroughly
@@ -479,10 +483,10 @@ Every investigation should reference the Design Doc:
 ```
 
 This command will:
-- Archive all completed investigations to `trinity/archive/investigations/`
-- Archive work orders to `trinity/archive/work-orders/`
-- Archive reports to `trinity/archive/reports/`
-- Archive session logs to `trinity/archive/sessions/`
+- Archive all completed investigations to `.claude/trinity/archive/investigations/`
+- Archive work orders to `.claude/trinity/archive/work-orders/`
+- Archive reports to `.claude/trinity/archive/reports/`
+- Archive session logs to `.claude/trinity/archive/sessions/`
 - Organize archives by date (YYYY-MM format)
 
 ## Integration with Workflow Orchestration
@@ -569,7 +573,7 @@ Templates work seamlessly with `/trinity-orchestrate`:
 
 After deployment, templates are located in:
 ```
-trinity/templates/investigations/
+.claude/trinity/templates/investigations/
 ├── bug.md
 ├── performance.md
 ├── security.md
@@ -683,7 +687,7 @@ After investigating templates, verify your findings:
 ```bash
 # Count template files
 find src/templates -name "*.template" | wc -l
-# Expected: 19 agent templates + knowledge base templates
+# Expected: 18 agent templates + knowledge base templates
 
 # Verify organization
 ls -la src/templates/agents/leadership/

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

@@ -1,5 +1,11 @@
----
-description: Generate AI-powered investigation plans with visualizations
+# Trinity Plan Investigation
+
+**Command:** `/investigation:trinity-plan-investigation`
+**Purpose:** Generate AI-powered investigation plans with visualizations
+**Architecture:** INO analysis → Plan generation → Mermaid visualization
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
 
 Generate a comprehensive AI-powered investigation plan using the Trinity Method.
@@ -70,7 +76,7 @@ graph TD
 
 **Output:**
 Save investigation plan to:
-`trinity/investigations/plans/PLAN-{investigation-title}.md`
+`.claude/trinity/investigations/plans/PLAN-{investigation-title}.md`
 
 **Plan Includes:**
 - Executive summary
@@ -119,15 +125,15 @@ Save investigation plan to:
 ```
 1. /trinity-create-investigation
    → Creates INV-XXX-problem.md
-   
+
 2. /trinity-plan-investigation
    → Reads INV-XXX-problem.md
    → Creates investigation-plan-XXX.md
-   
+
 3. Execute investigation
    → Follow plan
    → Document findings
-   
+
 4. Archive results
    → Update INV-XXX with conclusions
 ```

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

@@ -1,10 +1,14 @@
 # Trinity CHANGELOG Management
 
-**Purpose:** Launch APO (Documentation Specialist) to maintain CHANGELOG.md in Keep-a-Changelog format.
+**Command:** `/execution:trinity-changelog`
+**Purpose:** Launch APO (Documentation Specialist) to maintain CHANGELOG.md in Keep-a-Changelog format
+**Architecture:** APO 3-phase process (Discovery → Update → Report)
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
 
 **Use Case:** Ensure CHANGELOG.md exists, follows Keep-a-Changelog format, and documents project changes.
 
-**Deliverable:** CHANGELOG audit report in `trinity/reports/CHANGELOG-AUDIT-{date}.md`
+**Deliverable:** CHANGELOG audit report in `.claude/trinity/reports/CHANGELOG-AUDIT-{date}.md`
 
 ---
 
@@ -427,7 +431,7 @@ if (missing_categories.length > 0) {
 
 ### Phase 3: CHANGELOG Audit Report
 
-**APO Generates:** `trinity/reports/CHANGELOG-AUDIT-{date}.md`
+**APO Generates:** `.claude/trinity/reports/CHANGELOG-AUDIT-{date}.md`
 
 **Required Report Structure:**
 
@@ -553,7 +557,7 @@ if (missing_categories.length > 0) {
 ---
 
 **Report Generated:** {timestamp}
-**Report Location:** trinity/reports/CHANGELOG-AUDIT-{date}.md
+**Report Location:** .claude/trinity/reports/CHANGELOG-AUDIT-{date}.md
 ```
 
 ---
@@ -579,7 +583,7 @@ if (missing_categories.length > 0) {
 
 **After `/trinity-changelog` completes, verify:**
 
-1. ✅ Check `trinity/reports/CHANGELOG-AUDIT-{date}.md`
+1. ✅ Check `.claude/trinity/reports/CHANGELOG-AUDIT-{date}.md`
 2. ✅ Verify CHANGELOG.md exists in root
 3. ✅ Check [Unreleased] section present
 4. ✅ Verify format score ≥ 60/100
@@ -643,6 +647,3 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ```
 
 ---
-
-** Trinity Version:** 2.0.9
-**Last Updated:** 2026-01-12