write-tasklisted

# Task.md: milestone task index <HARD-GATE>The Design-stage candidate—`Design.md` plus `Contract.md` when the approved Design requires a separate cross-task interface authority—must have independent Critic plus primary-orchestrator review at one commit. Record `target_milestone_id`; every task belongs to that Milestone. If planning exposes changed upstream meaning, revise its WhitePaper, ROADMAP, Goal, Requirement, Design, or Contract authority instead of redefining it in Task.</HARD-GATE> Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing contract. Use the Design locale for artifact prose. Keep filename `Task.md`, `type: task`, `nature: normative`, and this parser-facing table header: ```markdown | # | task | spec anchor | prerequisite | status | execution | ``` ## Task content - Derive Task only from the reviewed Requirement, Design, and applicable Contract. If task planning requires changing upstream meaning or making a missing design decision, return to the authority that owns it. - Keep `Task.md` as a compact Milestone execution index. It answers only: - which independently decidable results must be delivered; - which AC, Design, and applicable Contract anchors authorize each result; - which real prerequisites prevent a task from starting; - the current macro status; - where the execution contract is linked. - Keep the parser-facing task header unchanged. Use stable task IDs and the task-state tokens