init-task-persistence

What problem does it solve?

This Skill guarantees the pipeline keeps the operator’s original intent intact by creating a per-task, append-only init-task artefact that every subsequent stage must read to detect and surface drift.

Core Features & Use Cases

• Creates a canonical init-task record that stores the verbatim /dr-init command brief plus an operator append-log.
• Enforces mandatory reading across stages so /dr-prd, /dr-plan, /dr-design, /dr-do, /dr-qa, /dr-compliance, and /dr-archive reconcile output with the init-task.
• Supports operator amendments with auditability via a structured, chronological append-log contract (including Q&A round blocks when required).
• Handles skipped /dr-init recovery by allowing retroactive backfill to seed a missing init-task so later QA utilities can proceed.

Quick Start

Use the init-task-persistence Skill to ensure your task’s verbatim operator intent is written at datarim/tasks/{TASK-ID}-init-task.md during /dr-init and then consistently validated and reflected by all subsequent pipeline commands.