Skip to content

Commit 2f6c7b1

Browse files
committed
fix(extensions): resolve residual EARS keyword contradiction in author guardrails
The author command's Guardrails section still said "exactly one EARS pattern keyword; no compound requirements", contradicting the EARS Reference section above it (which allows complex requirements that combine multiple pattern keywords). Reworded to match lint.md/convert.md and clarify that "compound" (multiple behaviors joined by and/commas) is a different concept from "complex" (one behavior expressed with combined pattern keywords). Found while verifying commit 700d717 fully resolves all review threads on PR #3324. Assisted-by: GitHub Copilot (model: claude-sonnet-5, autonomous)
1 parent 700d717 commit 2f6c7b1

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎extensions/ears/commands/speckit.ears.author.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,6 @@ After resolution, set `EARS_SLUG` and `EARS_DIR = .specify/ears/<EARS_SLUG>`.
112112
## Guardrails
113113

114114
- Ground every requirement in the provided input. Do not invent scope; mark unknowns as `[NEEDS CLARIFICATION]`.
115-
- Every requirement uses `shall` and exactly one EARS pattern keyword; no compound requirements.
115+
- Every requirement uses `shall` and at least one EARS pattern keyword (simple requirements use exactly one; complex requirements may combine multiple). Split compound requirements — statements joined by "and"/commas — into separate requirements; this is distinct from a single complex requirement combining pattern keywords.
116116
- Write only inside `EARS_DIR`. Do not modify `spec.md` or any source file. You may offer to insert the generated block into an existing spec, but only apply it after explicit confirmation.
117117
- Never overwrite an existing `requirements.md` without confirmation.

0 commit comments

Comments
 (0)