diff options
Diffstat (limited to '.ai/workflows/spec-response.org')
| -rw-r--r-- | .ai/workflows/spec-response.org | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/.ai/workflows/spec-response.org b/.ai/workflows/spec-response.org index 99619cc..c659a0e 100644 --- a/.ai/workflows/spec-response.org +++ b/.ai/workflows/spec-response.org @@ -50,6 +50,22 @@ Trigger when: Not for: drafting a spec from scratch (that's a design conversation), or informal inline comments (handle those conversationally / via the cj-comment flow). +* Precondition: spec filename + +Before Phase 0, verify the spec being responded to ends with =-spec.org=. Every design, decision, or planning document under a project's =docs/= directory carries that suffix as its identifier. The =.org= extension alone is not enough because =docs/= holds non-spec org files too. + +If the spec does not end with =-spec.org=, stop immediately and surface the mismatch: + +#+begin_example +The spec <path> does not end with -spec.org. Either the wrong file was named, or +the file should be renamed first. Spec workflows require the -spec.org suffix as a +guard against pointing the workflow at tutorial, inventory, or setup docs. +#+end_example + +The review file the response consumes follows the convention =<spec-basename>-review.org=, so a misnamed spec produces a mis-pointed review file too. Fix the spec name first. + +The user resolves the mismatch and re-invokes the workflow. Do not proceed with the response against a misnamed spec. + * Approach: How We Work Together ** Phase 0: Orient |