/Telos

name: Telos
version: 1.0.46
description: "Dual-context skill: Personal TELOS reads and updates goals, beliefs, narratives, strategies, and more with timestamped backups; Project TELOS analyzes .md/.csv directories for dependency chains, bottlenecks, and alignment, generating reports, narrative points, or dashboards. USE WHEN Telos, life goals, projects, dependencies, update TELOS, narrative points, McKinsey report, dashboard, what am I wrong about, life frames, mental models. NOT FOR conversational constitutional review (use Interview)."

🚨 MANDATORY: Voice Notification (REQUIRED BEFORE ANY ACTION)

**You MUST send this notification BEFORE doing anything else when this skill is invoked.**

1. **Send voice notification**:

   curl -s -X POST http://localhost:31337/notify \
     -H "Content-Type: application/json" \
     -d '{"message": "Running the WORKFLOWNAME workflow in the Telos skill to ACTION"}' \
     > /dev/null 2>&1 &

2. **Output text notification**:

   Running the **WorkflowName** workflow in the **Telos** skill to ACTION...

**This is not optional. Execute this curl command immediately upon skill invocation.**

Telos

What It Does

Reads and updates two kinds of context. Personal TELOS: the principal's life context — goals, beliefs, wisdom, books, movies, challenges, narratives, strategies, mission, models, predictions, traumas, frames, lessons, wrong-beliefs — at `~/.claude/LIFEOS/USER/TELOS/`, updated through the Update workflow with timestamped backups. Project TELOS: analyzes a directory of .md/.csv files to extract dependency chains (PROBLEMS→GOALS→STRATEGIES→PROJECTS), bottlenecks, alignment, and progress, then produces a McKinsey-style report, n=24 narrative points, or a Next.js dashboard built by parallel engineers.

The Problem

Life context and project state both sprawl across many files, and acting on them by hand is error-prone. Personal goals, beliefs, and lessons drift out of date, and hand-editing them risks losing history or corrupting structure. Project documentation hides the dependency chains, bottlenecks, and misalignments that decide whether the work is on track — you can read every file and still not see how PROBLEMS connect to GOALS connect to PROJECTS. This skill gives both a single safe way in: structured updates with backups for the personal side, and automated relationship analysis plus rendered outputs for the project side.

How It Works

**TELOS** (Telic Evolution and Life Operating System) is a context-gathering system with two applications:

1. **Personal TELOS** - {PRINCIPAL.NAME}'s life context system (beliefs, goals, lessons, wisdom) at `~/.claude/LIFEOS/USER/TELOS/` 2. **Project TELOS** - Analysis framework for organizations/projects (relationships, dependencies, goals, progress)

The skill detects which context a request means (see Context Detection below), then routes to the right workflow. Personal updates always go through the Update workflow so backups and changelog entries happen automatically. Project analysis scans the target directory, builds a relationship graph, and renders the output format you asked for.

Workflow Routing

**When executing a workflow, output this notification directly:**

Running the **WorkflowName** workflow in the **Telos** skill to ACTION...

| Workflow | Trigger | File | |----------|---------|------| | **Update** | "add to TELOS", "update my goals", "add book to TELOS" | `Workflows/Update.md` | | **InterviewExtraction** | "extract content", "extract interviews", "analyze interviews" | `Workflows/InterviewExtraction.md` | | **CreateNarrativePoints** | "create narrative", "narrative points", "TELOS report", "n=24" | `Workflows/CreateNarrativePoints.md` | | **WriteReport** | "write report", "McKinsey report", "create TELOS report", "professional report" | `Workflows/WriteReport.md` |

**Note:** For general project analysis, dashboards, dependency mapping, and executive summaries, the skill handles these directly without a separate workflow file.

Examples

**Example 1: Update personal TELOS**

User: "add Project Hail Mary to my TELOS books"
--> Invokes Update workflow
--> Creates timestamped backup of BOOKS.md
--> Adds book entry with formatted metadata
--> Logs change in updates.md with timestamp

**Example 2: Analyze project with TELOS**

User: "analyze ~/Projects/MyApp with TELOS"
--> Scans all .md and .csv files in directory
--> Extracts entities, relationships, dependencies
--> Returns analysis with dependency chains and progress metrics

**Example 3: Build project dashboard**

User: "build a dashboard for TELOSAPP"
--> Launches up to 16 parallel engineers
--> Creates Next.js dashboard with shadcn/ui + Aceternity
--> Returns interactive dashboard with dependency graphs, metrics cards, progress tables

**Example 4: Generate narrative points**

User: "create TELOS narrative for Acme Corp, n=24"
--> Invokes CreateNarrativePoints workflow
--> Analyzes TELOS context (situation, problems, recommendations)
--> Returns 24 crisp bullet points (8-12 words each)
--> Output is slide-ready for presentations or customer briefings

**Example 5: Generate McKinsey-style report**

User: "write a TELOS report for Acme Corp"
--> Invokes WriteReport workflow
--> First runs CreateNarrativePoints to generate story content
--> Maps narrative to McKinsey report structure
--> Generates web-based report with professional styling
--> Output at {project_dir}/report - run `bun dev` to view
--> White background, subtle Tokyo Night Storm accents
--> Includes: cover page, executive summary, findings, recommendations, roadmap

---

Context Detection

**How {DA_IDENTITY.NAME} determines which TELOS context:**

| User Request | Context | Location | |--------------|---------|----------| | "my TELOS", "my goals", "my beliefs", "add to TELOS" | Personal TELOS | `~/.claude/LIFEOS/USER/TELOS/` | | "Alma", "TELOSAPP", "analyze [project]", "dash