telos-purpose-core

To replace vague prompts with explicit purpose in LLM workflows, articulate project changes across four horizons—functional, architectural, constraint, and authorship—and coordinate plan, execution, and review steps with templates and guardrails.

Purpose-driven governance for LLM-assisted project changes enforces systematic evaluation and auditable modifications by defining four horizons, applying purpose templates, and backing decisions with ADRs to ensure safe, aligned outcomes.

Turn ambiguous project requests into structured LLM tasks by converting them into purpose-bearing fichas that declare clear functional, architectural, constraint, and authorship horizons before planning and executing changes.

Yes, you can use ADRs and templates to audit LLM-generated changes by validating proposals against the four horizons and capturing lessons during the check phase for future reuse and systematic governance.

The four horizons in project governance define decision-making boundaries: functional covers what the change does, architectural covers structural impact, constraint covers restrictions, and authorship covers ownership and accountability.

No dependencies are required to implement purpose-driven LLM workflows; the skill provides embedded purpose templates, ADRs, and governance principles directly to guide planning, execution, and review without external libraries.