T-BFKL-ensure-ready-tolerates-domain-sections
Status: closed/obsoleted · Impact: low · Complexity: small
Auto-generated from a /sdlc:task-work post-mortem. Review and
promote to ready before picking up.
task-ensure-ready walks the task body by canonical H2 names. A
task that introduces a domain-specific reference section (e.g. the
## Migration mapping table in
T-T5RB-consolidate-task-status-enum) breaks the linear-flow
assumption: the evaluator either rejects the file or silently treats
the section as the next canonical one. Establishing a convention for
domain-specific sections — and teaching the evaluator about it —
keeps richer task specs from confusing readiness checks.
“The
## Migration mappingtable sits between Approach and Files-to-touch in the task body, buttask-ensure-readylooks for the canonical contract sections by name. A task that introduces a domain-specific section breaks the linear flow assumption. Not blocking here, but if more tasks start carrying ‘reference tables’ they’ll need a convention (subsection under Approach? appendix- style at the end?).”
The evaluator currently looks up sections by H2 name in order and makes no allowance for interleaved non-contract sections.
Proposed
Section titled “Proposed”Either (a) the contract permits arbitrary extra H2 sections so long as all canonical ones are present in order, or (b) the contract designates a convention for domain-specific sections (e.g. subsection under Approach, or appendix block after Discovery context). The evaluator implements whichever rule is chosen. Future task specs have a documented place to put reference tables.
Approach
Section titled “Approach”- Pick the convention. Recommend (a) — allow arbitrary extra H2 sections as long as canonical ones appear in order — since it imposes the least burden on task authors.
- Update the evaluator’s section-walking logic to skip unrecognized H2 sections rather than misalign or error.
- Document the convention in
plugin/entities/task/implementation-ready.md. - Add an eval case: a task with an interleaved domain-specific section passes readiness.
Files to touch
Section titled “Files to touch”plugin/skills/task-ensure-ready/SKILL.md— section-walk logic.plugin/entities/task/implementation-ready.md— document the convention.plugin/skills/task-ensure-ready/tests/— new fixture with an interleaved section.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: A task whose body contains a non-canonical H2 between
canonical ones (e.g.
## Migration mappingbetween Approach and Files to touch) passes/sdlc:task-ensure-readywithout manual intervention. - AC-2: The convention is documented in
plugin/entities/task/implementation-ready.md.
Out of scope
Section titled “Out of scope”- Adding a registry of “blessed” domain-specific section names. The convention is structural (where they live), not by-name.
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”Spawned by /sdlc:task-work post-mortem of T-T5RB-consolidate-task-status-enum on 2026-05-19.