telos-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.

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.

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.

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.

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.

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.