@guilhermefsousa/open-spec-kit 0.0.9 → 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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/templates/agents/skills/setup-project/SKILL.md +3 -3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@guilhermefsousa/open-spec-kit",
3
- "version": "0.0.9",
3
+ "version": "0.0.10",
4
4
  "description": "CLI para spec-driven development com suporte a Claude Code e GitHub Copilot",
5
5
  "type": "module",
6
6
  "bin": {
package/templates/agents/skills/setup-project/SKILL.md CHANGED
@@ -191,11 +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 document and section the rule was extracted from (ex: "Regra de Negocio §9", "PadroesArquitetura §4.2", "Contratos de Mensageria §1"). This enables traceability.
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
196
  - Group rules by domain area (ownership, auth, entities, messaging, etc.)
197
- - **CRITICAL: extract rules from ALL documents in Demandas/, not just the business rules document.** Technical documents (architecture, messaging contracts, data modeling) contain rules too — idempotency constraints, retry patterns, DLQ handling, message format rules, authentication requirements, LGPD constraints. These are business rules expressed in technical language.
198
- - After writing all rules, **re-read ALL PO documents** (every single page in Demandas/) looking for "deve", "nao pode", "obrigatorio", "somente", "exclusivamente", "UNIQUE", "constraint", "obrigatorio" — any missed rule must be added
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
199
199
 
200
200
  **Fluxos**:
201
201
  - One section per business flow