telos-exec

Orchestrate horizon-aware task execution across dev-team, dev-solo, and documental modes.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jllopis/ingenieria-del-proposito --skill telos-exec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telos-exec
Source: https://github.com/jllopis/ingenieria-del-proposito/tree/main/plugins/telos/skills/exec
Command: npx skills add https://github.com/jllopis/ingenieria-del-proposito --skill telos-exec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables executing planned work in a horizon-aware manner, ensuring alignment with the defined purpose and constraints before each task.

Core Features & Use Cases

  • Horizon-aware execution: Recites and respects the four horizons before every task to guarantee governance and traceability.
  • Mode coverage: Supports dev-team, dev-solo, and documental workflows, either implementing plans or drafting them.
  • Requirement-driven automation: Reads project guidance from docs/REQUIREMENTS.md and docs/TASKS.md to drive prioritization and scope.
  • Incremental delivery: Executes changes in small, revisable steps with clear commit messages and verifiable outcomes.

Quick Start

Ask the AI to /telos:exec to start executing the active plan and recite horizons before each task.

Frequently Asked Questions about telos-exec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute planned project tasks with horizon-aware precision?

Horizon-aware task execution is initiated by invoking the /telos:exec command. This triggers the system to recite the four governance horizons before each task, ensuring all project work remains traceable and aligned with predefined constraints.

What is horizon-aware execution in software project management?

Horizon-aware execution is a governance mechanism that recites four defined horizons before every task. It guarantees purposeful AI work by maintaining strict alignment with project requirements and providing incremental, traceable progress updates.

How do I use REQUIREMENTS.md and TASKS.md for requirement-driven automation?

Requirement-driven automation reads project guidance directly from docs/REQUIREMENTS.md and docs/TASKS.md. This drives task prioritization and scope definition, ensuring automated execution strictly follows the documented project constraints.

Does horizon-aware execution work for solo development and documental workflows?

Horizon-aware execution supports dev-team, dev-solo, and documental workflows. It can actively implement plans or draft them, ensuring incremental delivery with clear commit messages and verifiable outcomes across all modes.

How are changes committed during incremental task execution?

Incremental task execution applies changes in small, revisable steps. This approach ensures every modification produces clear commit messages and verifiable outcomes, maintaining strict traceability throughout the development lifecycle.

What is the best way to ensure AI alignment before executing a task?

The best way to ensure AI alignment is by reciting the four project horizons before each task. This guardrail mechanism enforces governance and traceability, verifying that all automated work satisfies the defined purpose.