Skip to content

T-6S2N-path-citations-tolerate-basename-suffix

Status: closed/superseded · Impact: medium · Complexity: small

The implementation-ready gate’s path claim-resolver treats an imprecise prose path citation in a non-required narrative section (e.g. ## Discovery context) as a disqualifier, which nearly downshifted a materially-ready spec to planning/needs-definition over a one-word path imprecision. This task closes that gap in the SDLC plugin’s implementation-ready checker (and/or /sdlc:task-auto-define), originating from T-8ZKX-retire-legacy-vaultdashboard-component in https://github.com/sksizer/markdown-contract.

From the originating task’s post-mortem:

The implementation-ready gate disqualified a materially-ready task because a prose path citation in the non-required ## Discovery context section named ‘pages/index.stories.ts’ instead of the repo-root-relative ‘apps/daemon-web-prototype/pages/index.stories.ts’. Fix options: have /sdlc:task-auto-define emit repo-root-relative paths in prose citations, and/or have the implementation-ready path claim-resolver treat a unique-basename suffix match as satisfied — or at least demote the finding from disqualifier to warning — in non-required narrative sections.

TBD — receiver to fill before promoting from planning/draft.

TBD — receiver to fill before promoting from planning/draft.

TBD — receiver to fill before promoting from planning/draft.

TBD — receiver to fill before promoting from planning/draft.

TBD — receiver to fill before promoting from planning/draft.

  • none
  • none

Spawned by /sdlc:spawn-task-pr on 2026-07-04 UTC from T-8ZKX-retire-legacy-vaultdashboard-component in https://github.com/sksizer/markdown-contract.


← Back to Tasks