35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
---
|
|
status: resolved
|
|
parent: "[[038-implement-skill-map]]"
|
|
claimed-by: "019fbb66-80d0-7a01-8ac9-01255adfc7b2"
|
|
claimed-at: "2026-08-01T11:22:04-04:00"
|
|
blocked-by:
|
|
- "[[039-implement-skill-old-workflow-research]]"
|
|
- "[[041-implement-skill-wayfinder-contract-research]]"
|
|
- "[[079-implement-skill-matt-wayfinder-research]]"
|
|
tags:
|
|
- ticket/grill
|
|
---
|
|
|
|
# Implement skill ticket closeout grill
|
|
|
|
## Question
|
|
|
|
Exactly what should `implement` write into the Wayfinder task ticket, parent map, commit, and PR body when the implementation succeeds, partially succeeds, or fails?
|
|
|
|
## Resolution
|
|
|
|
The decision tree is fully walked at the level this workflow should specify.
|
|
Do not overprescribe closeout taxonomy.
|
|
The code is the implementation artifact.
|
|
The Wayfinder ticket closeout records durable coordination facts only.
|
|
|
|
Wayfinder `status` is the lifecycle authority.
|
|
Acceptance criteria checkboxes may be updated as useful closeout detail, with `[x]` for satisfied criteria and `[-]` for deliberately dropped criteria when practical, but checkbox state is not the source of truth.
|
|
|
|
Implementation Notes should stay concise and capture only what future agents or humans need: deviations, dropped or changed scope, verification, branch, commit, PR, or why the ticket remains unresolved.
|
|
The agent uses judgment for partial or ambiguous outcomes, but must keep the recorded lifecycle honest and must not imply completion when the work is not complete.
|
|
|
|
The parent map should receive only a concise decision or outcome summary as required by Wayfinder.
|
|
Detailed implementation records belong in the task ticket, commit, PR, and working code, not in the map.
|