Skill 01 — Task Refiner

Purpose: Convert messy input (PRD, chat, notes) into a single structured task note with clear acceptance criteria.

Protocols:

• •[[docs/PROTOCOLS/VAULT_PROBE]]
• •[[docs/PROTOCOLS/EVIDENCE]]
• •[[docs/PROTOCOLS/RUN_LOGGING]]
• •[[docs/PROTOCOLS/PATCH_GATE]]
• •[[docs/PROTOCOLS/CONTEXT_BUDGET]]

Tools:

• •[[tools/repl/README]] — patch-gated edits (generate + check + apply)

Inputs (from Orchestrator)

• •Raw task description (required)
• •Optional: paths to relevant PRD docs or notes to consult (do not read whole docs; probe first)

Outputs (must write)

• •docs/tasks/<task_slug>.md
• •artifacts/task_meta.json
• •[[docs/skills/01_task_refiner/SUMMARY]]

Task slug rules

• •lowercase
• •words separated by hyphens
• •no dates unless necessary
• •max ~6–10 words

Example: dashboards-converting-kpi-filters

Run log (mandatory)

Create: artifacts/_runs/<timestamp>_01_task_refiner/ with COMMANDS.md + LOG.txt.

Steps

1. •If the Orchestrator provided PRD/note paths, probe them:
   • •search for headings like “Goal”, “DoD”, “Constraints”
   • •section to extract only relevant parts
2. •Write docs/tasks/<task_slug>.md using docs/templates/TASK_TEMPLATE.md as a guide.
3. •Ensure Acceptance Criteria are testable and unambiguous.
4. •Write artifacts/task_meta.json with:
   • •task_slug
   • •title
   • •created_at
   • •acceptance_criteria (array)
   • •links (paths to related docs)
5. •Write SUMMARY.md including:
   • •task slug + file path
   • •key acceptance criteria
   • •any missing inputs/questions

Definition of Done

• • Task note exists under docs/tasks/
• • Acceptance Criteria is a checklist
• • task_meta.json exists and matches the task note
• • SUMMARY.md exists and references the task file