trinity-method-sdk 2.0.9 → 2.2.0
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.
- package/CHANGELOG.md +702 -267
- package/README.md +550 -540
- package/dist/cli/commands/deploy/agents.js +1 -1
- package/dist/cli/commands/deploy/ci-cd.d.ts +4 -3
- package/dist/cli/commands/deploy/ci-cd.js +10 -9
- package/dist/cli/commands/deploy/claude-setup.js +28 -35
- package/dist/cli/commands/deploy/configuration.js +10 -11
- package/dist/cli/commands/deploy/directories.js +13 -14
- package/dist/cli/commands/deploy/gitignore.js +3 -5
- package/dist/cli/commands/deploy/index.d.ts +1 -1
- package/dist/cli/commands/deploy/index.js +7 -3
- package/dist/cli/commands/deploy/knowledge-base.js +3 -3
- package/dist/cli/commands/deploy/pre-flight.js +1 -1
- package/dist/cli/commands/deploy/root-files.js +3 -18
- package/dist/cli/commands/deploy/sdk-install.js +1 -1
- package/dist/cli/commands/deploy/summary.js +3 -3
- package/dist/cli/commands/deploy/templates.js +33 -20
- package/dist/cli/commands/update/agents.js +1 -1
- package/dist/cli/commands/update/backup.js +6 -12
- package/dist/cli/commands/update/commands.d.ts +1 -0
- package/dist/cli/commands/update/commands.js +18 -45
- package/dist/cli/commands/update/knowledge-base.js +2 -2
- package/dist/cli/commands/update/pre-flight.js +11 -11
- package/dist/cli/commands/update/summary.js +5 -5
- package/dist/cli/commands/update/templates.js +35 -13
- package/dist/cli/commands/update/verification.js +5 -5
- package/dist/cli/commands/update/version.js +1 -1
- package/dist/cli/utils/deploy-ci.d.ts +3 -2
- package/dist/cli/utils/deploy-ci.js +24 -24
- package/dist/cli/utils/deploy-linting.js +101 -6
- package/dist/cli/utils/error-classes.d.ts +2 -2
- package/dist/cli/utils/linting-tools.js +14 -6
- package/dist/cli/utils/template-processor.js +2 -4
- package/dist/templates/{claude → .claude}/EMPLOYEE-DIRECTORY.md.template +16 -22
- package/dist/templates/{agents → .claude/agents}/aj-team/apo-documentation-specialist.md.template +10 -10
- package/dist/templates/{agents → .claude/agents}/aj-team/bas-quality-gate.md.template +13 -15
- package/dist/templates/{agents → .claude/agents}/aj-team/bon-dependency-manager.md.template +4 -4
- package/dist/templates/{agents → .claude/agents}/aj-team/cap-configuration-specialist.md.template +3 -3
- package/dist/templates/{agents → .claude/agents}/aj-team/dra-code-reviewer.md.template +8 -10
- package/dist/templates/{agents → .claude/agents}/aj-team/kil-task-executor.md.template +11 -13
- package/dist/templates/{agents → .claude/agents}/aj-team/uro-refactoring-specialist.md.template +3 -3
- package/dist/templates/{agents → .claude/agents}/audit/juno-auditor.md.template +46 -42
- package/dist/templates/{agents → .claude/agents}/deployment/ein-cicd.md.template +59 -164
- package/dist/templates/{agents → .claude/agents}/deployment/ino-context.md.template +25 -22
- package/dist/templates/{agents → .claude/agents}/deployment/tan-structure.md.template +32 -30
- package/dist/templates/{agents → .claude/agents}/deployment/zen-knowledge.md.template +28 -23
- package/dist/templates/{agents → .claude/agents}/leadership/aj-maestro.md.template +10 -6
- package/dist/templates/{agents → .claude/agents}/leadership/aly-cto.md.template +22 -19
- package/dist/templates/{agents → .claude/agents}/planning/eus-decomposer.md.template +8 -4
- package/dist/templates/{agents → .claude/agents}/planning/mon-requirements.md.template +8 -4
- package/dist/templates/{agents → .claude/agents}/planning/ror-design.md.template +8 -4
- package/dist/templates/{agents → .claude/agents}/planning/tra-planner.md.template +10 -4
- package/dist/templates/{shared/claude-commands → .claude/commands/execution}/trinity-audit.md.template +15 -15
- package/dist/templates/.claude/commands/execution/trinity-breakdown.md.template +535 -0
- package/dist/templates/{shared/claude-commands → .claude/commands/execution}/trinity-orchestrate.md.template +48 -48
- package/dist/templates/{shared/claude-commands → .claude/commands/infrastructure}/trinity-init.md.template +32 -54
- package/dist/templates/{shared/claude-commands → .claude/commands/investigation}/trinity-create-investigation.md.template +13 -7
- package/dist/templates/{shared/claude-commands → .claude/commands/investigation}/trinity-investigate-templates.md.template +19 -15
- package/dist/templates/{shared/claude-commands → .claude/commands/investigation}/trinity-plan-investigation.md.template +12 -6
- package/dist/templates/{shared/claude-commands → .claude/commands/maintenance}/trinity-changelog.md.template +9 -8
- package/dist/templates/.claude/commands/maintenance/trinity-docs-update.md.template +279 -0
- package/dist/templates/.claude/commands/maintenance/trinity-docs.md.template +2828 -0
- package/dist/templates/{shared/claude-commands → .claude/commands/maintenance}/trinity-readme.md.template +21 -20
- package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-decompose.md.template +6 -4
- package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-design.md.template +6 -4
- package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-plan.md.template +7 -5
- package/dist/templates/{shared/claude-commands → .claude/commands/planning}/trinity-requirements.md.template +6 -4
- package/dist/templates/{shared/claude-commands → .claude/commands/session}/trinity-continue.md.template +30 -24
- package/dist/templates/{shared/claude-commands → .claude/commands/session}/trinity-end.md.template +403 -397
- package/dist/templates/{shared/claude-commands → .claude/commands/session}/trinity-start.md.template +9 -4
- package/dist/templates/{shared/claude-commands → .claude/commands/utility}/trinity-agents.md.template +11 -8
- package/dist/templates/{shared/claude-commands → .claude/commands/utility}/trinity-verify.md.template +56 -57
- package/dist/templates/{shared/claude-commands → .claude/commands/utility}/trinity-workorder.md.template +13 -9
- package/dist/templates/ci/ci.yml.template +2 -2
- package/dist/templates/root/CLAUDE.md.template +9 -9
- package/dist/templates/root/linting/nodejs/.husky-pre-commit.template +5 -0
- package/dist/templates/source/base-CLAUDE.md.template +310 -310
- package/dist/templates/source/flutter-CLAUDE.md.template +593 -593
- package/dist/templates/source/nodejs-CLAUDE.md.template +531 -531
- package/dist/templates/source/python-CLAUDE.md.template +510 -510
- package/dist/templates/source/react-CLAUDE.md.template +513 -513
- package/dist/templates/source/rust-CLAUDE.md.template +653 -653
- package/dist/templates/trinity/CLAUDE.md.template +14 -14
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/AI-DEVELOPMENT-GUIDE.md.template +1 -1
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/ARCHITECTURE.md.template +5 -5
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/CODING-PRINCIPLES.md.template +1 -1
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/DOCUMENTATION-CRITERIA.md.template +1 -1
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/ISSUES.md.template +9 -9
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/TESTING-PRINCIPLES.md.template +1 -1
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/Technical-Debt.md.template +2 -4
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/To-do.md.template +2 -2
- package/dist/templates/{knowledge-base → trinity/knowledge-base}/Trinity.md.template +6 -6
- package/dist/templates/trinity/templates/documentation/api-docs/README.md.template +218 -0
- package/dist/templates/trinity/templates/documentation/configuration/documentation-structure.md.template +71 -0
- package/dist/templates/trinity/templates/documentation/configuration/env-example-generator.md.template +387 -0
- package/dist/templates/trinity/templates/documentation/discovery/api-endpoint-scanner.md.template +343 -0
- package/dist/templates/trinity/templates/documentation/discovery/component-discovery.md.template +254 -0
- package/dist/templates/trinity/templates/documentation/discovery/env-variable-extraction.md.template +316 -0
- package/dist/templates/trinity/templates/documentation/discovery/framework-detection.md.template +205 -0
- package/dist/templates/trinity/templates/documentation/guides/api-development.md.template +375 -0
- package/dist/templates/trinity/templates/documentation/guides/contributing.md.template +488 -0
- package/dist/templates/trinity/templates/documentation/guides/deployment.md.template +565 -0
- package/dist/templates/trinity/templates/documentation/guides/getting-started.md.template +118 -0
- package/dist/templates/trinity/templates/documentation/mermaid-diagrams/api-endpoint-map.md.template +56 -0
- package/dist/templates/trinity/templates/documentation/mermaid-diagrams/component-hierarchy.md.template +60 -0
- package/dist/templates/trinity/templates/documentation/mermaid-diagrams/database-er.md.template +49 -0
- package/dist/templates/trinity/templates/documentation/mermaid-diagrams/mvc-flow.md.template +41 -0
- package/dist/templates/trinity/templates/documentation/processes/error-handling-protocol.md.template +166 -0
- package/dist/templates/trinity/templates/documentation/processes/fallback-mechanism.md.template +88 -0
- package/dist/templates/trinity/templates/documentation/reports/apo-docs-update-checklist.md.template +343 -0
- package/dist/templates/trinity/templates/documentation/reports/juno-docs-update-checklist.md.template +1337 -0
- package/dist/templates/trinity/templates/documentation/reports/juno-final-report.md.template +237 -0
- package/dist/templates/trinity/templates/documentation/reports/juno-internal-report.md.template +461 -0
- package/dist/templates/trinity/templates/documentation/validation/documentation-verification-rules.md.template +379 -0
- package/dist/templates/trinity/templates/documentation/validation/juno-quality-gates.md.template +282 -0
- package/dist/templates/{investigations → trinity/templates/investigations}/bug.md.template +14 -14
- package/dist/templates/{investigations → trinity/templates/investigations}/feature.md.template +14 -14
- package/dist/templates/{investigations → trinity/templates/investigations}/performance.md.template +14 -14
- package/dist/templates/{investigations → trinity/templates/investigations}/security.md.template +14 -14
- package/dist/templates/{investigations → trinity/templates/investigations}/technical.md.template +14 -14
- package/dist/templates/{work-orders → trinity/templates/work-orders}/ANALYSIS-TEMPLATE.md.template +10 -13
- package/dist/templates/{work-orders → trinity/templates/work-orders}/AUDIT-TEMPLATE.md.template +10 -26
- package/dist/templates/{work-orders → trinity/templates/work-orders}/IMPLEMENTATION-TEMPLATE.md.template +10 -26
- package/dist/templates/{work-orders → trinity/templates/work-orders}/INVESTIGATION-TEMPLATE.md.template +10 -25
- package/dist/templates/{work-orders → trinity/templates/work-orders}/PATTERN-TEMPLATE.md.template +10 -26
- package/dist/templates/{work-orders → trinity/templates/work-orders}/VERIFICATION-TEMPLATE.md.template +10 -26
- package/package.json +99 -94
- package/dist/templates/agents/leadership/aj-cc.md.template +0 -462
- package/dist/templates/ci/cd.yml.template +0 -175
- package/dist/templates/ci/github-actions.yml +0 -86
- package/dist/templates/root/TRINITY.md.template +0 -52
- package/dist/templates/shared/claude-commands/trinity-docs.md.template +0 -2577
- /package/dist/templates/{linting → root/linting}/flutter/.pre-commit-config.yaml.template +0 -0
- /package/dist/templates/{linting → root/linting}/flutter/analysis_options.yaml.template +0 -0
- /package/dist/templates/{linting → root/linting}/nodejs/.eslintrc-commonjs.json.template +0 -0
- /package/dist/templates/{linting → root/linting}/nodejs/.eslintrc-esm.json.template +0 -0
- /package/dist/templates/{linting → root/linting}/nodejs/.eslintrc-typescript.json.template +0 -0
- /package/dist/templates/{linting → root/linting}/nodejs/.pre-commit-config.yaml.template +0 -0
- /package/dist/templates/{linting → root/linting}/nodejs/.prettierrc.json.template +0 -0
- /package/dist/templates/{linting → root/linting}/python/.flake8.template +0 -0
- /package/dist/templates/{linting → root/linting}/python/.pre-commit-config.yaml.template +0 -0
- /package/dist/templates/{linting → root/linting}/python/pyproject.toml.template +0 -0
- /package/dist/templates/{linting → root/linting}/rust/.pre-commit-config.yaml.template +0 -0
- /package/dist/templates/{linting → root/linting}/rust/clippy.toml.template +0 -0
- /package/dist/templates/{linting → root/linting}/rust/rustfmt.toml.template +0 -0
- /package/dist/templates/{documentation → trinity/templates/documentation}/ROOT-README.md.template +0 -0
- /package/dist/templates/{documentation → trinity/templates/documentation}/SUBDIRECTORY-README.md.template +0 -0
|
@@ -0,0 +1,279 @@
|
|
|
1
|
+
# Trinity Documentation Update
|
|
2
|
+
|
|
3
|
+
**Command:** `/maintenance:trinity-docs-update`
|
|
4
|
+
**Purpose:** Update existing documentation to reflect codebase changes
|
|
5
|
+
**Architecture:** JUNO Audit → 3 Parallel APOs → JUNO Verification
|
|
6
|
+
**Trinity Version:** 2.1.0
|
|
7
|
+
**Last Updated:** 2026-01-21
|
|
8
|
+
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
## CRITICAL: Autonomous Execution Mode
|
|
12
|
+
|
|
13
|
+
**This command runs in AUTONOMOUS mode from start to finish.**
|
|
14
|
+
|
|
15
|
+
**YOU (Claude Code orchestrator) MUST:**
|
|
16
|
+
- ✅ Execute all phases automatically (Phase 0 → 1 → 2 → 3 → Loop → Complete)
|
|
17
|
+
- ✅ Call JUNO to check completion after APOs return
|
|
18
|
+
- ✅ Re-launch incomplete APOs without asking
|
|
19
|
+
- ✅ Continue Phase 3 loop until 100% complete
|
|
20
|
+
- ✅ Only report to user when FINAL verification passes or fails
|
|
21
|
+
|
|
22
|
+
**YOU MUST NOT:**
|
|
23
|
+
- ❌ Stop and ask user "would you like me to continue?"
|
|
24
|
+
- ❌ Ask user to choose between options
|
|
25
|
+
- ❌ Present interim progress reports and wait for input
|
|
26
|
+
- ❌ Stop execution until command fully completes
|
|
27
|
+
|
|
28
|
+
**User interaction is ONLY required if:**
|
|
29
|
+
- Zero-tolerance policy violation found (abort case)
|
|
30
|
+
- Final verification FAILS and requires user decision
|
|
31
|
+
- Unrecoverable error occurs (e.g., cannot write files)
|
|
32
|
+
|
|
33
|
+
**Otherwise: Execute the full workflow autonomously without stopping.**
|
|
34
|
+
|
|
35
|
+
---
|
|
36
|
+
|
|
37
|
+
## Phase 0: Pre-Flight Check & State Initialization
|
|
38
|
+
|
|
39
|
+
### Step 0.1: Verify docs/ Directory Exists
|
|
40
|
+
|
|
41
|
+
```bash
|
|
42
|
+
if [ ! -d "docs/" ]; then
|
|
43
|
+
echo "❌ ABORT: docs/ directory not found"
|
|
44
|
+
echo ""
|
|
45
|
+
echo "This command updates EXISTING documentation."
|
|
46
|
+
echo "To generate NEW documentation, run:"
|
|
47
|
+
echo " /maintenance:trinity-docs"
|
|
48
|
+
exit 1
|
|
49
|
+
fi
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
**If docs/ does not exist:**
|
|
53
|
+
- **STOP IMMEDIATELY**
|
|
54
|
+
- Report to user that `/maintenance:trinity-docs` must be run first
|
|
55
|
+
- **DO NOT PROCEED** with any further steps
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## Phase 1: JUNO Comprehensive Audit
|
|
60
|
+
|
|
61
|
+
**Agent:** JUNO (Quality Auditor)
|
|
62
|
+
**Mode:** AUDIT + REPORT (Creates audit report file only)
|
|
63
|
+
**Output:** `.claude/trinity/reports/DOCS-UPDATE-AUDIT-{{DATE}}.md`
|
|
64
|
+
|
|
65
|
+
### Step 1.1: Execute JUNO Audit
|
|
66
|
+
|
|
67
|
+
1. **Read the audit checklist template:**
|
|
68
|
+
```
|
|
69
|
+
.claude/trinity/templates/documentation/reports/juno-docs-update-checklist.md
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
2. **Follow all instructions in the checklist** to perform the comprehensive audit
|
|
73
|
+
|
|
74
|
+
3. **Generate the audit report** with APO work assignments
|
|
75
|
+
|
|
76
|
+
4. **Save the report to:**
|
|
77
|
+
```
|
|
78
|
+
.claude/trinity/reports/DOCS-UPDATE-AUDIT-{{DATE}}.md
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
---
|
|
82
|
+
|
|
83
|
+
## Phase 2: APO Documentation Updates
|
|
84
|
+
|
|
85
|
+
**Agents:** APO-1, APO-2, APO-3 (parallel execution)
|
|
86
|
+
**Mode:** WRITE (Create/update documentation files)
|
|
87
|
+
**Output:** Updated/new documentation files in `docs/`
|
|
88
|
+
|
|
89
|
+
### Step 2.1: Launch Three APO Agents in Parallel
|
|
90
|
+
|
|
91
|
+
Use the Task tool to launch all three APO agents simultaneously:
|
|
92
|
+
|
|
93
|
+
1. **APO-1** - Base documentation updates
|
|
94
|
+
2. **APO-2** - Existing business logic documentation updates OR new documentation (first half)
|
|
95
|
+
3. **APO-3** - New business logic documentation (second half)
|
|
96
|
+
|
|
97
|
+
Each APO will:
|
|
98
|
+
1. Read the APO checklist template: `.claude/trinity/templates/documentation/reports/apo-docs-update-checklist.md`
|
|
99
|
+
2. Execute all instructions in the checklist
|
|
100
|
+
3. Complete their assigned work from JUNO's audit report
|
|
101
|
+
|
|
102
|
+
**CRITICAL: Launch all three APOs in a SINGLE message with three Task tool calls.**
|
|
103
|
+
|
|
104
|
+
### Step 2.2: Monitor APO Completion Status
|
|
105
|
+
|
|
106
|
+
**CRITICAL: After APOs return, you MUST check completion status before proceeding.**
|
|
107
|
+
|
|
108
|
+
**DO NOT:**
|
|
109
|
+
- ❌ Stop and ask user for guidance
|
|
110
|
+
- ❌ Present summary to user and wait
|
|
111
|
+
- ❌ Assume APOs are complete
|
|
112
|
+
- ❌ Skip to Phase 3 without checking
|
|
113
|
+
|
|
114
|
+
**YOU MUST:**
|
|
115
|
+
1. Wait for all three APO agents to return
|
|
116
|
+
2. Immediately proceed to Phase 3 Step 3.1 (JUNO verification)
|
|
117
|
+
3. Do NOT stop or ask user for input
|
|
118
|
+
|
|
119
|
+
**The workflow is automatic: Phase 2 → Phase 3 → Loop if needed → Complete**
|
|
120
|
+
|
|
121
|
+
---
|
|
122
|
+
|
|
123
|
+
## Phase 3: JUNO Verification Loop
|
|
124
|
+
|
|
125
|
+
**Agent:** JUNO (Quality Auditor)
|
|
126
|
+
**Mode:** VERIFICATION + REPORT (Creates verification report file)
|
|
127
|
+
**Output:** Verification report or restart Phase 2
|
|
128
|
+
|
|
129
|
+
### Step 3.1: JUNO Verifies APO Work Completion
|
|
130
|
+
|
|
131
|
+
**CRITICAL: You MUST call JUNO immediately after APOs return in Phase 2.**
|
|
132
|
+
|
|
133
|
+
**Instructions for launching JUNO:**
|
|
134
|
+
|
|
135
|
+
Use the Task tool to launch JUNO with this prompt:
|
|
136
|
+
|
|
137
|
+
"Execute JUNO Completion Verification for APO Checklists
|
|
138
|
+
|
|
139
|
+
**Mission:** Verify if all APO work is complete
|
|
140
|
+
|
|
141
|
+
**Instructions:**
|
|
142
|
+
|
|
143
|
+
1. Read all three APO checklists:
|
|
144
|
+
- .claude/trinity/reports/apo-1-docs-update-checklist.md
|
|
145
|
+
- .claude/trinity/reports/apo-2-docs-update-checklist.md
|
|
146
|
+
- .claude/trinity/reports/apo-3-docs-update-checklist.md
|
|
147
|
+
|
|
148
|
+
2. For each checklist, count:
|
|
149
|
+
- Total tasks assigned
|
|
150
|
+
- Tasks marked complete [x]
|
|
151
|
+
- Tasks still incomplete [ ]
|
|
152
|
+
|
|
153
|
+
3. Calculate completion percentage for each APO
|
|
154
|
+
|
|
155
|
+
4. Report results in this format:
|
|
156
|
+
- APO-1: X/Y tasks complete (Z%)
|
|
157
|
+
- APO-2: X/Y tasks complete (Z%)
|
|
158
|
+
- APO-3: X/Y tasks complete (Z%)
|
|
159
|
+
|
|
160
|
+
5. Determine next action:
|
|
161
|
+
- If ALL APOs = 100%: Report 'PROCEED TO STEP 3.2'
|
|
162
|
+
- If ANY APO < 100%: Report 'RESTART PHASE 2' with list of incomplete APOs
|
|
163
|
+
|
|
164
|
+
**Output Required:**
|
|
165
|
+
- Completion status for each APO
|
|
166
|
+
- Next action (PROCEED or RESTART)
|
|
167
|
+
- List of incomplete APOs (if any)"
|
|
168
|
+
|
|
169
|
+
**After JUNO reports:**
|
|
170
|
+
|
|
171
|
+
- **If JUNO says "PROCEED TO STEP 3.2"** → Continue to Step 3.2 below
|
|
172
|
+
- **If JUNO says "RESTART PHASE 2"** → Go to Step 3.1A (Restart Incomplete APOs)
|
|
173
|
+
|
|
174
|
+
### Step 3.1A: Restart Incomplete APOs
|
|
175
|
+
|
|
176
|
+
**CRITICAL: If any APO reported < 100%, you MUST restart them.**
|
|
177
|
+
|
|
178
|
+
**Instructions:**
|
|
179
|
+
|
|
180
|
+
1. Identify which APOs are incomplete from JUNO's report
|
|
181
|
+
|
|
182
|
+
2. Re-launch ONLY the incomplete APOs using the Task tool
|
|
183
|
+
|
|
184
|
+
3. Use this prompt for each incomplete APO:
|
|
185
|
+
|
|
186
|
+
"Continue Your Remaining Documentation Work
|
|
187
|
+
|
|
188
|
+
**Agent ID:** APO-{{DESIGNATION}}
|
|
189
|
+
|
|
190
|
+
**Instructions:**
|
|
191
|
+
|
|
192
|
+
1. Read your personal checklist:
|
|
193
|
+
- .claude/trinity/reports/apo-{{DESIGNATION}}-docs-update-checklist.md
|
|
194
|
+
|
|
195
|
+
2. Find the FIRST task marked [ ] (unchecked)
|
|
196
|
+
|
|
197
|
+
3. Continue working from that task onward
|
|
198
|
+
|
|
199
|
+
4. Follow the same workflow:
|
|
200
|
+
- Complete task
|
|
201
|
+
- Mark as [x]
|
|
202
|
+
- Save checklist
|
|
203
|
+
- Move to next task
|
|
204
|
+
|
|
205
|
+
5. DO NOT ask for guidance - continue until you reach your stopping point
|
|
206
|
+
|
|
207
|
+
**You are resuming work, not starting over. Pick up where you left off.**"
|
|
208
|
+
|
|
209
|
+
4. Wait for incomplete APOs to return
|
|
210
|
+
|
|
211
|
+
5. **Repeat Step 3.1** (call JUNO again to verify completion)
|
|
212
|
+
|
|
213
|
+
6. **Continue this loop until JUNO reports all APOs at 100%**
|
|
214
|
+
|
|
215
|
+
### Step 3.2: JUNO Audits Documentation Quality
|
|
216
|
+
|
|
217
|
+
**CRITICAL: Only reach this step when ALL APOs are 100% complete.**
|
|
218
|
+
|
|
219
|
+
Use the Task tool to launch JUNO with this prompt:
|
|
220
|
+
|
|
221
|
+
"Execute JUNO Final Quality Audit
|
|
222
|
+
|
|
223
|
+
**Mission:** Verify documentation quality and accuracy
|
|
224
|
+
|
|
225
|
+
**Instructions:**
|
|
226
|
+
|
|
227
|
+
1. Read JUNO's original audit report:
|
|
228
|
+
- .claude/trinity/reports/DOCS-UPDATE-AUDIT-{{DATE}}.md
|
|
229
|
+
|
|
230
|
+
2. For each item that was assigned to APOs, verify:
|
|
231
|
+
- File was created/updated (check file exists)
|
|
232
|
+
- Content matches requirements
|
|
233
|
+
- No hallucinated components
|
|
234
|
+
- Code examples are valid
|
|
235
|
+
|
|
236
|
+
3. Perform accuracy checks:
|
|
237
|
+
- Read source code files
|
|
238
|
+
- Compare against documentation
|
|
239
|
+
- Verify method signatures, parameters, types
|
|
240
|
+
- Check for outdated information
|
|
241
|
+
|
|
242
|
+
4. Generate verification report:
|
|
243
|
+
- Save to: .claude/trinity/reports/DOCS-UPDATE-VERIFICATION-{{DATE}}.md
|
|
244
|
+
- Include: Coverage percentage, accuracy percentage, issues found
|
|
245
|
+
|
|
246
|
+
5. Determine final status:
|
|
247
|
+
- If 100% coverage + 100% accuracy: Report 'VERIFICATION PASSED'
|
|
248
|
+
- If any issues: Report 'VERIFICATION FAILED' with issue list
|
|
249
|
+
|
|
250
|
+
**Output Required:**
|
|
251
|
+
- Coverage percentage
|
|
252
|
+
- Accuracy percentage
|
|
253
|
+
- Final status (PASSED or FAILED)
|
|
254
|
+
- Path to verification report"
|
|
255
|
+
|
|
256
|
+
**After JUNO reports:**
|
|
257
|
+
|
|
258
|
+
- **If verification PASSED:** Documentation update complete ✅ - Report to user
|
|
259
|
+
- **If verification FAILED:** Go to Step 3.2A (Fix Issues)
|
|
260
|
+
|
|
261
|
+
### Step 3.2A: Fix Documentation Issues
|
|
262
|
+
|
|
263
|
+
**If JUNO reports verification failed:**
|
|
264
|
+
|
|
265
|
+
1. Read JUNO's verification report to see issues
|
|
266
|
+
|
|
267
|
+
2. Identify which APO(s) need to fix issues
|
|
268
|
+
|
|
269
|
+
3. Re-launch affected APOs with specific fix instructions
|
|
270
|
+
|
|
271
|
+
4. Return to Step 3.2 (quality audit)
|
|
272
|
+
|
|
273
|
+
5. Continue loop until verification passes
|
|
274
|
+
|
|
275
|
+
---
|
|
276
|
+
|
|
277
|
+
**End of Phase 3**
|
|
278
|
+
|
|
279
|
+
---
|