tda-task-brief-from-plan

Converts research plans into agent-ready task briefs with acceptance criteria and assurance lanes.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill tda-task-brief-from-plan-zk-theory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tda-task-brief-from-plan
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/tda-task-brief-from-plan
Command: npx skills add https://github.com/ZK-Theory/TDL --skill tda-task-brief-from-plan-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a research plan, review finding, or conversation into work that an AI coding agent can execute safely is error-prone: scope creeps, acceptance criteria stay vague, and dispatch happens on unverified assumptions. This Skill converts plans into bounded, vertical task briefs for Claude Code or Codex with machine-checkable acceptance criteria. ## Core Features & Use Cases - Structured Brief Template: Produces task briefs covering execution context, assurance lanes, upstream contracts, inputs/outputs by path, validation commands, provenance, runtime constraints, and stop conditions. - Dispatch Safety Rules: Enforces hard scope stops, blocking user-decision gates, a no-synthetic-results rule, and verification steps for any inferred external dependency. - Boundary Routing: Routes outcome-contingent work to pre-registration and unresolved concepts to domain modeling instead of dispatching prematurely. - Use Case: A research manager has a plan note for a statistical analysis pipeline. Use this Skill to produce a task brief naming the capability gap, required contracts, validation commands, and stop conditions before handing it to an implementing agent. ## Quick Start Convert this research plan into an agent-ready task brief with acceptance criteria, assurance lanes, and stop conditions.

Frequently Asked Questions about tda-task-brief-from-plan

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

FAQPage Schema
How do I convert a research plan into a task brief for an AI coding agent?▼

Provide the plan and this Skill produces a vertical task brief with execution context, assurance lanes, inputs and outputs by path, machine-checkable acceptance criteria, validation commands, and stop conditions ready for dispatch to Claude Code or Codex.

What makes a task brief safe to dispatch to an autonomous agent?▼

A dispatch-safe brief bounds scope with explicit hard stops, restates user-decision gates as blocking rather than advisory, forbids synthetic output in results directories, and includes verification steps for any inferred property of external resources.

When should a plan not be converted into a task brief?▼

Do not create a brief when the work is outcome-contingent on a decision rule, which requires pre-registration instead, or when the concept is still unresolved and needs domain modeling or a design conversation first.

Can tests passing be the acceptance criterion for a task?▼

No. For any task touching an assurance lane, tests passing alone is never sufficient; the brief must name the specific enforcement artifact or record why none applies.

What are the limitations of task briefs for parallel dispatch?▼

Parallel dispatch is valid only when the resolved workspace is the worktree that currently owns the required branch. A detached checkout at the same commit is not an alternative owner and must not receive the task.