telos-framework 0.7.2 → 0.8.2

package/.claude/commands/telos/init.md

@@ -22,42 +22,9 @@ structure (L1), and generate all necessary files.
 This prevents confusion when the user answers one question and you misinterpret
 it as answering a different question.
 
-## Step 0: Detect AI Platform & Create Config
+## Important Note
 
-**IMPORTANT**: Before proceeding, detect which AI coding assistant is running:
-
-1. **Check environment indicators**:
-   - Claude Code: Check if `.claude/` directory exists or if running from Claude
-     slash command
-   - Opencode: Check if `.opencode/` directory exists or `OPENCODE_SESSION` env
-     var
-   - Other: Neither detected
-
-2. **If running from Claude Code AND no `CLAUDE.md` exists**:
-   - Create `CLAUDE.md` with the Telos reference template (see section 4.3 for
-     template)
-   - Include note: "Auto-generated by Telos initialization"
-
-3. **If `CLAUDE.md` exists but doesn't mention Telos**:
-   - Prepend the Telos reference section (see section 4.3)
-
-4. **Ask user which platform they want to initialize for**:
-
-Present ONLY this question and WAIT for response:
-
-```
-Which AI coding platform would you like to initialize Telos for?
-
-1. Claude Code (slash commands in `.claude/commands/telos/`)
-2. Opencode (commands in `.opencode/command/telos/`)
-3. Both
-4. Skip command installation (manual setup)
-
-Your choice [1-4]:
-```
-
-**IMPORTANT**: Do NOT preview next steps. Do NOT say "Next I'll...". STOP and
-WAIT for user response, then store it for Step 4.4.
+Platform setup (slash commands, config files) was already completed by running `npx telos-framework init`. You don't need to ask about platforms or create command files - they already exist. Your job is to analyze the codebase and generate the `.telos/` hierarchy files.
 
 ## Step 1: Analyze Codebase
 
@@ -543,6 +510,50 @@ For each level (L9 → L1), create `.telos/agents/l[N]-[agent-name].md`:
 - Tools: [Detected linters - ESLint, Prettier, etc.]
 - Examples: Reject PR with linting errors
 
+### 4.2.1 Copy Sub-Agent Specialists
+
+After creating the L1-L9 agent files, you MUST copy the specialized sub-agent files from the Telos framework templates.
+
+**CRITICAL: Execute these bash commands immediately:**
+
+```bash
+# Find telos-framework package location using Node module resolution
+TELOS_PATH=$(node -p "require.resolve('telos-framework/package.json').replace('/package.json', '')")
+
+# Create sub-agents directory
+mkdir -p .telos/agents/sub-agents
+
+# Copy all sub-agent files (15 specialized agents)
+cp "$TELOS_PATH/templates/agents/sub-agents/"*.md .telos/agents/sub-agents/
+
+# Copy sub-agent mapping guide
+cp "$TELOS_PATH/templates/agents/SUB_AGENT_MAPPING.md" .telos/agents/
+```
+
+**Verification:** After running these commands, confirm that `.telos/agents/sub-agents/` contains 15 markdown files and `.telos/agents/SUB_AGENT_MAPPING.md` exists.
+
+**Sub-agents included:**
+- api-design.md - REST/GraphQL API design
+- code-reviewer.md - Code quality review
+- component-implementation.md - UI component creation
+- database-design.md - Database schema design
+- devops.md - Deployment and CI/CD
+- documentation.md - Technical documentation
+- feature-implementation.md - Feature development
+- infrastructure.md - Cloud infrastructure
+- polish.md - Code optimization
+- prd.md - Product requirements
+- quality.md - Quality assurance
+- refactoring.md - Code refactoring
+- research.md - Technical research
+- security-audit.md - Security review
+- testing.md - Test creation
+
+**Mapping file:**
+- SUB_AGENT_MAPPING.md - Maps sub-agents to L1-L9 levels
+
+These sub-agents can be invoked by the L1-L9 agents using the Task tool for specialized work.
+
 ### 4.3 Integrate with AI Assistant Configuration Files
 
 Check for and update existing AI assistant configuration files to reference
@@ -606,103 +617,13 @@ agent definitions.
 **If no AI assistant config files exist**, create `AGENTS.md` with Telos
 content.
 
-### 4.4 Install Platform-Specific Commands
-
-Based on user's choice from Step 0:
-
-#### Option 1: Claude Code Commands
-
-Create slash commands in `.claude/commands/telos/`:
-
-**Files to create:**
-
-- `init.md` - This initialization command
-- `quick.md` - Quick initialization with auto-accept
-- `validate.md` - Validate code against Telos hierarchy
-- `status.md` - Show current Telos configuration
-- `reset.md` - Clear and reinitialize
-
-All use standard markdown format (already created by `telos init` CLI).
-
-#### Option 2: Opencode Commands
-
-Create commands in `.opencode/command/` using frontmatter format:
-
-**Template structure for Opencode:**
-
-```markdown
----
-description: [Command description]
----
-
-[Command template/prompt here]
-```
-
-**Files to create:**
-
-1. `.opencode/command/telos-init.md`:
-
-```markdown
----
-description: Initialize Telos multi-agent system for this project
----
-
-[Copy full content from .claude/commands/telos/init.md]
-```
-
-2. `.opencode/command/telos-quick.md`:
-
-```markdown
----
-description: Quick Telos initialization with auto-accepted AI proposals
----
-
-[Copy full content from .claude/commands/telos/quick.md]
-```
-
-3. `.opencode/command/telos-validate.md`:
-
-```markdown
----
-description: Validate current code against Telos purpose hierarchy
----
+### 4.4 Platform Commands Already Installed
 
-[Copy full content from .claude/commands/telos/validate.md]
-```
+**Note**: Platform-specific slash commands were already installed by `npx telos-framework init`. You don't need to create or modify command files - they already exist in:
+- `.claude/commands/telos/` (if Claude Code was selected)
+- `.opencode/command/` (if Opencode was selected)
 
-4. `.opencode/command/telos-status.md`:
-
-```markdown
----
-description: Show current Telos configuration and hierarchy
----
-
-[Copy full content from .claude/commands/telos/status.md]
-```
-
-5. `.opencode/command/telos-reset.md`:
-
-```markdown
----
-description: Clear existing Telos installation and reinitialize
----
-
-[Copy full content from .claude/commands/telos/reset.md]
-```
-
-**Note**: Opencode commands are installed directly in `.opencode/command/` with
-`telos-` prefix. This creates commands like `/telos-init` instead of
-`/telos/init`.
-
-#### Option 3: Both Platforms
-
-Create command files in both `.claude/commands/telos/` AND
-`.opencode/command/telos/`.
-
-#### Option 4: Skip Command Installation
-
-Only create `.telos/` directory structure and config file integrations. User
-will manually install commands later via `telos init` CLI.
+Skip any command installation steps.
 
 ### 4.5 Create Orchestrator (Optional)
 
@@ -732,12 +653,15 @@ Once all files are generated, display:
 
 - `.telos/TELOS.md` - Ultimate purpose and hierarchy
 - `.telos/agents/l9-telos-guardian.md` through `l1-syntax-linter.md`
+- `.telos/agents/sub-agents/` - 15 specialized sub-agents
+- `.telos/agents/SUB_AGENT_MAPPING.md` - Sub-agent delegation guide
 - Updated AI assistant config files (AGENTS.md, CLAUDE.md, .cursorrules, etc.)
-- Platform commands: [List based on Step 0 choice]
-  - Claude Code: `.claude/commands/telos/*.md` (5 commands)
-  - Opencode: `.opencode/command/telos/*.md` (5 commands)
 - `logos/orchestrator.js` - Request router (if applicable)
 
+**Platform commands** (already installed by CLI):
+  - Claude Code: `.claude/commands/telos/*.md` (5 commands)
+  - Opencode: `.opencode/command/telos-*.md` (5 commands)
+
 **Next steps:**
 
 1. Review the generated agent definitions in `.telos/agents/`

package/.claude/commands/telos/quick.md

@@ -40,9 +40,31 @@ Create all files exactly as specified in `/telos-init` Step 4:
 
 - `.telos/TELOS.md`
 - `.telos/agents/l9-telos-guardian.md` through `l1-syntax-linter.md`
+- `.telos/agents/sub-agents/` (15 specialized sub-agent files)
+- `.telos/agents/SUB_AGENT_MAPPING.md` (sub-agent mapping guide)
 - `AGENTS.md` (if `.claude/` or `.opencode/` exists)
 - `logos/orchestrator.js` (if Node.js project)
 
+### Copy Sub-Agent Specialists
+
+After generating the L1-L9 agent files, **EXECUTE these bash commands** to copy the specialized sub-agents:
+
+```bash
+# Find telos-framework package location using Node module resolution
+TELOS_PATH=$(node -p "require.resolve('telos-framework/package.json').replace('/package.json', '')")
+
+# Create sub-agents directory
+mkdir -p .telos/agents/sub-agents
+
+# Copy all sub-agent files (15 specialized agents)
+cp "$TELOS_PATH/templates/agents/sub-agents/"*.md .telos/agents/sub-agents/
+
+# Copy sub-agent mapping guide
+cp "$TELOS_PATH/templates/agents/SUB_AGENT_MAPPING.md" .telos/agents/
+```
+
+**Verification:** Confirm that `.telos/agents/sub-agents/` contains 15 markdown files.
+
 ## Step 4: Display Summary
 
 Once complete, show:
@@ -66,7 +88,9 @@ Once complete, show:
 
 **Files created:**
 - `.telos/TELOS.md`
-- `.telos/agents/` (9 agent definitions)
+- `.telos/agents/` (9 L1-L9 agent definitions)
+- `.telos/agents/sub-agents/` (15 specialized sub-agents)
+- `.telos/agents/SUB_AGENT_MAPPING.md`
 - `AGENTS.md`
 - `logos/orchestrator.js` (if applicable)
 

package/README.md

@@ -111,16 +111,36 @@ Full integration with [OpenSpec](https://openspec.dev) workflow:
 - Validation uses OpenSpec archive
 - Telos lineage tracked throughout
 
-### Technical Agent Delegation
+### Specialized Sub-Agent Delegation
 
-9-level agents can delegate to specialized technical agents from
-[Claude Collective](https://github.com/alan-colver/claude-code-collective):
+Each L1-L9 agent can delegate to 15 specialized sub-agents for deep technical expertise:
 
-- `research-agent` for technical investigation
-- `quality-agent` for comprehensive reviews
-- `testing-implementation-agent` for test suites
-- `devops-agent` for deployment
-- And more specialized agents
+**Strategic & Planning:**
+- `prd` - Product requirements and user stories
+- `research` - Technical research and library comparison
+
+**Implementation:**
+- `api-design` - REST/GraphQL API design
+- `component-implementation` - UI component creation
+- `feature-implementation` - Feature development
+- `database-design` - Database schema design
+
+**Quality & Testing:**
+- `code-reviewer` - Code quality review
+- `quality` - Comprehensive QA (accessibility, security, performance)
+- `security-audit` - Security vulnerability assessment
+- `testing` - Test creation and strategy
+
+**Operations & Documentation:**
+- `devops` - Deployment and CI/CD
+- `infrastructure` - Cloud infrastructure
+- `documentation` - Technical documentation
+
+**Optimization:**
+- `refactoring` - Code restructuring
+- `polish` - Performance optimization
+
+All sub-agents integrated from [agents repository](https://github.com/accolver/agents/tree/main/agent)
 
 ## Commands
 
@@ -156,6 +176,9 @@ your-project/
 │   │   ├── LOGOS.md         # Orchestrator instructions
 │   │   └── TOOLS.md         # Tool registry and mappings
 │   ├── agents/              # Individual agent definitions (L1-L9)
+│   │   ├── l9-telos-guardian.md through l1-syntax-linter.md
+│   │   ├── sub-agents/      # 15 specialized sub-agents
+│   │   └── SUB_AGENT_MAPPING.md  # Sub-agent to level mapping
 │   └── templates/           # Platform-specific configs
 ├── .telos/                  # Runtime state (gitignored)
 ├── TELOS.md                 # Symlink for visibility

package/lib/generators/agent-generator.js

@@ -106,6 +106,21 @@ Recommendation: MODIFY
 Modification needed: Ensure free tier preserves core value; premium only for advanced features
 \`\`\`
 
+## Sub-Agent Delegation
+
+You can delegate specialized tasks to expert sub-agents using the Task tool:
+
+**Primary Sub-Agents:**
+- \`prd\` - Understanding product requirements at strategic level
+- \`research\` - Strategic technology research and direction
+
+**Example Delegation:**
+\`\`\`
+Use the research subagent to analyze whether adopting [technology] aligns with our ultimate purpose of ${l9.purpose}.
+\`\`\`
+
+See \`.telos/agents/SUB_AGENT_MAPPING.md\` for complete sub-agent documentation.
+
 ## Remember
 
 You are the guardian of meaning. Every line of code should ultimately serve our Telos. When in doubt, ask: "Why are we building this software?" The answer is always:
@@ -228,6 +243,26 @@ Status: FAIL
 Cannot proceed until critical issues resolved.
 \`\`\`
 
+## Sub-Agent Delegation
+
+You can delegate specialized tasks to expert sub-agents using the Task tool:
+
+**Primary Sub-Agents:**
+- \`code-reviewer\` - Comprehensive code quality review
+- \`quality\` - Quality assurance including accessibility, security, performance
+- \`security-audit\` - Security vulnerability assessment
+
+**Secondary Sub-Agents:**
+- \`testing\` - Test quality validation
+- \`refactoring\` - Code cleanup and refactoring
+
+**Example Delegation:**
+\`\`\`
+Use the quality subagent to review [files] for quality, accessibility, security, and performance issues.
+\`\`\`
+
+See \`.telos/agents/SUB_AGENT_MAPPING.md\` for complete sub-agent documentation.
+
 ## Remember
 
 Clean code structure is the foundation. Without L1 integrity, higher-level abstractions crumble. Hold the line on quality.
@@ -354,6 +389,26 @@ Status: PASS
 Serves: L3 PricingComponent - enables dynamic pricing logic
 \`\`\`
 
+## Sub-Agent Delegation
+
+You can delegate specialized tasks to expert sub-agents using the Task tool:
+
+**Primary Sub-Agents:**
+- \`feature-implementation\` - Feature and function implementation
+- \`refactoring\` - Function refactoring and optimization
+
+**Secondary Sub-Agents:**
+- \`polish\` - Code optimization and performance tuning
+- \`database-design\` - Data access function implementation
+- \`testing\` - Unit test creation
+
+**Example Delegation:**
+\`\`\`
+Use the feature-implementation subagent to implement the [function] with proper error handling and validation.
+\`\`\`
+
+See \`.telos/agents/SUB_AGENT_MAPPING.md\` for complete sub-agent documentation.
+
 ## Remember
 
 Functions are atoms of behavior. Each must be:

package/lib/generators/all-agents-generator.js

@@ -89,6 +89,14 @@ Serves: [confirms higher-level contribution]
 
 ${getIntegration(level)}
 
+## Sub-Agent Delegation
+
+You can delegate specialized tasks to expert sub-agents using the Task tool:
+
+${getSubAgents(level)}
+
+See \`.telos/agents/SUB_AGENT_MAPPING.md\` for complete sub-agent documentation.
+
 ## Remember
 
 Your work at ${level} is essential to the hierarchy. Maintain quality and alignment with the purpose: "${hierarchyData.purpose}"
@@ -193,4 +201,75 @@ function getIntegration(level) {
   return integration[level] || '';
 }
 
+function getSubAgents(level) {
+  const subAgents = {
+    L3: `**Primary Sub-Agents:**
+- \`component-implementation\` - Component creation and design
+- \`feature-implementation\` - Feature-level component implementation
+
+**Secondary Sub-Agents:**
+- \`refactoring\` - Component refactoring
+- \`quality\` - Component quality review
+- \`testing\` - Component testing
+
+**Example Delegation:**
+\`\`\`
+Use the component-implementation subagent to create a reusable [component] that follows our design system.
+\`\`\``,
+    L4: `**Primary Sub-Agents:**
+- \`api-design\` - REST/GraphQL API design and contracts
+- \`database-design\` - Data schema and contract definition
+
+**Secondary Sub-Agents:**
+- \`devops\` - API deployment infrastructure
+- \`documentation\` - API documentation
+- \`testing\` - API and contract testing
+
+**Example Delegation:**
+\`\`\`
+Use the api-design subagent to design a RESTful API for [resource] with proper authentication and validation.
+\`\`\``,
+    L5: `**Primary Sub-Agents:**
+- \`testing\` - User journey and E2E testing
+- \`quality\` - Workflow quality assurance
+
+**Secondary Sub-Agents:**
+- \`component-implementation\` - User interaction implementation
+
+**Example Delegation:**
+\`\`\`
+Use the testing subagent to create E2E tests that validate the [workflow] user journey.
+\`\`\``,
+    L6: `**Primary Sub-Agents:**
+- \`component-implementation\` - UI component creation with accessibility
+- \`research\` - UX patterns and accessibility research
+
+**Secondary Sub-Agents:**
+- \`quality\` - Accessibility validation (WCAG 2.1 AA)
+- \`testing\` - User journey testing
+
+**Example Delegation:**
+\`\`\`
+Use the component-implementation subagent to create an accessible [component] following WCAG 2.1 AA standards.
+\`\`\``,
+    L7: `**Primary Sub-Agents:**
+- \`prd\` - Product requirements and feature specifications
+- \`research\` - Feature research and best practices
+
+**Example Delegation:**
+\`\`\`
+Use the prd subagent to create a comprehensive PRD for [feature] with user stories and acceptance criteria.
+\`\`\``,
+    L8: `**Primary Sub-Agents:**
+- \`prd\` - Understanding market needs and user requirements
+- \`research\` - Competitive analysis and market trends
+
+**Example Delegation:**
+\`\`\`
+Use the prd subagent to create user stories that demonstrate business value for [feature].
+\`\`\``
+  };
+  return subAgents[level] || '';
+}
+
 module.exports = { generateAllAgents };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "telos-framework",
-  "version": "0.7.2",
+  "version": "0.8.2",
   "description": "Telos-driven Multi-Agent Development Framework - A philosophically-grounded AI collective for purpose-aligned software development",
   "main": "index.js",
   "bin": {