telos-brief

Convert user requests into structured purpose fichas with four horizons.

Updated Mar 13, 2026

Search Tags:#governance #project-management #purpose #brief #horizons #ficha

Ready to run

npx skills add https://github.com/jllopis/ingenieria-del-proposito --skill telos-brief

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: telos-brief
Source: https://github.com/jllopis/ingenieria-del-proposito/tree/main/plugins/telos/skills/brief
Command: npx skills add https://github.com/jllopis/ingenieria-del-proposito --skill telos-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ambiguous user requests into explicit, action-oriented purpose fichas that guide decision-making before implementation.

Core Features & Use Cases

Converts user prompts into structured purpose fichas with four horizons (Functional, Architectural, Restriction, Ownership).
Prompts for clarifications when input is ambiguous and surfaces next steps for execution and validation.
Suitable for requests involving code changes, architecture ADRs, or policy/documentation deliverables.

Quick Start

Provide a clear user request and let the tool generate the four-horizons ficha, prompting for clarifications if needed.

Frequently Asked Questions about telos-brief

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

FAQPage Schema

How do I convert a vague project request into an actionable brief?▼

Converting a vague project request into an actionable brief involves structuring the input into a purpose ficha that defines functional goals, architectural decisions, restrictions, and ownership. The tool prompts for clarifications when the initial request lacks specificity.

What is a purpose ficha in project governance?▼

A purpose ficha in project governance is a concise, structured document that captures explicit, action-oriented decisions before implementation. It organizes requests across four horizons: Functional, Architectural, Restriction, and Ownership to guide execution.

How do I structure architecture decisions and code change requests before implementation?▼

Structuring architecture decisions and code change requests requires applying the four horizons framework to define functional requirements, architectural choices, project restrictions, and ownership boundaries. This ensures all decision-making context is explicit before development starts.

Can I use this for documentation deliverables and policy changes, or just code?▼

Yes, you can use this for documentation deliverables and policy changes, not just code. The tool applies to any project request requiring structured governance, including architecture ADRs, policy updates, and documentary deliverables.

What happens when my project brief input is ambiguous or missing details?▼

When your project brief input is ambiguous or missing details, the tool identifies the gaps and asks clarifying questions. This ensures the generated purpose ficha contains explicit next steps for execution and validation before implementation begins.

Best way to enforce project governance horizons across new development tasks?▼

The best way to enforce project governance horizons is to process every new development task through a structured ficha that validates Functional, Architectural, Restriction, and Ownership requirements. This converts ambiguous prompts into governed, actionable deliverables.