telos-framework 0.1.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/LICENSE +21 -0
- package/README.md +245 -0
- package/USAGE.md +337 -0
- package/bin/telos-cli.js +41 -0
- package/lib/commands/init.js +112 -0
- package/lib/commands/rediscover.js +48 -0
- package/lib/commands/status.js +77 -0
- package/lib/commands/validate.js +148 -0
- package/lib/discovery/code-scanner.js +129 -0
- package/lib/discovery/hierarchy-builder.js +147 -0
- package/lib/discovery/mcp-discovery.js +90 -0
- package/lib/discovery/telos-discovery.js +69 -0
- package/lib/discovery/tool-mapper.js +151 -0
- package/lib/generators/agent-generator.js +374 -0
- package/lib/generators/agents-md-generator.js +73 -0
- package/lib/generators/all-agents-generator.js +196 -0
- package/lib/generators/logos-md-generator.js +192 -0
- package/lib/generators/telos-md-generator.js +121 -0
- package/lib/generators/tools-md-generator.js +204 -0
- package/lib/integration/capability-abstraction.js +162 -0
- package/lib/integration/graceful-degradation.js +152 -0
- package/lib/integration/mcp-client.js +109 -0
- package/lib/integration/tool-config-writers.js +142 -0
- package/lib/integration/tool-invoker.js +166 -0
- package/lib/platform/platform-detector.js +74 -0
- package/lib/platform/symlink-creator.js +103 -0
- package/lib/spec/spec-formatter.js +79 -0
- package/lib/spec/spec-translator.js +150 -0
- package/lib/spec/validation-cascade.js +156 -0
- package/logos/orchestrator.js +139 -0
- package/logos/state-manager.js +137 -0
- package/package.json +59 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 Telos Contributors
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
ADDED
|
@@ -0,0 +1,245 @@
|
|
|
1
|
+
# Telos: Purpose-Driven Multi-Agent Development Framework
|
|
2
|
+
|
|
3
|
+
A philosophically-grounded AI collective that embeds Aristotelian purpose
|
|
4
|
+
hierarchy into software development. Every line of code serves your ultimate
|
|
5
|
+
mission.
|
|
6
|
+
|
|
7
|
+
## Philosophy
|
|
8
|
+
|
|
9
|
+
**Telos** (Greek: τέλος) means "end," "purpose," or "goal"—the ultimate reason
|
|
10
|
+
something exists.
|
|
11
|
+
|
|
12
|
+
**Logos** (Greek: λόγος) means "reason," "discourse," or "rational
|
|
13
|
+
principle"—the organizing intelligence that maintains coherent order.
|
|
14
|
+
|
|
15
|
+
Most development tools focus on _how_ to code. Telos ensures you're building the
|
|
16
|
+
_right_ thing by maintaining alignment between implementation and purpose across
|
|
17
|
+
nine levels of abstraction—from syntax to transcendent meaning.
|
|
18
|
+
|
|
19
|
+
Based on Kenneth Boulding's hierarchy of system complexity, Telos orchestrates
|
|
20
|
+
specialized AI agents that operate coherently from low-level linting to
|
|
21
|
+
strategic vision. The **Logos orchestrator** uses rational discourse to maintain
|
|
22
|
+
top-down purpose alignment and bottom-up validation.
|
|
23
|
+
|
|
24
|
+
## Architecture
|
|
25
|
+
|
|
26
|
+
### The Nine Levels
|
|
27
|
+
|
|
28
|
+
```
|
|
29
|
+
L9: Telos-Guardian → Strategic alignment with ultimate purpose
|
|
30
|
+
L8: Market-Analyst → Business metrics and KPIs
|
|
31
|
+
L7: Insight-Synthesizer → User feedback and behavioral analytics
|
|
32
|
+
L6: UX-Simulator → User experience and accessibility
|
|
33
|
+
L5: Journey-Validator → End-to-end workflows and integration
|
|
34
|
+
L4: Integration-Contractor → API contracts and service boundaries
|
|
35
|
+
L3: Component-Architect → Component design and composition
|
|
36
|
+
L2: Function-Author → Unit logic and TDD
|
|
37
|
+
L1: Syntax-Linter → Code structure and formatting
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
### Logos Orchestrator
|
|
41
|
+
|
|
42
|
+
The central orchestration engine implementing:
|
|
43
|
+
|
|
44
|
+
- **Top-down decomposition**: Strategic goals cascade into tactical specs
|
|
45
|
+
- **Bottom-up validation**: Implementation validates against purpose
|
|
46
|
+
- **Middle-out reconciliation**: Conflicts resolved through rational dialogue
|
|
47
|
+
- **Spec-driven workflow**: All changes flow through OpenSpec proposals
|
|
48
|
+
|
|
49
|
+
## Installation
|
|
50
|
+
|
|
51
|
+
```bash
|
|
52
|
+
npx telos-framework init
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
Or install globally:
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
npm install -g telos-framework
|
|
59
|
+
telos init
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
## Quick Start
|
|
63
|
+
|
|
64
|
+
### 1. Initialize Your Project
|
|
65
|
+
|
|
66
|
+
```bash
|
|
67
|
+
cd your-project
|
|
68
|
+
telos init
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
The interactive initialization will:
|
|
72
|
+
|
|
73
|
+
- Capture your project's ultimate purpose (Telos)
|
|
74
|
+
- Decompose it into a 9-level hierarchy
|
|
75
|
+
- Discover available tools and MCP servers
|
|
76
|
+
- Generate adapted agent definitions
|
|
77
|
+
- Create platform-specific configurations
|
|
78
|
+
|
|
79
|
+
### 2. Start Development
|
|
80
|
+
|
|
81
|
+
Your AI assistants now operate as a coherent multi-agent collective:
|
|
82
|
+
|
|
83
|
+
```
|
|
84
|
+
User: "Add user authentication"
|
|
85
|
+
↓
|
|
86
|
+
L9 Telos-Guardian: Validates alignment with project purpose
|
|
87
|
+
↓
|
|
88
|
+
L8 Market-Analyst: Defines success metrics
|
|
89
|
+
↓
|
|
90
|
+
... (decomposition cascade)
|
|
91
|
+
↓
|
|
92
|
+
L2 Function-Author: Implements with TDD
|
|
93
|
+
↓
|
|
94
|
+
L1 Syntax-Linter: Ensures code quality
|
|
95
|
+
↓
|
|
96
|
+
(Bottom-up validation confirms alignment)
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### 3. Validate Alignment
|
|
100
|
+
|
|
101
|
+
```bash
|
|
102
|
+
telos validate
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
Check that all work traces back to your ultimate Telos.
|
|
106
|
+
|
|
107
|
+
## Features
|
|
108
|
+
|
|
109
|
+
### Adaptive Tool Integration
|
|
110
|
+
|
|
111
|
+
Telos discovers and integrates your existing tools:
|
|
112
|
+
|
|
113
|
+
- Linters (ESLint, Ruff, etc.)
|
|
114
|
+
- Test frameworks (Vitest, Jest, Playwright)
|
|
115
|
+
- Analytics (PostHog, Amplitude)
|
|
116
|
+
- MCP servers
|
|
117
|
+
- Custom tooling
|
|
118
|
+
|
|
119
|
+
### Multi-Platform Support
|
|
120
|
+
|
|
121
|
+
Works with:
|
|
122
|
+
|
|
123
|
+
- Claude (Code, Projects)
|
|
124
|
+
- Cursor
|
|
125
|
+
- GitHub Copilot
|
|
126
|
+
- Google Gemini
|
|
127
|
+
- Any AI coding assistant
|
|
128
|
+
|
|
129
|
+
Single source of truth with platform-specific symlinks—no duplication.
|
|
130
|
+
|
|
131
|
+
### OpenSpec Integration
|
|
132
|
+
|
|
133
|
+
Full integration with [OpenSpec](https://openspec.dev) workflow:
|
|
134
|
+
|
|
135
|
+
- Logos creates proposals for changes
|
|
136
|
+
- Agents work through specs and tasks
|
|
137
|
+
- Validation uses OpenSpec archive
|
|
138
|
+
- Telos lineage tracked throughout
|
|
139
|
+
|
|
140
|
+
### Technical Agent Delegation
|
|
141
|
+
|
|
142
|
+
9-level agents can delegate to specialized technical agents from
|
|
143
|
+
[Claude Collective](https://github.com/alan-colver/claude-code-collective):
|
|
144
|
+
|
|
145
|
+
- `research-agent` for technical investigation
|
|
146
|
+
- `quality-agent` for comprehensive reviews
|
|
147
|
+
- `testing-implementation-agent` for test suites
|
|
148
|
+
- `devops-agent` for deployment
|
|
149
|
+
- And more specialized agents
|
|
150
|
+
|
|
151
|
+
## Commands
|
|
152
|
+
|
|
153
|
+
```bash
|
|
154
|
+
telos init # Initialize Telos in your project
|
|
155
|
+
telos status # Show current configuration
|
|
156
|
+
telos rediscover # Update tool detection
|
|
157
|
+
telos validate # Check Telos alignment
|
|
158
|
+
telos --help # Show all commands
|
|
159
|
+
```
|
|
160
|
+
|
|
161
|
+
## Project Structure
|
|
162
|
+
|
|
163
|
+
After initialization:
|
|
164
|
+
|
|
165
|
+
```
|
|
166
|
+
your-project/
|
|
167
|
+
├── telos/
|
|
168
|
+
│ ├── content/
|
|
169
|
+
│ │ ├── TELOS.md # Your project's purpose hierarchy
|
|
170
|
+
│ │ ├── AGENTS.md # Consolidated agent definitions
|
|
171
|
+
│ │ ├── LOGOS.md # Orchestrator instructions
|
|
172
|
+
│ │ └── TOOLS.md # Tool registry and mappings
|
|
173
|
+
│ ├── agents/ # Individual agent definitions (L1-L9)
|
|
174
|
+
│ └── templates/ # Platform-specific configs
|
|
175
|
+
├── .telos/ # Runtime state (gitignored)
|
|
176
|
+
├── TELOS.md # Symlink for visibility
|
|
177
|
+
└── [platform symlinks] # CLAUDE.md, .cursor/rules/, etc.
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
## Philosophy & Theory
|
|
181
|
+
|
|
182
|
+
### Why Hierarchical Agents?
|
|
183
|
+
|
|
184
|
+
Flat agent collectives lack governance—agents can work at cross-purposes.
|
|
185
|
+
Hierarchical organization with clear level boundaries ensures:
|
|
186
|
+
|
|
187
|
+
- Strategic coherence (top-down)
|
|
188
|
+
- Implementation integrity (bottom-up)
|
|
189
|
+
- Efficient specialization (right tool, right level)
|
|
190
|
+
|
|
191
|
+
### Why Telos?
|
|
192
|
+
|
|
193
|
+
Without explicit purpose capture, AI assistants optimize for immediate requests,
|
|
194
|
+
not ultimate goals. Telos makes purpose explicit and traceable, enabling:
|
|
195
|
+
|
|
196
|
+
- Alignment validation at every level
|
|
197
|
+
- Conflict resolution through purpose appeal
|
|
198
|
+
- Emergent strategic consistency
|
|
199
|
+
|
|
200
|
+
### Why Logos?
|
|
201
|
+
|
|
202
|
+
Unstructured agent communication devolves into noise. Logos enforces rational
|
|
203
|
+
discourse through:
|
|
204
|
+
|
|
205
|
+
- Spec-driven dialogue (OpenSpec format)
|
|
206
|
+
- Structured reporting protocols
|
|
207
|
+
- Level-appropriate context filtering
|
|
208
|
+
|
|
209
|
+
## Examples
|
|
210
|
+
|
|
211
|
+
See `/examples` for:
|
|
212
|
+
|
|
213
|
+
- Simple web app initialization
|
|
214
|
+
- Existing codebase integration
|
|
215
|
+
- Multi-platform usage demonstration
|
|
216
|
+
|
|
217
|
+
## Contributing
|
|
218
|
+
|
|
219
|
+
See [CONTRIBUTING.md](CONTRIBUTING.md) for how to contribute to this project.
|
|
220
|
+
|
|
221
|
+
## Philosophy Deep Dive
|
|
222
|
+
|
|
223
|
+
See [PHILOSOPHY.md](PHILOSOPHY.md) for comprehensive explanation of:
|
|
224
|
+
|
|
225
|
+
- Aristotelian teleology in software
|
|
226
|
+
- Boulding's hierarchy applied to development
|
|
227
|
+
- Logos as rational agent orchestration
|
|
228
|
+
- Ontological levels and emergence
|
|
229
|
+
|
|
230
|
+
## Troubleshooting
|
|
231
|
+
|
|
232
|
+
See [TROUBLESHOOTING.md](TROUBLESHOOTING.md) for common issues and solutions.
|
|
233
|
+
|
|
234
|
+
## License
|
|
235
|
+
|
|
236
|
+
MIT License - see [LICENSE](LICENSE)
|
|
237
|
+
|
|
238
|
+
---
|
|
239
|
+
|
|
240
|
+
**Transform AI-assisted development from reactive tool usage to coherent,
|
|
241
|
+
purpose-aligned creation.**
|
|
242
|
+
|
|
243
|
+
[GitHub Repository](https://github.com/telos-framework/telos) |
|
|
244
|
+
[Documentation](https://telos-framework.dev) |
|
|
245
|
+
[Report Issues](https://github.com/telos-framework/telos/issues)
|
package/USAGE.md
ADDED
|
@@ -0,0 +1,337 @@
|
|
|
1
|
+
# Telos CLI Usage Guide
|
|
2
|
+
|
|
3
|
+
## Commands
|
|
4
|
+
|
|
5
|
+
### `telos init`
|
|
6
|
+
|
|
7
|
+
Initialize Telos in your project with interactive discovery.
|
|
8
|
+
|
|
9
|
+
```bash
|
|
10
|
+
telos init [options]
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
**Options:**
|
|
14
|
+
|
|
15
|
+
- `-q, --quick` - Quick initialization with sensible defaults (skips interactive
|
|
16
|
+
prompts)
|
|
17
|
+
- `-v, --verbose` - Show detailed output during initialization
|
|
18
|
+
|
|
19
|
+
**What it does:**
|
|
20
|
+
|
|
21
|
+
1. **Phase 1: Telos Discovery** - Interactive questions to capture your
|
|
22
|
+
project's ultimate purpose
|
|
23
|
+
2. **Phase 2: Project Scan** - Detects languages, frameworks, and existing code
|
|
24
|
+
3. **Phase 3: Tool Discovery** - Finds available MCP servers and development
|
|
25
|
+
tools
|
|
26
|
+
4. **Phase 4: Agent Generation** - Creates 9 specialized agents adapted to your
|
|
27
|
+
tools
|
|
28
|
+
5. **Phase 5: Platform Setup** - Configures symlinks for your AI platform
|
|
29
|
+
(Claude, Cursor, etc.)
|
|
30
|
+
|
|
31
|
+
**Example:**
|
|
32
|
+
|
|
33
|
+
```bash
|
|
34
|
+
# Interactive initialization
|
|
35
|
+
telos init
|
|
36
|
+
|
|
37
|
+
# Quick start with defaults
|
|
38
|
+
telos init --quick
|
|
39
|
+
|
|
40
|
+
# Verbose output
|
|
41
|
+
telos init --verbose
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
---
|
|
45
|
+
|
|
46
|
+
### `telos status`
|
|
47
|
+
|
|
48
|
+
Show current Telos configuration and initialization status.
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
telos status [options]
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
**Options:**
|
|
55
|
+
|
|
56
|
+
- `-v, --verbose` - Show detailed configuration including Telos hierarchy
|
|
57
|
+
preview
|
|
58
|
+
|
|
59
|
+
**What it shows:**
|
|
60
|
+
|
|
61
|
+
- Initialization status
|
|
62
|
+
- Number of agents configured
|
|
63
|
+
- Number of tools discovered
|
|
64
|
+
- Platform configuration
|
|
65
|
+
- Initialization timestamp
|
|
66
|
+
|
|
67
|
+
**Example:**
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
# Basic status
|
|
71
|
+
telos status
|
|
72
|
+
|
|
73
|
+
# Detailed status with Telos preview
|
|
74
|
+
telos status --verbose
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
### `telos rediscover`
|
|
80
|
+
|
|
81
|
+
Re-run tool discovery and update agent configurations.
|
|
82
|
+
|
|
83
|
+
Use this command after:
|
|
84
|
+
|
|
85
|
+
- Installing new development tools
|
|
86
|
+
- Adding new MCP servers
|
|
87
|
+
- Changing project dependencies
|
|
88
|
+
|
|
89
|
+
```bash
|
|
90
|
+
telos rediscover [options]
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
**Options:**
|
|
94
|
+
|
|
95
|
+
- `-v, --verbose` - Show detailed discovery output
|
|
96
|
+
|
|
97
|
+
**What it does:**
|
|
98
|
+
|
|
99
|
+
1. Re-scans project for languages and frameworks
|
|
100
|
+
2. Re-discovers MCP servers
|
|
101
|
+
3. Updates tool mappings
|
|
102
|
+
4. Regenerates TOOLS.md
|
|
103
|
+
5. Updates agent configurations with new tools
|
|
104
|
+
|
|
105
|
+
**Example:**
|
|
106
|
+
|
|
107
|
+
```bash
|
|
108
|
+
# Rediscover tools
|
|
109
|
+
telos rediscover
|
|
110
|
+
|
|
111
|
+
# Verbose rediscovery
|
|
112
|
+
telos rediscover --verbose
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
---
|
|
116
|
+
|
|
117
|
+
### `telos validate`
|
|
118
|
+
|
|
119
|
+
Validate Telos alignment across the project.
|
|
120
|
+
|
|
121
|
+
```bash
|
|
122
|
+
telos validate [options]
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
**Options:**
|
|
126
|
+
|
|
127
|
+
- `-v, --verbose` - Show detailed validation results
|
|
128
|
+
|
|
129
|
+
**What it validates:**
|
|
130
|
+
|
|
131
|
+
- Telos hierarchy structure (L9 → L1)
|
|
132
|
+
- Agent definitions (all 9 agents present)
|
|
133
|
+
- Tool configuration (TOOLS.md exists)
|
|
134
|
+
- Platform setup (AGENTS.md and symlinks)
|
|
135
|
+
|
|
136
|
+
**Example:**
|
|
137
|
+
|
|
138
|
+
```bash
|
|
139
|
+
# Run validation
|
|
140
|
+
telos validate
|
|
141
|
+
|
|
142
|
+
# Detailed validation
|
|
143
|
+
telos validate --verbose
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
**Exit codes:**
|
|
147
|
+
|
|
148
|
+
- `0` - All validations passed
|
|
149
|
+
- `1` - One or more validations failed
|
|
150
|
+
|
|
151
|
+
---
|
|
152
|
+
|
|
153
|
+
## Typical Workflows
|
|
154
|
+
|
|
155
|
+
### First-Time Setup
|
|
156
|
+
|
|
157
|
+
```bash
|
|
158
|
+
# Clone telos into your project
|
|
159
|
+
cd your-project
|
|
160
|
+
git clone https://github.com/yourusername/telos.git .telos-framework
|
|
161
|
+
cd .telos-framework
|
|
162
|
+
|
|
163
|
+
# Initialize with interactive discovery
|
|
164
|
+
npm install
|
|
165
|
+
npm link
|
|
166
|
+
cd ..
|
|
167
|
+
telos init
|
|
168
|
+
|
|
169
|
+
# Check status
|
|
170
|
+
telos status
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
### Quick Setup (Existing Project)
|
|
174
|
+
|
|
175
|
+
```bash
|
|
176
|
+
cd your-project
|
|
177
|
+
telos init --quick
|
|
178
|
+
telos validate
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
### Adding New Tools
|
|
182
|
+
|
|
183
|
+
```bash
|
|
184
|
+
# Install new tool (e.g., Playwright)
|
|
185
|
+
npm install -D @playwright/test
|
|
186
|
+
|
|
187
|
+
# Rediscover tools
|
|
188
|
+
telos rediscover
|
|
189
|
+
|
|
190
|
+
# Verify update
|
|
191
|
+
telos status
|
|
192
|
+
```
|
|
193
|
+
|
|
194
|
+
### Continuous Validation
|
|
195
|
+
|
|
196
|
+
```bash
|
|
197
|
+
# Add to your CI/CD pipeline
|
|
198
|
+
telos validate || exit 1
|
|
199
|
+
```
|
|
200
|
+
|
|
201
|
+
---
|
|
202
|
+
|
|
203
|
+
## Configuration Files
|
|
204
|
+
|
|
205
|
+
After initialization, Telos creates:
|
|
206
|
+
|
|
207
|
+
```
|
|
208
|
+
your-project/
|
|
209
|
+
├── .telos/
|
|
210
|
+
│ ├── config.json # Runtime configuration
|
|
211
|
+
│ └── state.json # Orchestrator state
|
|
212
|
+
├── telos/
|
|
213
|
+
│ ├── content/
|
|
214
|
+
│ │ ├── TELOS.md # Purpose hierarchy
|
|
215
|
+
│ │ ├── AGENTS.md # Consolidated agents
|
|
216
|
+
│ │ ├── LOGOS.md # Orchestrator docs
|
|
217
|
+
│ │ └── TOOLS.md # Tool inventory
|
|
218
|
+
│ └── agents/
|
|
219
|
+
│ ├── l1-syntax-linter.md
|
|
220
|
+
│ ├── l2-function-author.md
|
|
221
|
+
│ └── ... (9 total)
|
|
222
|
+
└── TELOS.md # Symlink to telos/content/TELOS.md
|
|
223
|
+
```
|
|
224
|
+
|
|
225
|
+
---
|
|
226
|
+
|
|
227
|
+
## Getting Help
|
|
228
|
+
|
|
229
|
+
```bash
|
|
230
|
+
# Show all commands
|
|
231
|
+
telos --help
|
|
232
|
+
|
|
233
|
+
# Show command-specific help
|
|
234
|
+
telos init --help
|
|
235
|
+
telos status --help
|
|
236
|
+
telos rediscover --help
|
|
237
|
+
telos validate --help
|
|
238
|
+
```
|
|
239
|
+
|
|
240
|
+
---
|
|
241
|
+
|
|
242
|
+
## Troubleshooting
|
|
243
|
+
|
|
244
|
+
### Telos Not Initialized
|
|
245
|
+
|
|
246
|
+
**Error:** `✗ Telos not initialized`
|
|
247
|
+
|
|
248
|
+
**Solution:**
|
|
249
|
+
|
|
250
|
+
```bash
|
|
251
|
+
telos init
|
|
252
|
+
```
|
|
253
|
+
|
|
254
|
+
### Tool Discovery Issues
|
|
255
|
+
|
|
256
|
+
**Error:** Tools not being detected
|
|
257
|
+
|
|
258
|
+
**Solution:**
|
|
259
|
+
|
|
260
|
+
```bash
|
|
261
|
+
# Ensure package.json exists
|
|
262
|
+
# Install tools via package manager
|
|
263
|
+
npm install -D eslint vitest
|
|
264
|
+
|
|
265
|
+
# Rediscover
|
|
266
|
+
telos rediscover
|
|
267
|
+
```
|
|
268
|
+
|
|
269
|
+
### Validation Failures
|
|
270
|
+
|
|
271
|
+
**Error:** `✗ Agent Definitions`
|
|
272
|
+
|
|
273
|
+
**Solution:**
|
|
274
|
+
|
|
275
|
+
```bash
|
|
276
|
+
# Re-run initialization
|
|
277
|
+
telos init
|
|
278
|
+
|
|
279
|
+
# Or regenerate agents
|
|
280
|
+
telos rediscover
|
|
281
|
+
```
|
|
282
|
+
|
|
283
|
+
### Platform Symlink Issues (Windows)
|
|
284
|
+
|
|
285
|
+
**Error:** Symlinks not working on Windows
|
|
286
|
+
|
|
287
|
+
**Solution:**
|
|
288
|
+
|
|
289
|
+
- Run terminal as Administrator
|
|
290
|
+
- Or use directory junctions (automatically attempted)
|
|
291
|
+
- Or manually copy `telos/content/AGENTS.md` to platform-specific location
|
|
292
|
+
|
|
293
|
+
---
|
|
294
|
+
|
|
295
|
+
## Advanced Usage
|
|
296
|
+
|
|
297
|
+
### Custom Platform Configuration
|
|
298
|
+
|
|
299
|
+
Edit `.telos/config.json` to customize platform-specific settings:
|
|
300
|
+
|
|
301
|
+
```json
|
|
302
|
+
{
|
|
303
|
+
"platform": "claude",
|
|
304
|
+
"timestamp": "2024-10-24T...",
|
|
305
|
+
"symlinks": {
|
|
306
|
+
"CLAUDE.md": "telos/content/AGENTS.md",
|
|
307
|
+
"TELOS.md": "telos/content/TELOS.md"
|
|
308
|
+
}
|
|
309
|
+
}
|
|
310
|
+
```
|
|
311
|
+
|
|
312
|
+
### Manual Tool Addition
|
|
313
|
+
|
|
314
|
+
Edit `telos/content/TOOLS.md` to manually add tools, then:
|
|
315
|
+
|
|
316
|
+
```bash
|
|
317
|
+
telos rediscover
|
|
318
|
+
```
|
|
319
|
+
|
|
320
|
+
### Agent Customization
|
|
321
|
+
|
|
322
|
+
Edit individual agent files in `telos/agents/` to customize behavior. After
|
|
323
|
+
editing:
|
|
324
|
+
|
|
325
|
+
```bash
|
|
326
|
+
# Regenerate consolidated AGENTS.md
|
|
327
|
+
telos rediscover
|
|
328
|
+
```
|
|
329
|
+
|
|
330
|
+
---
|
|
331
|
+
|
|
332
|
+
For more information, see:
|
|
333
|
+
|
|
334
|
+
- [README.md](./README.md) - Philosophy and overview
|
|
335
|
+
- [PHILOSOPHY.md](./PHILOSOPHY.md) - Theoretical foundation (if exists)
|
|
336
|
+
- [GitHub Issues](https://github.com/yourusername/telos/issues) - Bug reports
|
|
337
|
+
and feature requests
|
package/bin/telos-cli.js
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
|
|
3
|
+
const { Command } = require('commander');
|
|
4
|
+
const { initCommand } = require('../lib/commands/init');
|
|
5
|
+
const { statusCommand } = require('../lib/commands/status');
|
|
6
|
+
const { rediscoverCommand } = require('../lib/commands/rediscover');
|
|
7
|
+
const { validateCommand } = require('../lib/commands/validate');
|
|
8
|
+
|
|
9
|
+
const program = new Command();
|
|
10
|
+
|
|
11
|
+
program
|
|
12
|
+
.name('telos')
|
|
13
|
+
.description('Telos-driven Multi-Agent Development Framework')
|
|
14
|
+
.version('0.1.0');
|
|
15
|
+
|
|
16
|
+
program
|
|
17
|
+
.command('init')
|
|
18
|
+
.description('Initialize Telos in your project with interactive discovery')
|
|
19
|
+
.option('-q, --quick', 'Quick initialization with sensible defaults')
|
|
20
|
+
.option('-v, --verbose', 'Show detailed output')
|
|
21
|
+
.action(initCommand);
|
|
22
|
+
|
|
23
|
+
program
|
|
24
|
+
.command('status')
|
|
25
|
+
.description('Show current Telos configuration')
|
|
26
|
+
.option('-v, --verbose', 'Show detailed configuration')
|
|
27
|
+
.action(statusCommand);
|
|
28
|
+
|
|
29
|
+
program
|
|
30
|
+
.command('rediscover')
|
|
31
|
+
.description('Re-run tool discovery and update configurations')
|
|
32
|
+
.option('-v, --verbose', 'Show detailed output')
|
|
33
|
+
.action(rediscoverCommand);
|
|
34
|
+
|
|
35
|
+
program
|
|
36
|
+
.command('validate')
|
|
37
|
+
.description('Validate Telos alignment across the project')
|
|
38
|
+
.option('-v, --verbose', 'Show detailed validation results')
|
|
39
|
+
.action(validateCommand);
|
|
40
|
+
|
|
41
|
+
program.parse();
|