T-BDKN-close-out-regenerates-docs-index
Status: closed/done · Impact: medium · Complexity: small
A consumer project’s docs/index.md is a generated artifact indexing task
statuses, but nothing in the task-work flow regenerates it after a task PR’s
planning-doc body edits merge — so the index drifts stale on every landed
task. Give /sdlc:docs a post-merge trigger: /sdlc:task-close-out should
run the regeneration (or an equivalent post-merge hook should). Complements
T-PA51-task-state-commits-regen-site-page, which covers the four
frontmatter task-state commit points but not planning-doc body edits landed
via task PRs.
docs/index.mdis a generated artifact indexing task statuses; nothing in the task-work flow regenerates it after planning-doc edits —/sdlc:docsneeds a post-merge run, or close-out should trigger it.—
T-UDPO-extract-single-binary-examplepost-mortem
TBD — receiver to fill before promoting from planning/draft.
Proposed
Section titled “Proposed”TBD — receiver to fill before promoting from planning/draft.
Approach
Section titled “Approach”TBD — receiver to fill before promoting from planning/draft.
Files to touch
Section titled “Files to touch”TBD — receiver to fill before promoting from planning/draft.
Acceptance criteria
Section titled “Acceptance criteria”TBD — receiver to fill before promoting from planning/draft.
Out of scope
Section titled “Out of scope”- none
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”Spawned by /sdlc:spawn-task-pr on 2026-07-03 UTC from
T-UDPO-extract-single-binary-example in
https://github.com/sksizer/markdown-contract.