trinity-method-sdk 2.0.0 → 2.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (12) hide show
  1. package/CHANGELOG.md +163 -116
  2. package/README.md +44 -59
  3. package/dist/cli/commands/deploy/gitignore.js +0 -1
  4. package/dist/cli/commands/deploy/index.js +1 -1
  5. package/dist/cli/commands/deploy/root-files.js +1 -1
  6. package/dist/cli/commands/deploy/sdk-install.js +1 -1
  7. package/dist/cli/utils/template-processor.js +1 -1
  8. package/dist/templates/claude/EMPLOYEE-DIRECTORY.md.template +4 -4
  9. package/dist/templates/shared/claude-commands/trinity-changelog.md.template +24 -0
  10. package/dist/templates/shared/claude-commands/trinity-docs.md.template +120 -5
  11. package/dist/templates/shared/claude-commands/trinity-readme.md.template +24 -0
  12. package/package.json +94 -94
package/CHANGELOG.md CHANGED
@@ -1,116 +1,163 @@
1
- # Changelog
2
-
3
- All notable changes to Trinity Method SDK will be documented in this file.
4
-
5
- The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
- and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
-
8
- ## [Unreleased]
9
-
10
- ### Added
11
-
12
- ### Changed
13
-
14
- ### Deprecated
15
-
16
- ### Removed
17
-
18
- ### Fixed
19
-
20
- ### Security
21
-
22
- ## [2.0.0] - 2025-12-21
23
-
24
- ### Added
25
-
26
- - **Agent System Expansion:** Grew from 7 to 19 specialized agents
27
- - **Planning Layer (4 agents):** MON (Requirements Analyst), ROR (Design Architect), TRA (Work Planner), EUS (Task Decomposer)
28
- - **Execution Layer (3 agents):** KIL (Task Executor), BAS (Quality Gate), DRA (Code Reviewer)
29
- - **Support Layer (4 agents):** APO (Documentation Specialist), BON (Dependency Manager), CAP (Configuration Specialist), URO (Refactoring Specialist)
30
- - **Leadership & Audit (2 agents):** ALY (Chief Technology Officer), JUNO (Quality Auditor)
31
- - **Infrastructure (5 agents):** TAN, ZEN, INO, EIN, AJ MAESTRO (legacy)
32
- - Increased deployment from 49 to 64 production-ready components
33
- - Expanded slash commands from 8 to 20 commands across 6 categories
34
- - Session Management: `/trinity-start`, `/trinity-continue`, `/trinity-end`
35
- - Planning: `/trinity-requirements`, `/trinity-design`, `/trinity-decompose`, `/trinity-plan`
36
- - Execution: `/trinity-orchestrate`, `/trinity-audit`, `/trinity-readme`, `/trinity-docs`, `/trinity-changelog`
37
- - Investigation: `/trinity-create-investigation`, `/trinity-plan-investigation`, `/trinity-investigate-templates`
38
- - Infrastructure: `/trinity-init`
39
- - Utility: `/trinity-verify`, `/trinity-agents`, `/trinity-workorder`
40
- - Enhanced `/trinity-readme` command template to v2.0.0 with comprehensive validation phases
41
- - Phase 2h: Command/Script/CLI Validation - Verifies all documented commands exist in codebase
42
- - Phase 2i: Code Example Validation - Checks code examples match current API signatures
43
- - Phase 2j: API/Function Reference Validation - Verifies documented functions/classes exist
44
- - Phase 2k: Dependency Claims Validation - Cross-references README with package manifests
45
- - Phase 2l: Stale Content Detection - Finds TODO markers, outdated dates, placeholder text
46
-
47
- ### Changed
48
-
49
- - **BREAKING:** Updated Trinity Method to v2.0.0 architecture
50
- - **Agent System:** Complete agent architecture redesign with specialized layers
51
- - **Documentation System:** Enhanced APO capabilities with comprehensive audit phases
52
- - Refactored 7 functions to reduce cyclomatic complexity (all ≤15)
53
- - Improved code maintainability and readability across codebase
54
- - Enhanced test coverage and reliability (405 tests, 100% passing)
55
-
56
- ### Deprecated
57
-
58
- - AJ MAESTRO orchestrator (v1.0) replaced by ALY in v2.0
59
-
60
- ### Fixed
61
-
62
- - Template path resolution in integration tests
63
- - Linting deployment tests now correctly locate template files
64
- - **Documentation Accuracy:** Fixed 6 critical inaccuracies in README.md
65
- - Removed 24+ non-existent CLI commands (`npx trinity investigate`, `crisis`, `analytics`, etc.)
66
- - Fixed 13 broken documentation links (docs/methodology/, docs/adr/, docs/workflows/)
67
- - Corrected agent count inconsistencies throughout documentation (unified to 19 agents)
68
- - Updated deployment examples to reflect actual CLI (`npx @trinity-method/cli deploy/update`)
69
- - Fixed broken ADR links in src/README.md (replaced with design principles summary)
70
- - Fixed broken ADR links in docs/README.md (removed non-existent file references)
71
-
72
- ---
73
-
74
- ## [1.0.1] - 2025-10-02
75
-
76
- ### Fixed
77
-
78
- - **Critical:** Missing template files in npm package (only 9 of 36 were included)
79
- - Fixed file paths to use bundled templates instead of workspace structure
80
- - All `.md.template` files now properly included in published package
81
- - Updated `deploy.js` and `update.js` to reference correct template locations
82
- - Bundled agents and hooks directly into CLI package for standalone operation
83
-
84
- ### Changed
85
-
86
- - Reorganized package structure to be self-contained when published to npm
87
- - Templates, agents, and hooks now bundled in `packages/cli/templates/`
88
-
89
- ---
90
-
91
- ## [1.0.0] - 2025-10-01
92
-
93
- ### Added
94
-
95
- - Initial release of Trinity Method SDK for Claude Code
96
- - 7 specialized Trinity agents (Aly, AJ, TAN, ZEN, INO, Ein, JUNO)
97
- - Claude Code-exclusive deployment
98
- - Interactive deployment with linting and CI/CD configuration
99
- - Linting configuration (ESLint, Prettier, etc.)
100
- - CI/CD automation (GitHub Actions, GitLab CI)
101
- - Matrix testing support
102
- - Coverage integration (Codecov, Coveralls)
103
- - Employee Directory with agent documentation
104
- - Trinity structure (knowledge-base, templates)
105
- - CLAUDE.md context file deployment
106
- - README injection for Trinity Method section
107
- - 8 slash commands (/trinity-init, /trinity-verify, /trinity-docs, /trinity-start, /trinity-continue, /trinity-end, /trinity-workorder, /trinity-agents)
108
- - Session management with archival system
109
- - Comprehensive CLI documentation
110
-
111
- ### Strategic Decision
112
-
113
- - Focused exclusively on Claude Code for exceptional user experience
114
- - Community contributions welcome for other coding agents
115
-
116
- [1.0.0]: https://github.com/lukadfagundes/trinity-method-sdk/releases/tag/v1.0.0
1
+ # Changelog
2
+
3
+ All notable changes to Trinity Method SDK will be documented in this file.
4
+
5
+ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
+ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
+
8
+ ## [Unreleased]
9
+
10
+ ### Added
11
+
12
+ ### Changed
13
+
14
+ ### Deprecated
15
+
16
+ ### Removed
17
+
18
+ ### Fixed
19
+
20
+ ### Security
21
+
22
+ ## [2.0.2] - 2026-01-02
23
+
24
+ ### Added
25
+
26
+ - **DOCUMENTATION RULES** section to all APO documentation commands (`/trinity-docs`, `/trinity-readme`, `/trinity-changelog`)
27
+ - Rule 1: No Self-Serving Trinity Documentation - Prevents APO from including Trinity Method information in user project documentation
28
+ - Provides clear ✅/❌ examples and rationale for focusing exclusively on user's codebase
29
+ - Explicit **Write tool execution commands** throughout `/trinity-docs` Phase 2
30
+ - Added 🚨 CRITICAL EXECUTION REQUIREMENT section at Phase 2 start
31
+ - Added **EXECUTION REQUIRED** code blocks for each seeding step
32
+ - Added **Phase 2 Execution Summary** with mandatory file creation checklist
33
+ - Ensures APO creates actual documentation files instead of just showing templates
34
+
35
+ ### Changed
36
+
37
+ - **`/trinity-docs` command:** Enhanced Phase 2 with explicit Write tool requirements
38
+ - Step 2 (Guides): Added execution requirements for getting-started.md and framework-specific guides
39
+ - Step 3 (API): Added execution requirements for api/README.md
40
+ - Step 4 (Architecture): Added execution requirements for architecture/overview.md
41
+ - Step 5 (Reference): Added execution requirements for reference/README.md
42
+ - Phase now requires minimum 4 files to be created: getting-started.md, api/README.md, architecture/overview.md, reference/README.md
43
+
44
+ ### Fixed
45
+
46
+ - **APO file creation issue:** `/trinity-docs` now explicitly commands APO to use Write tool, preventing scenario where directory structure is created but documentation files are not written
47
+
48
+ ## [2.0.1] - 2025-12-29
49
+
50
+ ### Added
51
+
52
+ - Installation instructions in README.md with npx and global install options
53
+ - Automatic npm deployment on every push to main branch via GitHub Actions CD workflow
54
+
55
+ ### Changed
56
+
57
+ - **CD Workflow:** Modified to deploy to npm on all main branch pushes (not just version tags)
58
+ - **CD Workflow:** GitHub releases now only created for version tags, not regular commits
59
+ - Updated all package references from `@trinity-method/cli` to `trinity-method-sdk`
60
+
61
+ ### Fixed
62
+
63
+ - Removed redundant `node_modules/` from Trinity's .gitignore additions
64
+
65
+ ## [2.0.0] - 2025-12-21
66
+
67
+ ### Added
68
+
69
+ - **Agent System Expansion:** Grew from 7 to 19 specialized agents
70
+ - **Planning Layer (4 agents):** MON (Requirements Analyst), ROR (Design Architect), TRA (Work Planner), EUS (Task Decomposer)
71
+ - **Execution Layer (3 agents):** KIL (Task Executor), BAS (Quality Gate), DRA (Code Reviewer)
72
+ - **Support Layer (4 agents):** APO (Documentation Specialist), BON (Dependency Manager), CAP (Configuration Specialist), URO (Refactoring Specialist)
73
+ - **Leadership & Audit (2 agents):** ALY (Chief Technology Officer), JUNO (Quality Auditor)
74
+ - **Infrastructure (5 agents):** TAN, ZEN, INO, EIN, AJ MAESTRO (legacy)
75
+ - Increased deployment from 49 to 64 production-ready components
76
+ - Expanded slash commands from 8 to 20 commands across 6 categories
77
+ - Session Management: `/trinity-start`, `/trinity-continue`, `/trinity-end`
78
+ - Planning: `/trinity-requirements`, `/trinity-design`, `/trinity-decompose`, `/trinity-plan`
79
+ - Execution: `/trinity-orchestrate`, `/trinity-audit`, `/trinity-readme`, `/trinity-docs`, `/trinity-changelog`
80
+ - Investigation: `/trinity-create-investigation`, `/trinity-plan-investigation`, `/trinity-investigate-templates`
81
+ - Infrastructure: `/trinity-init`
82
+ - Utility: `/trinity-verify`, `/trinity-agents`, `/trinity-workorder`
83
+ - Enhanced `/trinity-readme` command template to v2.0.0 with comprehensive validation phases
84
+ - Phase 2h: Command/Script/CLI Validation - Verifies all documented commands exist in codebase
85
+ - Phase 2i: Code Example Validation - Checks code examples match current API signatures
86
+ - Phase 2j: API/Function Reference Validation - Verifies documented functions/classes exist
87
+ - Phase 2k: Dependency Claims Validation - Cross-references README with package manifests
88
+ - Phase 2l: Stale Content Detection - Finds TODO markers, outdated dates, placeholder text
89
+
90
+ ### Changed
91
+
92
+ - **BREAKING:** Updated Trinity Method to v2.0.0 architecture
93
+ - **Agent System:** Complete agent architecture redesign with specialized layers
94
+ - **Documentation System:** Enhanced APO capabilities with comprehensive audit phases
95
+ - Refactored 7 functions to reduce cyclomatic complexity (all ≤15)
96
+ - Improved code maintainability and readability across codebase
97
+ - Enhanced test coverage and reliability (405 tests, 100% passing)
98
+
99
+ ### Deprecated
100
+
101
+ - AJ MAESTRO orchestrator (v1.0) replaced by ALY in v2.0
102
+
103
+ ### Fixed
104
+
105
+ - Template path resolution in integration tests
106
+ - Linting deployment tests now correctly locate template files
107
+ - **Documentation Accuracy:** Fixed 6 critical inaccuracies in README.md
108
+ - Removed 24+ non-existent CLI commands (`npx trinity investigate`, `crisis`, `analytics`, etc.)
109
+ - Fixed 13 broken documentation links (docs/methodology/, docs/adr/, docs/workflows/)
110
+ - Corrected agent count inconsistencies throughout documentation (unified to 19 agents)
111
+ - Updated deployment examples to reflect actual CLI (`npx @trinity-method/cli deploy/update`)
112
+ - Fixed broken ADR links in src/README.md (replaced with design principles summary)
113
+ - Fixed broken ADR links in docs/README.md (removed non-existent file references)
114
+
115
+ ---
116
+
117
+ ## [1.0.1] - 2025-10-02 (Legacy - @trinity-method/cli)
118
+
119
+ ### Fixed
120
+
121
+ - **Critical:** Missing template files in npm package (only 9 of 36 were included)
122
+ - Fixed file paths to use bundled templates instead of workspace structure
123
+ - All `.md.template` files now properly included in published package
124
+ - Updated `deploy.js` and `update.js` to reference correct template locations
125
+ - Bundled agents and hooks directly into CLI package for standalone operation
126
+
127
+ ### Changed
128
+
129
+ - Reorganized package structure to be self-contained when published to npm
130
+ - Templates, agents, and hooks now bundled in `packages/cli/templates/`
131
+
132
+ **Note:** This version was published as `@trinity-method/cli`. Starting with v2.0.0, the package was renamed to `trinity-method-sdk`.
133
+
134
+ ---
135
+
136
+ ## [1.0.0] - 2025-10-01 (Legacy - @trinity-method/cli)
137
+
138
+ ### Added
139
+
140
+ - Initial release of Trinity Method SDK for Claude Code
141
+ - 7 specialized Trinity agents (Aly, AJ, TAN, ZEN, INO, Ein, JUNO)
142
+ - Claude Code-exclusive deployment
143
+ - Interactive deployment with linting and CI/CD configuration
144
+ - Linting configuration (ESLint, Prettier, etc.)
145
+ - CI/CD automation (GitHub Actions, GitLab CI)
146
+ - Matrix testing support
147
+ - Coverage integration (Codecov, Coveralls)
148
+ - Employee Directory with agent documentation
149
+ - Trinity structure (knowledge-base, templates)
150
+ - CLAUDE.md context file deployment
151
+ - README injection for Trinity Method section
152
+ - 8 slash commands (/trinity-init, /trinity-verify, /trinity-docs, /trinity-start, /trinity-continue, /trinity-end, /trinity-workorder, /trinity-agents)
153
+ - Session management with archival system
154
+ - Comprehensive CLI documentation
155
+
156
+ ### Strategic Decision
157
+
158
+ - Focused exclusively on Claude Code for exceptional user experience
159
+ - Community contributions welcome for other coding agents
160
+
161
+ **Note:** This version was published as `@trinity-method/cli`. Starting with v2.0.0, the package was renamed to `trinity-method-sdk`.
162
+
163
+ [1.0.0]: https://github.com/lukadfagundes/trinity-method-sdk/releases/tag/v1.0.0
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # Trinity Method SDK
2
2
 
3
- [![npm version](https://img.shields.io/npm/v/@trinity-method/cli?color=success)](https://www.npmjs.com/package/@trinity-method/cli)
3
+ [![npm version](https://img.shields.io/npm/v/trinity-method-sdk?color=success)](https://www.npmjs.com/package/trinity-method-sdk)
4
4
  [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
5
5
  [![Node.js Version](https://img.shields.io/badge/node-%3E%3D16.9.0-brightgreen)](https://nodejs.org/)
6
6
  [![AI Agents](https://img.shields.io/badge/AI%20Agent-Claude%20Code-blue)](https://github.com/lukadfagundes/trinity-method-sdk)
@@ -185,14 +185,33 @@ Trinity deploys **64 production-ready components** in 90 seconds:
185
185
 
186
186
  ## How Trinity Works
187
187
 
188
+ ### Installation
189
+
190
+ **Option 1: Use npx (Recommended - No installation needed)**
191
+
192
+ ```bash
193
+ # Runs latest version without installing
194
+ npx trinity-method-sdk deploy
195
+ ```
196
+
197
+ **Option 2: Global Installation**
198
+
199
+ ```bash
200
+ # Install once globally
201
+ npm install -g trinity-method-sdk
202
+
203
+ # Then use anywhere
204
+ trinity deploy
205
+ ```
206
+
188
207
  ### Quick Start (90 Seconds to Production)
189
208
 
190
209
  ```bash
191
210
  # Navigate to your project
192
211
  cd your-project
193
212
 
194
- # Deploy Trinity Method
195
- npx @trinity-method/cli deploy
213
+ # Deploy Trinity Method (using npx)
214
+ npx trinity-method-sdk deploy
196
215
  ```
197
216
 
198
217
  **Interactive Wizard:**
@@ -209,10 +228,10 @@ npx @trinity-method/cli deploy
209
228
 
210
229
  ```bash
211
230
  # Deploy Trinity to your project
212
- npx @trinity-method/cli deploy
231
+ npx trinity-method-sdk deploy
213
232
 
214
233
  # Update Trinity to latest version
215
- npx @trinity-method/cli update
234
+ npx trinity-method-sdk update
216
235
  ```
217
236
 
218
237
  ### Using Trinity Method (Slash Commands)
@@ -300,19 +319,19 @@ The Trinity Method **philosophy** is agent-agnostic, but this SDK is optimized f
300
319
 
301
320
  ```bash
302
321
  # Node.js/Express API
303
- cd my-api && npx @trinity-method/cli deploy
322
+ cd my-api && npx trinity-method-sdk deploy
304
323
  # Result: API with ESLint, Prettier, pre-commit, 19 agents, quality gates
305
324
 
306
325
  # Python/Django Project
307
- cd my-django && npx @trinity-method/cli deploy
326
+ cd my-django && npx trinity-method-sdk deploy
308
327
  # Result: Django with Black, Flake8, isort, pre-commit, full Trinity infrastructure
309
328
 
310
329
  # Flutter Mobile App
311
- cd my-flutter-app && npx @trinity-method/cli deploy
330
+ cd my-flutter-app && npx trinity-method-sdk deploy
312
331
  # Result: Flutter with Dart Analyzer, pre-commit, investigation templates
313
332
 
314
333
  # Rust CLI Tool
315
- cd my-rust-cli && npx @trinity-method/cli deploy
334
+ cd my-rust-cli && npx trinity-method-sdk deploy
316
335
  # Result: Rust with Clippy, Rustfmt, pre-commit, crisis management
317
336
  ```
318
337
 
@@ -460,65 +479,31 @@ Trinity uses GitHub Actions for comprehensive continuous integration and deploym
460
479
 
461
480
  **CI Workflow Location:** [.github/workflows/ci.yml](.github/workflows/ci.yml)
462
481
 
463
- #### Continuous Deployment (CD)
482
+ #### Publishing to npm
464
483
 
465
- **Automated Publishing to npm:**
466
-
467
- The CD pipeline automatically publishes to npm when you push version tags to the main branch:
484
+ **Manual Publishing Workflow:**
468
485
 
469
486
  ```bash
470
- # Create release commit and tag (triggers CD pipeline on main branch only)
471
- git commit --allow-empty -m "chore: release v2.0.0"
472
- git tag -a v2.0.0 -m "Trinity Method SDK v2.0.0"
473
- git push origin main --follow-tags
474
- ```
487
+ # 1. Update version and changelog
488
+ npm version patch # or minor, major
475
489
 
476
- **CD Pipeline Workflow:**
477
-
478
- 1. **Pre-deployment Validation**: Verify CI passed, tag format correct (v\*), on main branch
479
- 2. **Build & Trinity Validation**: Build artifacts, validate Trinity components
480
- 3. **npm Publish**: Automated publishing using `NPM_TOKEN` secret
481
- 4. **GitHub Release**: Create GitHub release with CHANGELOG
482
- 5. **Deployment Summary**: Post-deployment notifications and metrics
483
-
484
- **CD Workflow Location:** [.github/workflows/cd.yml](.github/workflows/cd.yml)
485
-
486
- **Important:** The CD pipeline only triggers on the `main` branch. Tags pushed to `dev` or `testing` branches will not trigger automated deployment.
487
-
488
- **Required Setup:**
489
-
490
- Before automated deployment works, you must configure the `NPM_TOKEN` secret:
491
-
492
- 1. Create npm granular access token (see [.env.example](.env.example) for detailed instructions)
493
- 2. Add to GitHub Secrets:
494
- - Go to: **Settings → Secrets and variables → Actions → New repository secret**
495
- - Name: `NPM_TOKEN`
496
- - Value: [your npm token]
497
-
498
- **Documentation:**
499
-
500
- - **Complete CI/CD Guide**: [docs/guides/CI-CD-GUIDE.md](docs/guides/CI-CD-GUIDE.md)
501
- - **Quick Reference**: [docs/reference/CI-CD-REFERENCE.md](docs/reference/CI-CD-REFERENCE.md)
502
-
503
- ### Manual Publishing (Optional)
504
-
505
- You can still publish manually if needed:
490
+ # 2. Build and publish
491
+ npm run build
492
+ npm publish --access public
506
493
 
507
- ```bash
508
- # After pushing to main and CI passes
509
- npm login # Authenticate with npm
510
- npm publish # Publishes with prepublishOnly checks
494
+ # 3. Create git tag and push
495
+ git tag -a v2.0.1 -m "Release v2.0.1"
496
+ git push origin main --follow-tags
511
497
  ```
512
498
 
513
499
  **Automated Checks Before Publishing:**
514
500
 
515
- 1. `prepublishOnly` script runs automatically
516
- 2. TypeScript compilation (`npm run build`)
517
- 3. Template copying to dist/
518
- 4. Full test suite execution (`npm run test`)
519
- 5. Only publishes if all checks pass
501
+ The `prepublishOnly` script runs automatically before every publish:
520
502
 
521
- **Note:** Manual publishing is now optional. The CD pipeline handles automated publishing when you create version tags (recommended workflow).
503
+ 1. TypeScript compilation (`npm run build`)
504
+ 2. Template copying to dist/
505
+ 3. Full test suite execution (`npm run test`)
506
+ 4. Only publishes if all checks pass
522
507
 
523
508
  ---
524
509
 
@@ -532,7 +517,7 @@ MIT License - see [LICENSE](LICENSE) for details
532
517
 
533
518
  ### Project Resources
534
519
 
535
- - **npm Package**: [@trinity-method/cli](https://www.npmjs.com/package/@trinity-method/cli)
520
+ - **npm Package**: [trinity-method-sdk](https://www.npmjs.com/package/trinity-method-sdk)
536
521
  - **GitHub**: [lukadfagundes/trinity-method-sdk](https://github.com/lukadfagundes/trinity-method-sdk)
537
522
  - **Issues**: [GitHub Issues](https://github.com/lukadfagundes/trinity-method-sdk/issues)
538
523
  - **Discussions**: [GitHub Discussions](https://github.com/lukadfagundes/trinity-method-sdk/discussions)
package/dist/cli/commands/deploy/gitignore.js CHANGED
@@ -22,7 +22,6 @@ export async function updateGitignore(spinner) {
22
22
  const trinityIgnores = [
23
23
  '',
24
24
  '# Trinity Method SDK',
25
- 'node_modules/',
26
25
  '.claude/',
27
26
  'trinity/',
28
27
  '*CLAUDE.md',
package/dist/cli/commands/deploy/index.js CHANGED
@@ -98,7 +98,7 @@ export async function deploy(options) {
98
98
  PACKAGE_MANAGER: stack.packageManager || 'npm',
99
99
  BACKEND_FRAMEWORK: stack.framework,
100
100
  CURRENT_DATE: new Date().toISOString(),
101
- TRINITY_VERSION: pkg.version || '2.0.0',
101
+ TRINITY_VERSION: pkg.version || '2.0.2',
102
102
  };
103
103
  // STEP 4: Create directory structure
104
104
  const directoriesCreated = await createDirectories(spinner);
package/dist/cli/commands/deploy/root-files.js CHANGED
@@ -39,7 +39,7 @@ async function deployRootClaudeMarkdown(templatesPath, variables) {
39
39
  */
40
40
  async function deployVersionFile(pkgVersion) {
41
41
  const versionPath = validatePath('trinity/VERSION');
42
- await fs.writeFile(versionPath, pkgVersion || '2.0.0');
42
+ await fs.writeFile(versionPath, pkgVersion || '2.0.2');
43
43
  return 1;
44
44
  }
45
45
  /**
package/dist/cli/commands/deploy/sdk-install.js CHANGED
@@ -24,7 +24,7 @@ export async function installSDK(spinner) {
24
24
  if (!packageJson.dependencies) {
25
25
  packageJson.dependencies = {};
26
26
  }
27
- packageJson.dependencies['trinity-method-sdk'] = '^2.0.0';
27
+ packageJson.dependencies['trinity-method-sdk'] = '^2.0.2';
28
28
  await fs.writeJson(packageJsonPath, packageJson, { spaces: 2 });
29
29
  spinner.text = 'Installing Trinity Method SDK (this may take a moment)...';
30
30
  // Install dependencies
package/dist/cli/utils/template-processor.js CHANGED
@@ -24,7 +24,7 @@ const VARIABLE_RESOLVERS = {
24
24
  DEPLOYMENT_TIMESTAMP: (v) => toString(v.DEPLOYMENT_TIMESTAMP || v.timestamp) || new Date().toISOString(),
25
25
  LANGUAGE: (v) => toString(v.LANGUAGE || v.language) || 'Unknown',
26
26
  PACKAGE_MANAGER: (v) => toString(v.PACKAGE_MANAGER || v.packageManager) || 'npm',
27
- TRINITY_VERSION: (v) => toString(v.TRINITY_VERSION) || '2.0.0',
27
+ TRINITY_VERSION: (v) => toString(v.TRINITY_VERSION) || '2.0.2',
28
28
  TECHNOLOGY_STACK: (v) => toString(v.TECHNOLOGY_STACK || v.TECH_STACK || v.techStack) || 'Unknown',
29
29
  PRIMARY_FRAMEWORK: (v) => toString(v.PRIMARY_FRAMEWORK || v.FRAMEWORK || v.framework) || 'Generic',
30
30
  CURRENT_DATE: (v) => toString(v.CURRENT_DATE) || new Date().toISOString().split('T')[0],
package/dist/templates/claude/EMPLOYEE-DIRECTORY.md.template CHANGED
@@ -348,7 +348,7 @@
348
348
  ### Initial Project Setup (Recommended)
349
349
  **1. Deploy Trinity Method:**
350
350
  ```bash
351
- npx @trinity-method/cli deploy
351
+ npx trinity-method-sdk deploy
352
352
  ```
353
353
 
354
354
  **2. Complete knowledge base (optional but recommended):**
@@ -360,7 +360,7 @@ npx @trinity-method/cli deploy
360
360
  ### Fast Deployment (Minimal)
361
361
  **Deploy without metrics:**
362
362
  ```bash
363
- npx @trinity-method/cli deploy --skip-audit
363
+ npx trinity-method-sdk deploy --skip-audit
364
364
  ```
365
365
 
366
366
  **Complete manually when needed:**
@@ -393,7 +393,7 @@ npx @trinity-method/cli deploy --skip-audit
393
393
  ### CI/CD Customization (After Basic Deployment)
394
394
  **1. Deploy Trinity Method:**
395
395
  ```bash
396
- npx @trinity-method/cli deploy --ci-deploy
396
+ npx trinity-method-sdk deploy --ci-deploy
397
397
  ```
398
398
 
399
399
  **2. Customize CI/CD (Ein):**
@@ -499,7 +499,7 @@ Trinity Method SDK can optionally configure linting tools during deployment.
499
499
 
500
500
  **To setup during deployment:**
501
501
  ```bash
502
- npx @trinity-method/cli deploy
502
+ npx trinity-method-sdk deploy
503
503
  # Select "Recommended" or "Custom" when prompted
504
504
  ```
505
505
 
package/dist/templates/shared/claude-commands/trinity-changelog.md.template CHANGED
@@ -44,6 +44,30 @@ The `/trinity-changelog` command invokes APO (Documentation Specialist) to manag
44
44
 
45
45
  ---
46
46
 
47
+ ## DOCUMENTATION RULES
48
+
49
+ **These rules apply to ALL documentation created by this command. NO EXCEPTIONS.**
50
+
51
+ ### Rule 1: No Self-Serving Trinity Documentation
52
+
53
+ **❌ FORBIDDEN:**
54
+ - Including information about Trinity Method in project documentation
55
+ - Explaining what Trinity Method is in README/docs
56
+ - Mentioning Trinity agents (APO, MON, ROR, KIL, BAS, etc.) in user-facing docs
57
+ - Documenting Trinity slash commands in project docs
58
+ - Adding Trinity Method badges, links, or references to project documentation
59
+ - Describing the Trinity Method SDK in project documentation
60
+
61
+ **✅ CORRECT:**
62
+ - Document the USER'S codebase exclusively
63
+ - Focus on the project's functionality, architecture, and usage
64
+ - Trinity Method is a development tool, not the subject of documentation
65
+ - The project documentation is about the project, not about how it was documented
66
+
67
+ **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.
68
+
69
+ ---
70
+
47
71
  ## When to Use `/trinity-changelog`
48
72
 
49
73
  ### Perfect Use Cases:
package/dist/templates/shared/claude-commands/trinity-docs.md.template CHANGED
@@ -56,6 +56,30 @@ The `/trinity-docs` command invokes APO (Documentation Specialist) to **create a
56
56
 
57
57
  ---
58
58
 
59
+ ## DOCUMENTATION RULES
60
+
61
+ **These rules apply to ALL documentation created by this command. NO EXCEPTIONS.**
62
+
63
+ ### Rule 1: No Self-Serving Trinity Documentation
64
+
65
+ **❌ FORBIDDEN:**
66
+ - Including information about Trinity Method in project documentation
67
+ - Explaining what Trinity Method is in README/docs
68
+ - Mentioning Trinity agents (APO, MON, ROR, KIL, BAS, etc.) in user-facing docs
69
+ - Documenting Trinity slash commands in project docs
70
+ - Adding Trinity Method badges, links, or references to project documentation
71
+ - Describing the Trinity Method SDK in project documentation
72
+
73
+ **✅ CORRECT:**
74
+ - Document the USER'S codebase exclusively
75
+ - Focus on the project's functionality, architecture, and usage
76
+ - Trinity Method is a development tool, not the subject of documentation
77
+ - The project documentation is about the project, not about how it was documented
78
+
79
+ **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.
80
+
81
+ ---
82
+
59
83
  ## When to Use `/trinity-docs`
60
84
 
61
85
  ### Perfect Use Cases:
@@ -440,6 +464,14 @@ for each file1 in all_md_files:
440
464
 
441
465
  **Goal:** Create hierarchical docs/ structure with seeded initial content
442
466
 
467
+ **🚨 CRITICAL EXECUTION REQUIREMENT:**
468
+
469
+ APO MUST use the **Write tool** to create documentation files in this phase.
470
+ - Creating directories is NOT enough
471
+ - Showing content templates is NOT enough
472
+ - APO MUST execute `Write("docs/guides/getting-started.md", content)` commands
473
+ - Minimum 4 files MUST be created: getting-started.md, api/README.md, architecture/overview.md, reference/README.md
474
+
443
475
  **Standard Directory Structure:**
444
476
 
445
477
  ```
@@ -479,8 +511,34 @@ for each dir in required_dirs:
479
511
 
480
512
  **CRITICAL: Create useful starter guides based on project type, not empty placeholders**
481
513
 
514
+ **✅ APO MUST:**
515
+ 1. USE Write tool to create docs/guides/getting-started.md with project-specific content
516
+ 2. USE Write tool to create framework-specific guides (if applicable)
517
+ 3. Content MUST be based on actual project metadata from Phase 1
518
+ 4. NO generic placeholders - use real project name, version, dependencies
519
+
520
+ **EXECUTION REQUIRED:**
521
+ ```javascript
522
+ // APO MUST execute these Write commands:
523
+
524
+ // 1. Create getting-started.md
525
+ Write("docs/guides/getting-started.md", getting_started_content);
526
+
527
+ // 2. Create framework-specific guide (if detected)
528
+ if (framework === "Express" || framework === "NestJS") {
529
+ Write("docs/guides/api-development.md", api_dev_content);
530
+ }
531
+ if (framework === "React" || framework === "Next.js") {
532
+ Write("docs/guides/component-development.md", component_dev_content);
533
+ }
534
+ if (framework === "Django" || framework === "Flask") {
535
+ Write("docs/guides/django-development.md", django_dev_content);
536
+ }
537
+ ```
538
+
539
+ **CONTENT TEMPLATE for docs/guides/getting-started.md:**
540
+
482
541
  ```markdown
483
- ### docs/guides/getting-started.md
484
542
 
485
543
  # Getting Started with {{PROJECT_NAME}}
486
544
 
@@ -663,8 +721,20 @@ python manage.py startapp myapp
663
721
 
664
722
  **Step 3: Seed docs/api/ Content (ENHANCEMENT 2 + 8)**
665
723
 
724
+ **✅ APO MUST:**
725
+ 1. USE Write tool to create docs/api/README.md
726
+ 2. Include links to auto-generated API docs if detected in Phase 1
727
+ 3. If no auto-generated docs, create basic API documentation structure
728
+
729
+ **EXECUTION REQUIRED:**
730
+ ```javascript
731
+ // APO MUST execute this Write command:
732
+ Write("docs/api/README.md", api_readme_content);
733
+ ```
734
+
735
+ **CONTENT TEMPLATE for docs/api/README.md:**
736
+
666
737
  ```markdown
667
- ### docs/api/README.md
668
738
 
669
739
  # API Documentation
670
740
 
@@ -729,8 +799,21 @@ Consider using tools like:
729
799
 
730
800
  **CRITICAL: Create real architecture documentation from codebase analysis**
731
801
 
802
+ **✅ APO MUST:**
803
+ 1. USE Write tool to create docs/architecture/overview.md
804
+ 2. Content MUST be auto-generated from Phase 1 codebase analysis
805
+ 3. Include actual directory structure, detected patterns, entry points
806
+ 4. NO generic templates - use real project metadata
807
+
808
+ **EXECUTION REQUIRED:**
809
+ ```javascript
810
+ // APO MUST execute this Write command:
811
+ Write("docs/architecture/overview.md", architecture_overview_content);
812
+ ```
813
+
814
+ **CONTENT TEMPLATE for docs/architecture/overview.md:**
815
+
732
816
  ```markdown
733
- ### docs/architecture/overview.md
734
817
 
735
818
  # Architecture Overview
736
819
 
@@ -864,8 +947,21 @@ For detailed API documentation, see [../api/](../api/).
864
947
 
865
948
  **Step 5: Seed docs/reference/ Content (ENHANCEMENT 2)**
866
949
 
950
+ **✅ APO MUST:**
951
+ 1. USE Write tool to create docs/reference/README.md
952
+ 2. Include actual CLI commands from package.json scripts
953
+ 3. Document environment variables if .env.example exists
954
+ 4. List configuration options if detected
955
+
956
+ **EXECUTION REQUIRED:**
957
+ ```javascript
958
+ // APO MUST execute this Write command:
959
+ Write("docs/reference/README.md", reference_readme_content);
960
+ ```
961
+
962
+ **CONTENT TEMPLATE for docs/reference/README.md:**
963
+
867
964
  ```markdown
868
- ### docs/reference/README.md
869
965
 
870
966
  # Reference Documentation
871
967
 
@@ -1028,6 +1124,23 @@ See [../README.md](../README.md) for complete documentation index.
1028
1124
  {Content from Step 5 - already seeded with CLI commands, env vars}
1029
1125
  ```
1030
1126
 
1127
+ **Phase 2 Execution Summary:**
1128
+
1129
+ **✅ MANDATORY FILE CREATIONS:**
1130
+
1131
+ APO MUST have executed Write tool for these files (minimum required):
1132
+ 1. ✅ docs/guides/getting-started.md
1133
+ 2. ✅ docs/api/README.md
1134
+ 3. ✅ docs/architecture/overview.md
1135
+ 4. ✅ docs/reference/README.md
1136
+
1137
+ **Optional (based on detected framework):**
1138
+ - docs/guides/{framework}-development.md (if Express/React/Django/etc detected)
1139
+
1140
+ **VERIFICATION:**
1141
+
1142
+ If APO did NOT create these files using Write tool, APO has FAILED Phase 2.
1143
+
1031
1144
  **APO Output:**
1032
1145
 
1033
1146
  ```markdown
@@ -1040,7 +1153,9 @@ See [../README.md](../README.md) for complete documentation index.
1040
1153
  - ✅ docs/reference/
1041
1154
  - ✅ docs/images/
1042
1155
 
1043
- **Content Seeded:** {count} files created
1156
+ **Files Created with Write Tool:** {count} files
1157
+
1158
+ **VERIFICATION - Files Created:**
1044
1159
 
1045
1160
  **Guides:**
1046
1161
  - ✅ docs/guides/getting-started.md ({line_count} lines)
package/dist/templates/shared/claude-commands/trinity-readme.md.template CHANGED
@@ -49,6 +49,30 @@ The `/trinity-readme` command invokes APO (Documentation Specialist) to manage R
49
49
 
50
50
  ---
51
51
 
52
+ ## DOCUMENTATION RULES
53
+
54
+ **These rules apply to ALL documentation created by this command. NO EXCEPTIONS.**
55
+
56
+ ### Rule 1: No Self-Serving Trinity Documentation
57
+
58
+ **❌ FORBIDDEN:**
59
+ - Including information about Trinity Method in project documentation
60
+ - Explaining what Trinity Method is in README/docs
61
+ - Mentioning Trinity agents (APO, MON, ROR, KIL, BAS, etc.) in user-facing docs
62
+ - Documenting Trinity slash commands in project docs
63
+ - Adding Trinity Method badges, links, or references to project documentation
64
+ - Describing the Trinity Method SDK in project documentation
65
+
66
+ **✅ CORRECT:**
67
+ - Document the USER'S codebase exclusively
68
+ - Focus on the project's functionality, architecture, and usage
69
+ - Trinity Method is a development tool, not the subject of documentation
70
+ - The project documentation is about the project, not about how it was documented
71
+
72
+ **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.
73
+
74
+ ---
75
+
52
76
  ## When to Use `/trinity-readme`
53
77
 
54
78
  ### Perfect Use Cases:
package/package.json CHANGED
@@ -1,94 +1,94 @@
1
- {
2
- "name": "trinity-method-sdk",
3
- "version": "2.0.0",
4
- "description": "Trinity Method SDK - Investigation-first development methodology for any project",
5
- "type": "module",
6
- "main": "dist/index.js",
7
- "types": "dist/index.d.ts",
8
- "files": [
9
- "dist/",
10
- "!dist/**/*.map",
11
- "README.md",
12
- "LICENSE",
13
- "CHANGELOG.md"
14
- ],
15
- "bin": {
16
- "trinity": "./dist/cli/index.js"
17
- },
18
- "scripts": {
19
- "clean": "rimraf dist",
20
- "prebuild": "npm run clean",
21
- "build": "tsc && npm run copy-templates",
22
- "copy-templates": "node -e \"const fs=require('fs-extra'); fs.copySync('src/templates', 'dist/templates');\"",
23
- "test": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js",
24
- "test:unit": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects unit",
25
- "test:integration": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects integration",
26
- "test:e2e": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects e2e --passWithNoTests",
27
- "test:performance": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects performance --passWithNoTests",
28
- "test:coverage": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --coverage",
29
- "test:watch": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --watch",
30
- "lint": "eslint src/ tests/",
31
- "lint:fix": "eslint src/ tests/ --fix",
32
- "format": "prettier --write src/ tests/",
33
- "format:check": "prettier --check src/ tests/",
34
- "type-check": "tsc --noEmit",
35
- "docs:generate": "typedoc --out docs src/",
36
- "pretest": "npm run type-check",
37
- "prepublishOnly": "npm run build && npm run test",
38
- "prepare": "husky"
39
- },
40
- "keywords": [
41
- "trinity-method",
42
- "development-methodology",
43
- "investigation-first",
44
- "ai-coding",
45
- "claude-code",
46
- "cursor",
47
- "copilot"
48
- ],
49
- "author": "Trinity Method",
50
- "license": "MIT",
51
- "devDependencies": {
52
- "@eslint/js": "^9.39.2",
53
- "@jest/globals": "^30.2.0",
54
- "@types/fs-extra": "^11.0.4",
55
- "@types/glob": "^8.1.0",
56
- "@types/inquirer": "^9.0.9",
57
- "@types/jest": "^30.0.0",
58
- "@types/node": "^25.0.3",
59
- "@typescript-eslint/eslint-plugin": "^8.50.0",
60
- "@typescript-eslint/parser": "^8.50.0",
61
- "eslint": "^9.39.2",
62
- "eslint-plugin-jest": "^29.5.0",
63
- "husky": "^9.1.7",
64
- "jest": "^30.2.0",
65
- "jest-mock": "^30.2.0",
66
- "lint-staged": "^16.2.7",
67
- "prettier": "^3.0.0",
68
- "rimraf": "^6.0.1",
69
- "ts-jest": "^29.1.0",
70
- "typedoc": "^0.28.15",
71
- "typescript": "^5.9.3"
72
- },
73
- "dependencies": {
74
- "chalk": "^5.3.0",
75
- "commander": "^14.0.2",
76
- "fs-extra": "^11.3.3",
77
- "glob": "^13.0.0",
78
- "inquirer": "^13.1.0",
79
- "ora": "^9.0.0"
80
- },
81
- "lint-staged": {
82
- "*.{ts,tsx}": [
83
- "eslint --fix",
84
- "prettier --write"
85
- ],
86
- "*.{js,jsx}": [
87
- "eslint --fix",
88
- "prettier --write"
89
- ],
90
- "*.{json,md,yml,yaml}": [
91
- "prettier --write"
92
- ]
93
- }
94
- }
1
+ {
2
+ "name": "trinity-method-sdk",
3
+ "version": "2.0.2",
4
+ "description": "Trinity Method SDK - Investigation-first development methodology for any project",
5
+ "type": "module",
6
+ "main": "dist/index.js",
7
+ "types": "dist/index.d.ts",
8
+ "files": [
9
+ "dist/",
10
+ "!dist/**/*.map",
11
+ "README.md",
12
+ "LICENSE",
13
+ "CHANGELOG.md"
14
+ ],
15
+ "bin": {
16
+ "trinity": "./dist/cli/index.js"
17
+ },
18
+ "scripts": {
19
+ "clean": "rimraf dist",
20
+ "prebuild": "npm run clean",
21
+ "build": "tsc && npm run copy-templates",
22
+ "copy-templates": "node -e \"const fs=require('fs-extra'); fs.copySync('src/templates', 'dist/templates');\"",
23
+ "test": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js",
24
+ "test:unit": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects unit",
25
+ "test:integration": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects integration",
26
+ "test:e2e": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects e2e --passWithNoTests",
27
+ "test:performance": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --selectProjects performance --passWithNoTests",
28
+ "test:coverage": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --coverage",
29
+ "test:watch": "node --experimental-vm-modules --no-warnings node_modules/jest/bin/jest.js --watch",
30
+ "lint": "eslint src/ tests/",
31
+ "lint:fix": "eslint src/ tests/ --fix",
32
+ "format": "prettier --write src/ tests/",
33
+ "format:check": "prettier --check src/ tests/",
34
+ "type-check": "tsc --noEmit",
35
+ "docs:generate": "typedoc --out docs src/",
36
+ "pretest": "npm run type-check",
37
+ "prepublishOnly": "npm run build && npm run test",
38
+ "prepare": "husky"
39
+ },
40
+ "keywords": [
41
+ "trinity-method",
42
+ "development-methodology",
43
+ "investigation-first",
44
+ "ai-coding",
45
+ "claude-code",
46
+ "cursor",
47
+ "copilot"
48
+ ],
49
+ "author": "Trinity Method",
50
+ "license": "MIT",
51
+ "devDependencies": {
52
+ "@eslint/js": "^9.39.2",
53
+ "@jest/globals": "^30.2.0",
54
+ "@types/fs-extra": "^11.0.4",
55
+ "@types/glob": "^8.1.0",
56
+ "@types/inquirer": "^9.0.9",
57
+ "@types/jest": "^30.0.0",
58
+ "@types/node": "^25.0.3",
59
+ "@typescript-eslint/eslint-plugin": "^8.50.0",
60
+ "@typescript-eslint/parser": "^8.50.0",
61
+ "eslint": "^9.39.2",
62
+ "eslint-plugin-jest": "^29.5.0",
63
+ "husky": "^9.1.7",
64
+ "jest": "^30.2.0",
65
+ "jest-mock": "^30.2.0",
66
+ "lint-staged": "^16.2.7",
67
+ "prettier": "^3.0.0",
68
+ "rimraf": "^6.0.1",
69
+ "ts-jest": "^29.1.0",
70
+ "typedoc": "^0.28.15",
71
+ "typescript": "^5.9.3"
72
+ },
73
+ "dependencies": {
74
+ "chalk": "^5.3.0",
75
+ "commander": "^14.0.2",
76
+ "fs-extra": "^11.3.3",
77
+ "glob": "^13.0.0",
78
+ "inquirer": "^13.1.0",
79
+ "ora": "^9.0.0"
80
+ },
81
+ "lint-staged": {
82
+ "*.{ts,tsx}": [
83
+ "eslint --fix",
84
+ "prettier --write"
85
+ ],
86
+ "*.{js,jsx}": [
87
+ "eslint --fix",
88
+ "prettier --write"
89
+ ],
90
+ "*.{json,md,yml,yaml}": [
91
+ "prettier --write"
92
+ ]
93
+ }
94
+ }