T-RV1F-ground-approach-file-citations
Status: closed/superseded · Impact: medium · Complexity: small
Close a gap surfaced on T-1TA2-repeatable-sections-as-collections in
https://github.com/sksizer/markdown-contract: /sdlc:task-auto-define should
ground the ## Approach file citations it writes against the target codebase,
so a synthesized spec points at the real edit site instead of a
plausible-but-wrong path.
task-auto-define writes the task spec’s ## Approach file citations from the task’s prose without grounding them against the codebase. On T-1TA2 the Approach cited declarative/schema.ts for the DSL change, but the section-structure DSL actually compiles in declarative/body.ts (schema.ts is the value-schema Zod compiler); the readiness gate’s path-claim resolver flagged the abbreviated citations and the true edit site only surfaced on reading the code. Auto-define should resolve each cited path against the repo and prefer the module that actually contains the named responsibility, so specs point at the real edit site.
—
T-1TA2-repeatable-sections-as-collections
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-04 UTC from
T-1TA2-repeatable-sections-as-collections in
https://github.com/sksizer/markdown-contract.