π« Toolkit to help you get started with SDD or any other process!
fix(commands): rename NFR references to success criteria in analyze and clarify (#1935)
Ismael816c1160e92a
diff --git a/templates/commands/analyze.md b/templates/commands/analyze.mdindex 827d4e4ca..b3174338d 100644--- a/templates/commands/analyze.md+++ b/templates/commands/analyze.md@@ -44,7 +44,7 @@ Load only the minimal necessary context from each artifact:- Overview/Context- Functional Requirements-- Non-Functional Requirements+- Success Criteria (measurable outcomes β e.g., performance, security, availability, user success, business impact)- User Stories- Edge Cases (if present)@@ -71,7 +71,7 @@ Load only the minimal necessary context from each artifact:Create internal representations (do not include raw artifacts in output):-- **Requirements inventory**: Each functional + non-functional requirement with a stable key (derive slug based on imperative phrase; e.g., "User can upload file" β `user-can-upload-file`)+- **Requirements inventory**: For each Functional Requirement (FR-###) and Success Criterion (SC-###), record a stable key. Use the explicit FR-/SC- identifier as the primary key when present, and optionally also derive an imperative-phrase slug for readability (e.g., "User can upload file" β `user-can-upload-file`). Include only Success Criteria items that require buildable work (e.g., load-testing infrastructure, security audit tooling), and exclude post-launch outcome metrics and business KPIs (e.g., "Reduce support tickets by 50%").- **User story/action inventory**: Discrete user actions with acceptance criteria- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword / explicit reference patterns like IDs or key phrases)- **Constitution rule set**: Extract principle names and MUST/SHOULD normative statements@@ -105,7 +105,7 @@ Focus on high-signal findings. Limit to 50 findings total; aggregate remainder i- Requirements with zero associated tasks- Tasks with no mapped requirement/story-- Non-functional requirements not reflected in tasks (e.g., performance, security)+- Success Criteria requiring buildable work (performance, security, availability) not reflected in tasks#### F. Inconsistencydiff --git a/templates/commands/clarify.md b/templates/commands/clarify.mdindex 196fa2c0f..26efb5aed 100644--- a/templates/commands/clarify.md+++ b/templates/commands/clarify.md@@ -145,7 +145,7 @@ Execution steps:- Functional ambiguity β Update or add a bullet in Functional Requirements.- User interaction / actor distinction β Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.- Data shape / entities β Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.- - Non-functional constraint β Add/modify measurable criteria in Non-Functional / Quality Attributes section (convert vague adjective to metric or explicit target).+ - Non-functional constraint β Add/modify measurable criteria in Success Criteria > Measurable Outcomes (convert vague adjective to metric or explicit target).- Edge case / negative flow β Add a new bullet under Edge Cases / Error Handling (or create such subsection if template provides placeholder for it).- Terminology conflict β Normalize term across spec; retain original only if necessary by adding `(formerly referred to as "X")` once.- If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.