# Project Telos

> Project-only Telos context mapping for goals, constraints, stakeholders, decisions, dependencies, risks, and narrative reports. Use when analyzing a project, building a project context pack, mapping dependencies, writing an executive project brief, or creating a non-personal project dashboard/report.

- Skill: `mj-deving/project-telos` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mj-deving/project-telos`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mj-deving/project-telos/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: mj-deving (https://skillmd.com/u/mj-deving)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mj-deving/project-telos

---


# Project Telos

Use this skill to build a portable, non-personal operating map for a project or organization.

This public variant intentionally excludes personal life, career, belief, and private-user memory workflows. Work only from user-provided files, repositories, notes, or public sources.

## Boundaries

- Do not read private personal context directories unless the user explicitly provides them for this task.
- Do not store personal beliefs, goals, credentials, or private life context.
- Do not include secrets in generated reports.
- Treat project context as shareable by default unless the user says otherwise.

## Core Model

Capture the project as:

- **Purpose**: mission, goals, success criteria, and non-goals.
- **Actors**: users, teams, stakeholders, owners, dependencies.
- **Assets**: repositories, docs, dashboards, datasets, services, APIs.
- **Decisions**: architectural choices, product calls, open questions.
- **Constraints**: deadlines, budgets, compliance, technical limits.
- **Risks**: blockers, unknowns, fragility, coordination hazards.
- **Trajectory**: current state, next milestones, and likely future forks.

## Workflow

1. Define the project boundary and intended audience.
2. Inventory available evidence: docs, code, issues, PRs, diagrams, notes, and source links.
3. Extract entities, decisions, dependencies, risks, and unresolved questions.
4. Identify contradictions, stale assumptions, and missing owners.
5. Produce a project context pack or executive brief.
6. Recommend concrete follow-up tasks, owners, and validation checks.

## Output Patterns

For a compact context pack:

- **Project Thesis**
- **Current State**
- **Dependency Map**
- **Decision Log**
- **Risks / Unknowns**
- **Next Actions**

For an executive report:

- **Executive Summary**
- **Strategic Context**
- **Operating Model**
- **Progress and Blockers**
- **Recommendations**
- **Appendix: Evidence Reviewed**