proofline
TR

task-author

Purpose

Turns a one-sentence request or an external issue into the canonical TASK.md: goal, context, numbered observable acceptance criteria, out of scope, constraints, risks and a suggested class.

Source Skill purpose

When to use it

Use task-author before planning a non-trivial change or when importing an external issue into the canonical task format. It turns a request into a goal, context, numbered observable acceptance criteria, explicit out-of-scope items, constraints, risks and a class justified by the class indicators. It reads only enough project context to avoid needless questions. Ambiguity is gathered into one input round rather than silently filled. The result can be rendered into a configured target template while tracker writes remain with the adapter.

Imported issue text is handled as data and missing canonical fields become questions. A criterion says what can be observed from a situation, not which library or algorithm to use. The author self-checks the task before handing it to planning, and tracker writes stay with the task adapter.

Source Skill purpose

How it works

Steps of the skill, in source orderEach numbered step follows the skill definition and links to its source.1. Resolve contextFlow2. Gather only needed factsFlow3. Draft the taskFlow4. Self-check and validateFlow5. Ask if neededFlow6. Return the taskFlow
Steps of the skill, in source order

Source Flow

  1. Resolve context Choose the local or run output location and identify the request source. Resolve the target template with validate-task.mjs --resolve-template; a project template takes precedence over the bundled one.

    Source Flow

  2. Gather only needed facts Read only enough to avoid needless questions: the README, the directory layout and the files the request names. Record each repository fact you rely on as path:symbol.

    Source Flow

  3. Draft the task Write each canonical section and classify by the strongest applicable indicator. Take verification commands from the project's own build and test commands.

    Source Flow

  4. Self-check and validate Run the task checklist and validator, fixing every reported issue.

    Source Flow

  5. Ask if needed Mark all remaining requirement questions in the draft as QUESTION-n, collect them in one input round and stop.

    Source Flow

  6. Return the task Show the validated task or hand it to the lead for the next step.

    Source Flow

Key rules

  • Write acceptance criteria as observable input or situation and outcome.

    Source Hard rules

  • Keep implementation details out of criteria unless the user requires them.

    Source Hard rules

  • State at least one explicit out-of-scope line.

    Source Hard rules

  • Gather ambiguity into exactly one question round.

    Source Hard rules

  • Derive task class from indicators rather than intuition.

    Source Hard rules

Output and gate

Output

  • Write the canonical task sections in their required order.

    Source Output

Gate

The skill definition states no gate rule.

Source Skill definition

Source

Source Skill definition

← All skills