CLEAR

Audit mission briefs for Context, Limit, Eval, Augment, and Result.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/terateams/TAES --skill clear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CLEAR
Source: https://github.com/terateams/TAES/tree/main/.github/skills/CLEAR
Command: npx skills add https://github.com/terateams/TAES --skill clear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CLEAR provides a rigorous preflight check to ensure Context, Limit, Eval, Augment, and Result are defined before starting a mission, preventing ambiguous task definitions.

Core Features & Use Cases

  • Five-element preflight: validates that all five elements exist and are coherent in mission briefs.
  • Template-driven checks: guides the creation of MISSION.md with explicit sections and acceptance criteria.
  • Use Case: before launching a new automation task or project, run CLEAR to confirm the mission is well-scoped and auditable.

Quick Start

Run the CLEAR preflight on MISSION.md to verify that all five elements are present and properly defined.

Frequently Asked Questions about CLEAR

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

FAQPage Schema
What is a preflight check for project task definition?

A preflight check for project task definition audits mission briefs to ensure essential elements like context, limits, and acceptance criteria are complete before initiation. This prevents ambiguous task definitions and ensures launch readiness.

How do I verify mission brief readiness before launching a sprint?

To verify mission brief readiness, run a preflight check on your MISSION.md to confirm that Context, Limit, Eval, Augment, and Result are explicitly defined and map to actionable acceptance criteria.

What elements should be included in a project preflight checklist?

A project preflight checklist should include five concrete elements: Context, Limit, Eval, Augment, and Result. These ensure the mission is well-scoped and auditable before task initiation.

Can I use a template-driven preflight check for automation tasks?

Yes, template-driven preflight checks guide the creation of MISSION.md with explicit sections and acceptance criteria. They apply to automation tasks to ensure mission elements are coherent and properly defined.

When do I need to run a preflight check on mission briefs?

You need to run a preflight check on mission briefs before initiating any new project, sprint, or automation task. This ensures the mission is well-scoped and auditable before launch.