@guilhermefsousa/open-spec-kit 0.0.8 → 0.0.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -191,10 +191,11 @@ Minimum expected terms for any project:
|
|
|
191
191
|
**Regras** (table format):
|
|
192
192
|
- Columns: ID | Regra | Fonte | Verificavel
|
|
193
193
|
- ID: sequential (RN-01, RN-02, ...)
|
|
194
|
-
- **Fonte**: MUST reference the
|
|
194
|
+
- **Fonte**: MUST reference the document and section the rule was extracted from. This enables traceability.
|
|
195
195
|
- Verificavel: how to test this rule (concrete, not vague)
|
|
196
|
-
- Group rules by domain area (ownership, auth, entities, etc.)
|
|
197
|
-
-
|
|
196
|
+
- Group rules by domain area (ownership, auth, entities, messaging, etc.)
|
|
197
|
+
- **CRITICAL: extract rules from EVERY page in Demandas/ — not just one.** Every child page read in Step 1f is a source of rules. Business documents, technical documents, data modeling, messaging contracts — all of them contain constraints that must become numbered rules.
|
|
198
|
+
- After writing all rules, **re-read EVERY page in Demandas/** looking for "deve", "nao pode", "obrigatorio", "somente", "exclusivamente", "UNIQUE", "constraint" — any missed rule must be added
|
|
198
199
|
|
|
199
200
|
**Fluxos**:
|
|
200
201
|
- One section per business flow
|