write-tasklisted

# Task.md: milestone task index <HARD-GATE>The complete linked Design Bundle—root `Design.md` plus every applicable module, `design/Contract.md`, split contract, and structural authority—must have passed its owning-stage acceptance and Critic necessity gates at one commit. Record `target_milestone_id`; every task belongs to that Milestone. If planning exposes changed upstream meaning or an implementation-significant unknown, stop and return the issue to `gmgn` for routing instead of deciding it in Task.</HARD-GATE> Before writing, load the registered `gmgn` Skill through normal discovery and follow its local writing rules. 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, applicable Contract, and any implementation-relevant D-ID already linked by Design. If task planning requires changing upstream meaning or making a missing decision, stop and return the issue to `gmgn` for routing. - Keep `Task.md` as a Milestone execution index. It answers only: - which independently decidable results must be delivered; - which applicable D-ID, AC, Design, and Contract anchors authorize each result; - which real prerequisites prevent a task from starting; - the current macro status; - where the execution contract is linked. - Keep t