implementlisted

# implement Use this skill to implement an approved PRD end to end. Match the user's language by default. The public closing flow is intentionally small: ```text implementation complete -> final evidence registered -> sasu implement verify -> sasu implement finalize ``` `state.json` is the only machine record. `receipt.json` and `implementation-result.md` are derived outputs. ## Reference Routing Read each directly linked reference completely when its condition applies. | Reference | Read when | | --- | --- | | [`references/execution-planning.md`](references/execution-planning.md) | Before implementation, while closing tasks, or when execution order is unclear. | | [`references/verification-and-evidence.md`](references/verification-and-evidence.md) | Before capturing or registering final runtime evidence and before unified verify. | | [`references/reviews-and-finalization.md`](references/reviews-and-finalization.md) | Before unified verify, finalize, or a blocked handoff. | | [`references/worktrees-and-delivery.md`](references/worktrees-and-delivery.md) | When delivery is `pr`, a worktree is configured, or post-receipt delivery is requested. | ## Core Invariants - Never implement a pending PRD without explicit human approval or the user's verbatim conversational approval. - Treat Major Technical Structure Changes as the approved structure boundary. - Do not add unmapped scope, services, schemas, external calls, destructive actions, or compatibility paths. - Ver