trinity-method-sdk 2.0.8 → 2.1.0

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

@@ -1,6 +1,10 @@
 # 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.
 
@@ -71,6 +75,27 @@ The `/trinity-readme` command invokes APO (Documentation Specialist) to manage R
 
 **Why:** Trinity Method SDK is a tool for developers. The project's documentation should focus exclusively on the project's code, features, and usage - not on the development methodology used to create it.
 
+### Rule 1 Enforcement Checklist
+
+Before finalizing any README, verify:
+
+- [ ] No 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.)
+- [ ] No Trinity session files documented
+- [ ] No Trinity work orders documented
+
+**Verification Command:**
+```bash
+# Check for forbidden Trinity references in README
+grep -i "trinity/" README.md && echo "❌ VIOLATION: Documents trinity/ directory"
+grep -i "\.claude/" README.md && echo "❌ VIOLATION: Documents .claude/ directory"
+grep -i "/trinity-" README.md && echo "❌ VIOLATION: Documents Trinity commands"
+```
+
+**If any violations found:** Remove the offending documentation immediately.
+
 ---
 
 ## When to Use `/trinity-readme`
@@ -298,6 +323,52 @@ for (let i = 0; i < glob_output_lines; i++) {
 }
 ```
 
+**Step 4.5: Filter Gitignored and Trinity Directories (CRITICAL)**
+
+**CRITICAL: Remove Trinity infrastructure and gitignored directories from documentation.**
+
+```bash
+# Filter out Trinity infrastructure (ALWAYS excluded)
+filtered_directories = []
+
+for each directory in all_directories:
+  # ALWAYS skip Trinity infrastructure
+  if directory.includes("trinity/") or directory.includes(".claude/"):
+    echo "SKIP: $directory (Trinity infrastructure - never document)"
+    continue
+
+  # Check if gitignored (optional but recommended)
+  if git check-ignore -q "$directory" 2>/dev/null; then
+    echo "SKIP: $directory (gitignored)"
+    continue
+  fi
+
+  # Include this directory
+  filtered_directories.push(directory)
+  echo "INCLUDE: $directory"
+done
+```
+
+**Trinity Detection Warning:**
+
+If you detect 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
+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/
+✓ Filtering Trinity infrastructure and gitignored directories...
+  - 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.
+
 **Step 5: Report Complete Inventory (Using Validated Count)**
 
 APO MUST output:
@@ -352,7 +423,8 @@ APO MUST answer ALL checklist items:
    - If NO: STOP and use Glob output count
 
 6. **Project Structure Sanity:**
-   - For project with backend/, frontend/, database/, trinity/, do I expect nested CLAUDE.md files? ✅ YES | ❌ NO
+   - 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)
    - If YES but none found: Re-run Glob with explicit paths
 
 **Self-Verification Action:**
@@ -362,12 +434,79 @@ IF any critical item = ❌ NO:
     - backend/**/CLAUDE.md
     - frontend/**/CLAUDE.md
     - database/**/CLAUDE.md
-    - trinity/**/CLAUDE.md
+    - src/**/CLAUDE.md
+    - lib/**/CLAUDE.md
   Merge results and re-validate
 
+**Note:** Do NOT include trinity/ or .claude/ patterns - these are methodology infrastructure.
+
 **Checklist Completion:** ✅ 6/6 items verified
 ```
 
+**Step 7: License Verification (CRITICAL)**
+
+**CRITICAL: Verify actual LICENSE file before generating license badges.**
+
+Before generating any license badge, read and verify the LICENSE file:
+
+1. **Check for LICENSE file:**
+   ```bash
+   # Check for LICENSE file (various naming conventions)
+   if exists("LICENSE"): LICENSE_FILE = "LICENSE"
+   elif exists("LICENSE.md"): LICENSE_FILE = "LICENSE.md"
+   elif exists("LICENSE.txt"): LICENSE_FILE = "LICENSE.txt"
+   elif exists("LICENCE"): LICENSE_FILE = "LICENCE"
+   else: LICENSE_FILE = null
+   ```
+
+2. **Read LICENSE file and detect type:**
+   ```javascript
+   // Read first 3 lines to identify license type
+   firstLine = read(LICENSE_FILE).lines[0].toUpperCase()
+   firstThreeLines = read(LICENSE_FILE).lines.slice(0, 3).join(' ').toUpperCase()
+
+   // Detect license type from file header
+   if (firstLine.includes('MIT LICENSE')): DETECTED_LICENSE = 'MIT'
+   elif (firstLine.includes('ISC LICENSE')): DETECTED_LICENSE = 'ISC'
+   elif (firstLine.includes('APACHE LICENSE')): DETECTED_LICENSE = 'Apache-2.0'
+   elif (firstLine.includes('BSD 3-CLAUSE')): DETECTED_LICENSE = 'BSD-3-Clause'
+   elif (firstLine.includes('BSD 2-CLAUSE')): DETECTED_LICENSE = 'BSD-2-Clause'
+   elif (firstThreeLines.includes('GNU GENERAL PUBLIC LICENSE VERSION 3')): DETECTED_LICENSE = 'GPL-3.0'
+   elif (firstThreeLines.includes('GNU GENERAL PUBLIC LICENSE VERSION 2')): DETECTED_LICENSE = 'GPL-2.0'
+   elif (firstThreeLines.includes('GNU LESSER GENERAL PUBLIC LICENSE')): DETECTED_LICENSE = 'LGPL-3.0'
+   else: DETECTED_LICENSE = null
+   ```
+
+3. **Compare with package.json (if exists):**
+   ```javascript
+   if exists("package.json"):
+     PACKAGE_LICENSE = read("package.json").license
+
+     if (DETECTED_LICENSE && PACKAGE_LICENSE && DETECTED_LICENSE != PACKAGE_LICENSE):
+       echo "⚠️  WARNING: package.json claims ${PACKAGE_LICENSE} but LICENSE file is ${DETECTED_LICENSE}"
+       echo "Using LICENSE file as source of truth: ${DETECTED_LICENSE}"
+   ```
+
+4. **Determine badge license (priority order):**
+   ```javascript
+   // Priority: LICENSE file > package.json > default
+   if (DETECTED_LICENSE):
+     BADGE_LICENSE = DETECTED_LICENSE  // Use LICENSE file (source of truth)
+   elif (PACKAGE_LICENSE):
+     BADGE_LICENSE = PACKAGE_LICENSE   // Fall back to package.json
+   else:
+     BADGE_LICENSE = "Unlicensed"      // Default if neither found
+   ```
+
+5. **Generate license badge:**
+   ```markdown
+   [![License](https://img.shields.io/badge/License-${BADGE_LICENSE}-yellow)](LICENSE)
+   ```
+
+**Rule:** The LICENSE file is the legal source of truth. package.json metadata is secondary.
+
+**Mismatch Detection:** If LICENSE file and package.json disagree, always use LICENSE file and warn user to update package.json.
+
 ---
 
 ### Phase 2: README Audit (Root + Subdirectories)
@@ -940,7 +1079,7 @@ Scan README.md for common stale content patterns:
 
 **Outdated Date References:**
 ```markdown
-- "Last updated: 2021"
+- "**Last Updated**: 2021"
 - "As of January 2022"
 - "In version 1.0 (released 2020)"
 ```
@@ -1039,7 +1178,7 @@ Scan README for version mentions:
 ```markdown
 ❌ **Outdated Date Reference**
 - **File:** README.md (line Y)
-- **Current (WRONG):** "Last updated: January 2022"
+- **Current (WRONG):** "**Last Updated**: January 2022"
 - **Reality:** Current year is 2025, content is stale
 - **Correct:** Update date or remove if unnecessary
 - **Fix in:** Phase 3 (Root README Update)
@@ -1333,33 +1472,6 @@ for each directory in directories_to_create:
   See [{directory}/CLAUDE.md](CLAUDE.md) for architecture details.
   ```
 
-**Type C: Trinity Directory**
-- **Detection:** Directory name is "trinity"
-- **Template:**
-  ```markdown
-  # Trinity Method
-
-  Trinity Method v2.0 implementation for {project name}.
-
-  ## Directory Structure
-  {Use ls to show trinity/ subdirectories}
-
-  ## Key Files
-  {List actual files in trinity/knowledge-base/ with line counts}
-
-  ## Trinity Commands
-  ```bash
-  /trinity-start          # Start workflow guide
-  /trinity-audit          # Run codebase audit
-  /trinity-readme         # Update READMEs
-  /trinity-docs           # Organize docs/
-  /trinity-changelog      # Update CHANGELOG
-  ```
-
-  ## Documentation
-  See [trinity/CLAUDE.md](CLAUDE.md) for Trinity Method context.
-  ```
-
 **Type D: Test Directory**
 - **Detection:** Directory name contains "test", "__tests__", "spec"
 - **Template:**
@@ -1990,6 +2102,3 @@ If Phase 6 validation shows coverage < 100%, status = ❌ FAILED even if Phase 4
 - Re-run command if failures detected
 
 ---
-
-**Command Specification Version:** 2.0.0
-**Last Updated:** 2025-12-27

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.
@@ -48,7 +54,7 @@ git log --oneline -5
 ```bash
 cat trinity/work-orders/WO-042-jwt-refresh-implementation.md
 # Status: IN PROGRESS
-# Last updated: 2 hours ago
+# **Last Updated**: 2 hours ago
 # Progress: Task 3/7
 ```
 

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

@@ -1,5 +1,11 @@
----
-description: End session and archive work to trinity/archive/
+# Trinity End
+
+**Command:** `/session:trinity-end`
+**Purpose:** End session and archive work to trinity/archive/
+**Architecture:** ALY session summary → Work archival → Documentation update
+**Trinity Version:** 2.1.0
+**Last Updated:** 2026-01-21
+
 ---
 
 End current Trinity Method session and prepare for commit.

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.

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.

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

@@ -1,5 +1,11 @@
----
-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.
@@ -68,7 +74,7 @@ Report:
 ### Example 1: Complete Installation (100%)
 
 ```markdown
-# Trinity v2.0 Verification Report
+# Trinity Verification Report
 
 **Project**: MyApp
 **Date**: 2025-12-18
@@ -450,4 +456,3 @@ ls -la .github/workflows/
 ```
 
 ---
-

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.

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

@@ -1,6 +1,6 @@
 # {{PROJECT_NAME}} - Trinity Method
 
-**Version:** {{TRINITY_VERSION}}
+** Trinity Version:** {{TRINITY_VERSION}}
 **Deployed:** {{DEPLOYMENT_TIMESTAMP}}
 
 ---