task-compiler

Compile user stories into machine-readable TaskContracts with verifiable acceptance criteria.

15|4|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/choam2426/geas --skill task-compiler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-compiler
Source: https://github.com/choam2426/geas/tree/main/plugin/skills/task-compiler
Command: npx skills add https://github.com/choam2426/geas --skill task-compiler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Task Compiler removes ambiguity in feature requests by converting user stories and design briefs into machine-readable TaskContracts that contain verifiable acceptance criteria, scope allowlists, eval commands, routing, and quality rubrics.

Core Features & Use Cases

  • Structured TaskContracts: Generate task_id, title, goal, task_kind, risk_level, gate_profile, vote_round_policy, and status.
  • Verification-ready Outputs: Produce acceptance criteria, eval_commands, retry_budget, scope.surfaces, dependencies, routing, base_snapshot, and rubrics for automated gates and reviews.
  • Context-aware Classification: Use mission spec, design brief, architecture rules, and existing tasks to determine IDs, risk, reviewers, and dependencies.
  • Use Case: When specifying a mission, run the compiler to convert each issue or feature description into a validated TaskContract ready for execution and verification.

Quick Start

Compile a user story into a TaskContract using the mission spec and design brief for context.

Frequently Asked Questions about task-compiler

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

FAQPage Schema
How do I convert user stories into verifiable acceptance criteria for automated testing?

Compile user stories into machine-readable TaskContracts to generate verifiable acceptance criteria, eval commands, and quality rubrics for automated gates and reviews.

What is a TaskContract and how does it scope engineering tasks?

A TaskContract is a machine-readable output containing task_id, goal, risk_level, scope allowlists, dependencies, and retry budgets to define and verify scoped engineering tasks.

How do I automate task routing and dependency mapping from feature descriptions?

Apply the compiler to mission workflows using design briefs and architecture context to automatically produce task routing, dependency lists, and reviewer assignments.

Can I generate eval commands and retry budgets for automated verification pipelines?

Yes, compiling feature descriptions produces verification-ready outputs including specific eval_commands, retry_budget configurations, and base snapshots for automated orchestration.

Does task compilation work with existing architecture rules and mission specs?

The compiler uses mission specs, design briefs, architecture rules, and existing tasks as context to determine task IDs, risk levels, dependencies, and classification.

What limitations exist when compiling design briefs into task contracts?

The compiler requires structured mission specs and architecture context to determine routing and dependencies accurately; ambiguous feature descriptions may produce incomplete scope allowlists or verification rubrics.