trinity-method-sdk 2.0.9 → 2.2.0

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

@@ -1,5 +1,11 @@
----
-description: Guide through your first Trinity workflow
+# Trinity Start
+
+**Command:** `/session:trinity-start`
+**Purpose:** Guide through your first Trinity workflow
+**Architecture:** ALY workflow selection → Context setup → First task planning
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
 
 Guide the user through starting their first Trinity Method workflow.
@@ -59,7 +65,7 @@ For complex or long-running tasks, suggest creating a work order:
 /trinity-workorder
 ```
 
-This creates a structured investigation in `trinity/work-orders/` with:
+This creates a structured investigation in `.claude/trinity/work-orders/` with:
 - Problem statement
 - Requirements and acceptance criteria
 - Design decisions
@@ -71,7 +77,6 @@ This creates a structured investigation in `trinity/work-orders/` with:
 **Leadership:**
 - ALY (CTO) - Strategic planning, architecture decisions
 - AJ MAESTRO - Workflow orchestration and planning
-- AJ CC - Code quality oversight
 
 **Deployment:**
 - TAN - Trinity structure deployment

package/dist/templates/{shared/claude-commands → .claude/commands/utility}/trinity-agents.md.template

@@ -1,5 +1,11 @@
----
-description: Display Trinity agent directory and information
+# Trinity Agents
+
+**Command:** `/utility:trinity-agents`
+**Purpose:** Display Trinity agent directory and information
+**Architecture:** Reference documentation (no execution)
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
 
 Display the Trinity Method Agent Directory with all 19 specialized agents.
@@ -10,11 +16,10 @@ Display the Trinity Method Agent Directory with all 19 specialized agents.
 
 Agents are organized in 5 subdirectories by role:
 
-### 1. Leadership Team (3 agents)
+### 1. Leadership Team (2 agents)
 Located in: `.claude/agents/leadership/`
 - **ALY (Chief Technology Officer)** - Strategic planning and architecture decisions
 - **AJ MAESTRO (Orchestration Lead)** - Workflow planning and agent coordination
-- **AJ CC (Code Coordinator)** - Code quality and implementation oversight
 
 ### 2. Deployment Team (4 agents)
 Located in: `.claude/agents/deployment/`
@@ -99,7 +104,6 @@ Ask which agent you want to learn more about, and Claude will read that agent's
 |-------|------|-------------|---------------|
 | **ALY** | CTO | Strategic decisions, stop point reviews | leadership/aly-cto.md |
 | **AJ MAESTRO** | Orchestrator | Coordinate Medium/Large workflows | leadership/aj-maestro.md |
-| **AJ CC** | Continuity | Session recovery, investigations | leadership/aj-cc.md |
 | **TAN** | Structure | Deploy Trinity folders (init only) | deployment/tan-structure.md |
 | **ZEN** | Knowledge | Populate knowledge base (init only) | deployment/zen-knowledge.md |
 | **INO** | Context | CLAUDE.md hierarchy (init only) | deployment/ino-context.md |
@@ -128,9 +132,9 @@ What do you need?
 │
 ├─ Start new work → ALY (determines scale) → AJ MAESTRO
 │
-├─ Resume interrupted work → AJ CC (session recovery)
+├─ Resume interrupted work → AJ MAESTRO (session recovery)
 │
-├─ Investigation only → AJ CC (read-only analysis)
+├─ Investigation only → ALY (read-only analysis)
 │
 └─ Specific task:
     │
@@ -159,7 +163,6 @@ What do you need?
 **Examples**:
 - **ALY** - Chief Technology Officer (CTO)
 - **AJ MAESTRO** - Implementation Orchestrator
-- **AJ CC** - Continuous Context Specialist
 - **MON** - Requirements Analyst
 - **KIL** - Task Executor
 

package/dist/templates/{shared/claude-commands → .claude/commands/utility}/trinity-verify.md.template

@@ -1,32 +1,37 @@
----
-description: Verify Trinity Method installation completeness
+# Trinity Verify
+
+**Command:** `/utility:trinity-verify`
+**Purpose:** Verify Trinity Method installation completeness
+**Architecture:** TAN structure validation → File integrity checks → Deployment verification
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
 
 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/
+   - .claude/trinity/knowledge-base/
+   - .claude/trinity/reports/
+   - .claude/trinity/sessions/
+   - .claude/trinity/investigations/
+   - .claude/trinity/investigations/plans/
+   - .claude/trinity/work-orders/
+   - .claude/trinity/templates/
+   - .claude/trinity/templates/work-orders/
+   - .claude/trinity/templates/investigations/
+   - .claude/trinity/archive/work-orders/
+   - .claude/trinity/archive/investigations/
+   - .claude/trinity/archive/reports/
+   - .claude/trinity/archive/sessions/
 
 2. **CLAUDE.md Context Files:**
    - Root CLAUDE.md (behavioral hierarchy)
-   - trinity/CLAUDE.md (Trinity-specific context)
+   - .claude/trinity/CLAUDE.md (Trinity-specific context)
 
-3. **Agent Organization (19 agents in 5 subdirectories):**
-   - .claude/agents/leadership/ (3 agents: ALY, AJ MAESTRO, AJ CC)
+3. **Agent Organization (18 agents in 5 subdirectories):**
+   - .claude/agents/leadership/ (2 agents: ALY, AJ MAESTRO)
    - .claude/agents/deployment/ (4 agents: TAN, ZEN, INO, EIN)
    - .claude/agents/audit/ (1 agent: JUNO)
    - .claude/agents/planning/ (4 agents: MON, ROR, TRA, EUS)
@@ -42,9 +47,9 @@ Check for:
    - 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/
+   - Work Orders: 6 templates in .claude/trinity/templates/work-orders/
+   - Investigations: 5 templates in .claude/trinity/templates/investigations/
+   - Documentation: 2 templates in .claude/trinity/templates/documentation/
 
 6. **Knowledge Base Files (9 files):**
    - ARCHITECTURE.md, Trinity.md, To-do.md, ISSUES.md, Technical-Debt.md
@@ -53,7 +58,6 @@ Check for:
 
 7. **CI/CD Workflows (if deployed):**
    - .github/workflows/ci.yml (BAS 6-phase quality gates)
-   - .github/workflows/cd.yml (Deployment pipeline)
 
 Report:
 - ✅ Installed components
@@ -80,17 +84,16 @@ Report:
 - ✅ .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):
+- ✅ .claude/trinity/knowledge-base/
+- ✅ .claude/trinity/work-orders/
+- ✅ .claude/trinity/sessions/
+- ✅ .claude/trinity/planning/
+- ✅ .claude/trinity/reports/
+
+### 2. Agent Deployment ✅ (18/18)
+**Leadership** (2/2):
 - ✅ 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)
@@ -146,7 +149,6 @@ Report:
 
 ### 5. CI/CD Workflows ✅ (Optional)
 - ✅ .github/workflows/ci.yml (BAS 6-phase gates)
-- ✅ .github/workflows/cd.yml (Deployment pipeline)
 
 ## Summary
 **Status**: ✅ FULLY DEPLOYED
@@ -171,17 +173,16 @@ Report:
 - ✅ .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):
+- ✅ .claude/trinity/knowledge-base/
+- ❌ .claude/trinity/work-orders/ (MISSING)
+- ✅ .claude/trinity/sessions/
+- ✅ .claude/trinity/planning/
+- ❌ .claude/trinity/reports/ (MISSING)
+
+### 2. Agent Deployment ⚠️ (16/18)
+**Leadership** (2/2):
 - ✅ aly-cto.md
 - ✅ aj-maestro.md
-- ✅ aj-cc.md
 
 **Deployment** (2/4):
 - ✅ tan-structure.md
@@ -244,8 +245,8 @@ Report:
 
 **Symptom**:
 ```
-❌ trinity/work-orders/ not found
-❌ trinity/reports/ not found
+❌ .claude/trinity/work-orders/ not found
+❌ .claude/trinity/reports/ not found
 ```
 
 **Cause**: Incomplete `trinity deploy` or TAN agent failure
@@ -253,19 +254,19 @@ Report:
 **Fix**:
 ```bash
 # Manually create missing directories
-mkdir -p trinity/work-orders
-mkdir -p trinity/reports
-mkdir -p trinity/sessions
-mkdir -p trinity/planning
+mkdir -p .claude/trinity/work-orders
+mkdir -p .claude/trinity/reports
+mkdir -p .claude/trinity/sessions
+mkdir -p .claude/trinity/planning
 
 # Verify creation
-ls -la trinity/
+ls -la .claude/trinity/
 ```
 
 **Verification**:
 ```bash
 # Should show all directories
-trinity/
+.claude/trinity/
 ├── work-orders/
 ├── reports/
 ├── sessions/
@@ -325,20 +326,20 @@ find .claude/agents -name "*.md" -type f
 
 # OR manually populate files
 # ISSUES.md should contain:
-echo "# Known Issues\n\nNo issues currently tracked." > trinity/knowledge-base/ISSUES.md
+echo "# Known Issues\n\nNo issues currently tracked." > .claude/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
+echo "# Project To-Do List\n\nNo tasks currently tracked." > .claude/trinity/knowledge-base/To-do.md
 ```
 
 **Verification**:
 ```bash
 # Check file sizes (should be >0 bytes)
-ls -lh trinity/knowledge-base/*.md
+ls -lh .claude/trinity/knowledge-base/*.md
 
 # Verify content
-cat trinity/knowledge-base/ISSUES.md
-cat trinity/knowledge-base/To-do.md
+cat .claude/trinity/knowledge-base/ISSUES.md
+cat .claude/trinity/knowledge-base/To-do.md
 ```
 
 ---
@@ -446,8 +447,6 @@ ls -la .github/workflows/
 
 # Expected (if CI/CD requested):
 # ci.yml
-# cd.yml
 ```
 
 ---
-

package/dist/templates/{shared/claude-commands → .claude/commands/utility}/trinity-workorder.md.template

@@ -1,9 +1,13 @@
----
-description: Create Trinity Method work orders interactively
----
-
 # Trinity Work Orders
 
+**Command:** `/utility:trinity-workorder`
+**Purpose:** Create Trinity Method work orders interactively
+**Architecture:** MON wizard → Template selection → Work order creation
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
+---
+
 ## What Are Work Orders?
 
 Work orders are structured task documents that provide clear objectives, task breakdown, progress tracking, context preservation, and quality assurance.
@@ -38,7 +42,7 @@ When `/trinity-workorder` is invoked, the agent will:
    - Deliverables and acceptance criteria
    - Priority and estimated effort
 
-2. **Select appropriate template** from `trinity/templates/work-orders/`:
+2. **Select appropriate template** from `.claude/trinity/templates/work-orders/`:
    - **Investigation:** Research and analysis tasks
    - **Implementation:** Feature development tasks
    - **Analysis:** Code analysis and review tasks
@@ -46,7 +50,7 @@ When `/trinity-workorder` is invoked, the agent will:
    - **Pattern:** Pattern detection and analysis
    - **Verification:** Verification and validation tasks
 
-3. **Create work order file** in `trinity/work-orders/WO-XXX-{task-name}.md`
+3. **Create work order file** in `.claude/trinity/work-orders/WO-XXX-{task-name}.md`
 
 4. **Populate template** with:
    - Clear mission objective
@@ -74,13 +78,13 @@ When `/trinity-workorder` is invoked, the agent will:
 
 ## Orchestration
 
-Once work order is created in `trinity/work-orders/`, execute it:
+Once work order is created in `.claude/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.
+**AJ MAESTRO** picks up the work order from `.claude/trinity/work-orders/` and orchestrates the 18-agent team to complete the task following Trinity Method workflows.
 
 ---
 
@@ -92,7 +96,7 @@ See WO-042 example in work order files showing full structure with objectives, i
 
 ## Available Templates
 
-Work order templates are located in `trinity/templates/work-orders/`:
+Work order templates are located in `.claude/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

package/dist/templates/ci/ci.yml.template

@@ -1,9 +1,9 @@
-# {{PROJECT_NAME}} - Trinity Method CI/CD Pipeline
+# {{PROJECT_NAME}} - Trinity Method CI Pipeline
 # Trinity Method v{{TRINITY_VERSION}}
 # Framework: {{FRAMEWORK}}
 # Generated by: EIN (CI/CD Specialist)
 
-name: Trinity CI/CD Pipeline
+name: Trinity CI Pipeline
 
 on:
   push:

package/dist/templates/root/CLAUDE.md.template

@@ -20,7 +20,7 @@ This project uses the Trinity Method with layered context files:
 Project-specific overview, architecture, and living documentation references.
 
 ### 2. Trinity Method Context
-**File**: [trinity/CLAUDE.md](trinity/CLAUDE.md)
+**File**: [.claude/trinity/CLAUDE.md](.claude/trinity/CLAUDE.md)
 Enforces Trinity Method protocols: investigation-first development, quality gates, crisis management.
 
 ### 3. Technology-Specific Context
@@ -29,7 +29,7 @@ Framework-specific debugging standards, performance optimization, testing patter
 
 ### 4. Agent Directory
 **File**: [.claude/EMPLOYEE-DIRECTORY.md](.claude/EMPLOYEE-DIRECTORY.md)
-Complete guide to the 19-agent Trinity team and workflow orchestration.
+Complete guide to the 18-agent Trinity team and workflow orchestration.
 
 ---
 
@@ -37,29 +37,29 @@ Complete guide to the 19-agent Trinity team and workflow orchestration.
 
 ### Architecture
 
-See: [trinity/knowledge-base/ARCHITECTURE.md](trinity/knowledge-base/ARCHITECTURE.md)
+See: [.claude/trinity/knowledge-base/ARCHITECTURE.md](.claude/trinity/knowledge-base/ARCHITECTURE.md)
 
 ### Current Tasks
 
-See: [trinity/knowledge-base/To-do.md](trinity/knowledge-base/To-do.md)
+See: [.claude/trinity/knowledge-base/To-do.md](.claude/trinity/knowledge-base/To-do.md)
 
 ### Known Issues
 
-See: [trinity/knowledge-base/ISSUES.md](trinity/knowledge-base/ISSUES.md)
+See: [.claude/trinity/knowledge-base/ISSUES.md](.claude/trinity/knowledge-base/ISSUES.md)
 
 ### Technical Debt
 
-See: [trinity/knowledge-base/Technical-Debt.md](trinity/knowledge-base/Technical-Debt.md)
+See: [.claude/trinity/knowledge-base/Technical-Debt.md](.claude/trinity/knowledge-base/Technical-Debt.md)
 
 ### Testing Standards
 
-See: [trinity/knowledge-base/TESTING-PRINCIPLES.md](trinity/knowledge-base/TESTING-PRINCIPLES.md)
+See: [.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md](.claude/trinity/knowledge-base/TESTING-PRINCIPLES.md)
 
 ### Coding Principles
 
-See: [trinity/knowledge-base/CODING-PRINCIPLES.md](trinity/knowledge-base/CODING-PRINCIPLES.md)
+See: [.claude/trinity/knowledge-base/CODING-PRINCIPLES.md](.claude/trinity/knowledge-base/CODING-PRINCIPLES.md)
 
 ---
 
 **Trinity Method:** Investigation-first development methodology
-**Session Location:** trinity/sessions/
+**Session Location:** .claude/trinity/sessions/

package/dist/templates/root/linting/nodejs/.husky-pre-commit.template

@@ -0,0 +1,5 @@
+#!/usr/bin/env sh
+# {{PROJECT_NAME}} - Pre-commit Quality Gates
+# Trinity Method v{{TRINITY_VERSION}}
+# Framework: {{FRAMEWORK}}
+npx lint-staged