@guilhermefsousa/open-spec-kit 0.0.10 → 0.0.11

package/templates/agents/skills/specifying-features/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: specifying-features
+name: osk-spec
 description: "Breaks an approved PRD into N feature specifications with brief, scenarios (Given/When/Then), contracts, and repo-partitioned tasks. Generates/updates Design Document on Confluence."
 metadata:
   works_on: [copilot, antigravity, claude]
@@ -16,11 +16,11 @@ Take an approved PRD and produce minimal, unambiguous feature specifications tha
 
 ### Validate prerequisites
 
-1. Read `projects.yml` — if empty, **stop** with message: "/setup não foi executado."
-2. Read `docs/architecture.md` — if file does not exist: **stop** — "/setup não gerou architecture.md. Execute /setup primeiro."
-3. In Confluence (via MCP — same as /setup), find the feature page and check its labels:
-   - If label `prd-aprovado` is NOT present: **stop** — "PRD não aprovado. A feature precisa ter label 'prd-aprovado' antes de rodar /spec. Execute /discovery primeiro."
-   - If label `prd-rejeitado` is present AND its addition date is MORE RECENT than `prd-aprovado` (check via MCP — page metadata or label timestamps): **stop** — "PRD foi rejeitado após aprovação. Execute /discovery para resolver antes de prosseguir."
+1. Read `projects.yml` — if empty, **stop** with message: "/osk-init não foi executado."
+2. Read `docs/architecture.md` — if file does not exist: **stop** — "/osk-init não gerou architecture.md. Execute /osk-init primeiro."
+3. In Confluence (via MCP — same as /osk-init), find the feature page and check its labels:
+   - If label `prd-aprovado` is NOT present: **stop** — "PRD não aprovado. A feature precisa ter label 'prd-aprovado' antes de rodar /osk-spec. Execute /osk-discover primeiro."
+   - If label `prd-rejeitado` is present AND its addition date is MORE RECENT than `prd-aprovado` (check via MCP — page metadata or label timestamps): **stop** — "PRD foi rejeitado após aprovação. Execute /osk-discover para resolver antes de prosseguir."
    - If `prd-aprovado` IS present and no subsequent `prd-rejeitado`: proceed
 4. Read the feature page content — verify it has a "## PRD" section with "### Requisitos aceitos". If not: **stop** — "PRD não encontrado na página da feature."
 5. **Idempotency check**: if `specs/` already contains a directory for this feature (matching name or Confluence page ID in links.md):
@@ -46,8 +46,8 @@ Read these files FIRST:
 **Figma freshness check (if Figma configured):**
 If `projects.yml` has `figma.file_url` and Figma MCP is available:
 1. Read `get_metadata()` for the feature's frames
-2. Compare key elements (screen count, form fields) against what /discovery captured in the PRD
-3. If significant changes detected (new screens, removed fields) → WARN: "Design no Figma mudou desde o /discovery. Diferenças: {list}. Continuar com o design atual ou re-executar /discovery?"
+2. Compare key elements (screen count, form fields) against what /osk-discover captured in the PRD
+3. If significant changes detected (new screens, removed fields) → WARN: "Design no Figma mudou desde o /osk-discover. Diferenças: {list}. Continuar com o design atual ou re-executar /osk-discover?"
 4. If no changes or Figma unavailable → proceed silently
 
 ## Inputs
@@ -80,8 +80,8 @@ Numbering is sequential: find the highest existing number in `specs/` and increm
 ### 3. Write specs (per feature)
 
 > **⚠️ MANDATORY: generate ALL 5 files per feature — `brief.md`, `scenarios.md`, `contracts.md`, `tasks.md`, `links.md`.**
-> `/dev` rejects specs with missing files (checks in Phase A). `open-spec-kit validate` fails on Rule-01 if any of the 5 are absent.
-> `links.md` is frequently forgotten because it's the smallest — it is **mandatory** and `/dev` depends on it to track post-merge PRs.
+> `/osk-build` rejects specs with missing files (checks in Phase A). `open-spec-kit validate` fails on Rule-01 if any of the 5 are absent.
+> `links.md` is frequently forgotten because it's the smallest — it is **mandatory** and `/osk-build` depends on it to track post-merge PRs.
 
 **MANDATORY LANGUAGE for ALL generated files**: Brazilian Portuguese (pt-BR) with correct accents. This includes code comments, Gherkin descriptions, and free text. Examples: "não" NOT "nao", "autenticação" NOT "autenticacao", "código" NOT "codigo", "é" NOT "e", "já" NOT "ja", "número" NOT "numero", "válido" NOT "valido", "obrigatório" NOT "obrigatorio", "mínimo" NOT "minimo". Technical terms stay in English (endpoint, token, hash, bcrypt, JWT).
 
@@ -142,7 +142,7 @@ Numbering is sequential: find the highest existing number in `specs/` and increm
 - **NFR scenarios (if PRD has "Requisitos Não-Funcionais")**: for each measurable NFR target (e.g., "GET /bills < 200ms p95"), create at least one CT-NNN-XX scenario with a concrete Given/When/Then. Example: `Given 50 concurrent users, When GET /api/v1/bills with filters, Then p95 response time < 200ms`. If the NFR is not measurable in a test (e.g., "99.9% uptime"), include it in brief.md under "Restrições" instead. Add NFR-related tasks to tasks.md (e.g., "add response time middleware", "configure rate limiting").
 - **No unresolved markers (MANDATORY)**: specs MUST NOT contain any of these markers anywhere — including inside code blocks and code examples:
   `MOCKADO`, `TODO`, `A CONFIRMAR`, `TBD`, `FIXME`, `PLACEHOLDER`, `TKTK`
-  If any assumption is not validated, go back to /discovery to resolve it.
+  If any assumption is not validated, go back to /osk-discover to resolve it.
   The `open-spec-kit validate` command will ERROR on any unresolved marker.
 - **Cross-spec dependencies are NOT REQs**: if a feature uses an entity or type defined in another spec, do NOT create a REQ for it. Instead, use a `> Dependency:` block in the brief:
   `> Dependency: Uses entity Tutor defined in specs/002 (see contracts.md of feature 002)`
@@ -181,7 +181,7 @@ Additional rules:
 #### tasks.md
 - **IMPORTANT**: use the EXACT repo name as declared in `projects.yml` as heading `## repo-name`. E.g., `## todo-app-api`, NOT `## Backend`. The `open-spec-kit validate` command checks that headings match repos from projects.yml (Rule 21).
 - Group tasks by repo (from `projects.yml`) — each `## repo` heading is one **execution unit** (1 agent or 1 dev)
-- **Validate repos**: every repo referenced in tasks.md MUST exist in `projects.yml`. If a task references a repo not in projects.yml, **add it** with `status: planned` and `url: null`. The /dev will auto-create it in Phase A.1. Log: "Repo '{name}' adicionado ao projects.yml com status: planned."
+- **Validate repos**: every repo referenced in tasks.md MUST exist in `projects.yml`. If a task references a repo not in projects.yml, **add it** with `status: planned` and `url: null`. The /osk-build will auto-create it in Phase A.1. Log: "Repo '{name}' adicionado ao projects.yml com status: planned."
 - Within each `## repo` block, list tasks in execution order — the list order IS the dependency order (no need to annotate dependencies between tasks of the same block)
 - **Parallelism between blocks**: if a repo block depends ONLY on contracts (already defined in contracts.md) and NOT on the implementation of another block, mark with `[P]` — it can start in parallel. Example: `### todo-front [P] — can start after contracts are defined`
 - **Dependency between blocks**: if a repo block REQUIRES another block to be COMPLETED first, declare explicitly with `> Dependency: todo-api block must be completed before starting`
@@ -192,11 +192,11 @@ Additional rules:
   - M (médio): 2-8h, multiple files, may need investigation
   - G (grande): > 8h, complex logic, new patterns, integration work
   - Format: `- [ ] [P] T-NNN-REPO-XX: description (REQ-NNN)`
-- **Feature grande**: if the PRD has more than 15 behaviors/requirements or spans 4+ repos, /discovery should have flagged it already. If it arrived here approved, proceed without questioning. Just note in brief.md: "Feature com {N} requisitos — escopo aprovado pelo PO."
+- **Feature grande**: if the PRD has more than 15 behaviors/requirements or spans 4+ repos, /osk-discover should have flagged it already. If it arrived here approved, proceed without questioning. Just note in brief.md: "Feature com {N} requisitos — escopo aprovado pelo PO."
 
 #### links.md
 - Link to Confluence feature page
-- Empty PR table with this schema (filled by /dev during implementation):
+- Empty PR table with this schema (filled by /osk-build during implementation):
 
 ```markdown
 ## PRs
@@ -205,7 +205,7 @@ Additional rules:
 |------|--------|-------|--------|
 ```
 
-Status values: `open`, `em-review`, `merged`, `closed`. The /dev uses the Status column to detect merged MRs for post-merge Phase D.
+Status values: `open`, `em-review`, `merged`, `closed`. The /osk-build uses the Status column to detect merged MRs for post-merge Phase D.
 
 #### ✅ Artifact checklist (MANDATORY — verify before proceeding to self-review)
 
@@ -215,7 +215,7 @@ Confirm you generated all **5 files** for this feature:
 - [ ] `scenarios.md` — Given/When/Then per behavior
 - [ ] `contracts.md` — endpoints, entities, enums, rules
 - [ ] `tasks.md` — checklist per repo (use EXACT repo name from projects.yml as heading `##`)
-- [ ] `links.md` — Confluence URL + PR table ← **frequently forgotten; /dev depends on this file**
+- [ ] `links.md` — Confluence URL + PR table ← **frequently forgotten; /osk-build depends on this file**
 
 If any file is missing, **create it now** before continuing.
 
@@ -226,7 +226,7 @@ If contracts.md defines REST endpoints, generate a minimal OpenAPI 3.0 stub file
 - request/response schemas (from contract types)
 - auth scheme (if authenticated endpoints: bearerAuth)
 
-This is a STUB — /dev may extend it during implementation. Mark as draft: `info.description: "Auto-generated from contracts.md — draft"`
+This is a STUB — /osk-build may extend it during implementation. Mark as draft: `info.description: "Auto-generated from contracts.md — draft"`
 
 If the feature has no REST endpoints (e.g., worker-only feature), skip this step.
 
@@ -276,23 +276,23 @@ Result values:
 - ⚠️ = partially passing, documented exceptions (include reason)
 - ❌ = failing — MUST be fixed before proceeding (this state should not appear in the final report since all failures are fixed first)
 
-The /dev reads this report in Phase A before starting implementation. If it contains ⚠️ items, the dev evaluates whether to proceed or request spec changes.
+The /osk-build reads this report in Phase A before starting implementation. If it contains ⚠️ items, the dev evaluates whether to proceed or request spec changes.
 
 ### 5. Validate Glossary on Confluence (read-only)
 
-> **Ownership rule**: the Glossário is updated ONLY by /discovery (exit gate). The /spec only VALIDATES.
+> **Ownership rule**: the Glossário is updated ONLY by /osk-discover (exit gate). The /osk-spec only VALIDATES.
 
-Check if the /discovery phase identified new terms (see "GLOSSÁRIO" notes on the feature page or in the PRD). If yes:
+Check if the /osk-discover phase identified new terms (see "GLOSSÁRIO" notes on the feature page or in the PRD). If yes:
 1. Read the current Glossário on Confluence (in storage format)
 2. Verify that ALL new terms listed in the PRD section "GLOSSÁRIO: termos novos" are present in the Glossário page
-3. **If any term is MISSING**: **stop** — "Glossário incompleto. O /discovery deveria ter adicionado os termos '{missing}' no exit gate. Re-execute /discovery para corrigir."
+3. **If any term is MISSING**: **stop** — "Glossário incompleto. O /osk-discover deveria ter adicionado os termos '{missing}' no exit gate. Re-execute /osk-discover para corrigir."
 4. **If all terms are present**: proceed (no update needed)
 
-Do NOT add terms directly — this is /discovery's responsibility.
+Do NOT add terms directly — this is /osk-discover's responsibility.
 
 ### 6. Generate/update Design Document on Confluence
 
-> **Ownership rule**: the DD is owned by the `design-doc` agent (Labs). The /spec delegates creation/update to it. Only uses MCP directly as a fallback.
+> **Ownership rule**: the DD is owned by the `design-doc` agent (Labs). The /osk-spec delegates creation/update to it. Only uses MCP directly as a fallback.
 
 Read `projects.yml` → `agents.design_doc`. If configured (not null), use that agent to generate or update the DD on Confluence with:
 - Updated architecture (if feature adds components)
@@ -333,7 +333,7 @@ Read `projects.yml` → `agents.design_doc`. If configured (not null), use that
       • tasks.md — {task_count} tasks por repo
 
       📊 <b>Cobertura:</b> {req_count} REQs → {scenario_count} cenários" \
-        --next "Review técnico antes de iniciar /dev" \
+        --next "Review técnico antes de iniciar /osk-build" \
         --button-text "Ver spec no Confluence" \
         --button-url "{feature_page_url}"
 
@@ -404,7 +404,7 @@ If a Confluence operation fails mid-flow (updating DD, changing labels, reading
 ### Integration
 - [ ] DD updated on Confluence
 - [ ] Glossary validated on Confluence (all PRD terms present)
-- [ ] All open decisions in architecture.md resolved (no blockers for /dev)
+- [ ] All open decisions in architecture.md resolved (no blockers for /osk-build)
 - [ ] Feature label updated on Confluence → `em-spec`
 - [ ] All spec files committed and pushed
 - [ ] GChat notification sent
@@ -412,10 +412,10 @@ If a Confluence operation fails mid-flow (updating DD, changing labels, reading
 
 ## Exit gate (BLOCKING — cannot close the loop without these)
 
-The /spec CANNOT be considered done until ALL of the following are true. If any item fails, fix it before moving to /dev.
+The /osk-spec CANNOT be considered done until ALL of the following are true. If any item fails, fix it before moving to /osk-build.
 
 1. **Design Document exists and is updated on Confluence** — the DD page MUST exist under the project root. If it doesn't exist, create it. If it exists, add/update the section for this feature. NEVER skip this step. Verify by reading the DD page after updating.
-2. **Glossary validated** — if any feature PRD has a "GLOSSÁRIO: termos novos" section, ALL listed terms MUST be present in the Glossário page. Read the Glossário page and verify. If any term is MISSING: **stop** — "Glossário incompleto. Re-execute /discovery para adicionar os termos faltantes." The /spec does NOT add terms — it only validates that /discovery did its job.
-3. **All decisions resolved** — read `docs/architecture.md` "Decisões em Aberto" section. If ANY decision is still open that blocks /dev, the /spec CANNOT close. Technical decisions can be resolved by the dev team. Business decisions must go back to the PO. If an open decision needs resolution, go back to /discovery — the /spec does not resolve decisions, only validates.
+2. **Glossary validated** — if any feature PRD has a "GLOSSÁRIO: termos novos" section, ALL listed terms MUST be present in the Glossário page. Read the Glossário page and verify. If any term is MISSING: **stop** — "Glossário incompleto. Re-execute /osk-discover para adicionar os termos faltantes." The /osk-spec does NOT add terms — it only validates that /osk-discover did its job.
+3. **All decisions resolved** — read `docs/architecture.md` "Decisões em Aberto" section. If ANY decision is still open that blocks /osk-build, the /osk-spec CANNOT close. Technical decisions can be resolved by the dev team. Business decisions must go back to the PO. If an open decision needs resolution, go back to /osk-discover — the /osk-spec does not resolve decisions, only validates.
 4. **Self-review completed** — the traceability matrix (REQ → CT, CT → REQ) MUST be verified. Report what was checked and any fixes applied. Do NOT skip silently.
 5. **Commit and push** — all spec files MUST be committed and pushed to the spec repo before closing. Verify with `git status` that working directory is clean.

package/templates/github/agents/spec-hub.agent.md

@@ -1,6 +1,6 @@
 ---
 name: spec-agent
-description: "Orquestra o ciclo de especificação: invoca skills (/setup, /discovery, /spec, /dev) e coordena agents do Labs."
+description: "Orquestra o ciclo de especificação: invoca skills (/osk-init, /osk-discover, /osk-spec, /osk-build) e coordena agents do Labs."
 user-invocable: true
 disable-model-invocation: false
 tools:
@@ -47,10 +47,10 @@ Cada skill tem instruções completas em `.agents/skills/*/SKILL.md`:
 
 | Skill | Prompt file | O que faz |
 |-------|-------------|-----------|
-| Setup | `/setup` | Bootstrap do projeto a partir do Confluence |
-| Discovery | `/discovery` | Análise de demanda, Q&A com PO, gera PRD |
-| Spec | `/nova-feature` | Quebra PRD em specs técnicas (brief, cenários, contratos, tasks) |
-| Dev | `/dev` | Orquestra implementação (TDD, MR, security, docs vivas) |
+| Setup | `/osk-init` | Bootstrap do projeto a partir do Confluence |
+| Discovery | `/osk-discover` | Análise de demanda, Q&A com PO, gera PRD |
+| Spec | `/osk-spec` | Quebra PRD em specs técnicas (brief, cenários, contratos, tasks) |
+| Dev | `/osk-build` | Orquestra implementação (TDD, MR, security, docs vivas) |
 
 ## Sub-agents
 

package/templates/github/copilot-instructions.md

@@ -25,10 +25,10 @@ Invoke via prompt files (digite `/` no chat):
 
 | Comando | Skill | O que faz |
 |---------|-------|-----------|
-| `/setup` | setup-project | Bootstrap do projeto a partir do Confluence |
-| `/discovery` | discovery | Análise de demanda, Q&A com PO, gera PRD |
-| `/nova-feature` | specifying-features | Quebra PRD em specs técnicas |
-| `/dev` | dev-orchestrator | Orquestra implementação TDD |
+| `/osk-init` | osk-init | Bootstrap do projeto a partir do Confluence |
+| `/osk-discover` | osk-discover | Análise de demanda, Q&A com PO, gera PRD |
+| `/osk-spec` | osk-spec | Quebra PRD em specs técnicas |
+| `/osk-build` | osk-build | Orquestra implementação TDD |
 
 Cada prompt file aponta para o SKILL.md completo em `.agents/skills/*/SKILL.md`.
 
@@ -75,12 +75,12 @@ Este projeto suporta Claude Code e Copilot. Ao modificar agents, rules ou skills
 
 ```
 Projeto (Space ou página raiz)
-+-- Visão do Produto        <- /setup gera
-+-- Glossário               <- /setup gera | /discovery e /dev atualizam
-+-- DD (Design Document)    <- design-doc agent gera | /dev atualiza
++-- Visão do Produto        <- /osk-init gera
++-- Glossário               <- /osk-init gera | /osk-discover e /osk-build atualizam
++-- DD (Design Document)    <- design-doc agent gera | /osk-build atualiza
 +-- Demandas/               <- PO joga docs aqui
-+-- Features/               <- /setup cria | /discovery escreve dúvidas + PRD
-+-- Domínio/                <- /setup gera | /dev atualiza
++-- Features/               <- /osk-init cria | /osk-discover escreve dúvidas + PRD
++-- Domínio/                <- /osk-init gera | /osk-build atualiza
 |   +-- Regras
 |   +-- Fluxos
 |   +-- Tabelas de Referência

package/templates/github/instructions/hub_structure.instructions.md

@@ -23,7 +23,7 @@ applyTo: "specs/**,docs/**,projects.yml"
 | `contracts.md` | Schemas, tipos, regras de negócio |
 | `tasks.md` | Tarefas por repo (1 task = 1 PR) |
 | `links.md` | Tracking de PRs + link Confluence |
-| `audit-report.md` | Resultado do self-review do /spec |
+| `audit-report.md` | Resultado do self-review do /osk-spec |
 | `conformance-report.json` | Validação de conformidade pós-implementação |
 
 ## Regras

package/templates/github/instructions/ownership.instructions.md

@@ -19,15 +19,15 @@ Antes de criar ou modificar qualquer artefato, leia `.agents/rules/ownership.ins
 
 | Artefato | Owner | Updater |
 |----------|-------|---------|
-| `projects.yml` | /setup | /spec, /dev |
-| `docs/architecture.md` | /setup | /discovery |
-| `specs/NNN/brief.md` | /spec | — |
-| `specs/NNN/scenarios.md` | /spec | — |
-| `specs/NNN/contracts.md` | /spec | — |
-| `specs/NNN/tasks.md` | /spec | — |
-| `specs/NNN/links.md` | /spec | /dev |
-| `specs/NNN/audit-report.md` | /spec | — |
-| `specs/NNN/conformance-report.json` | /dev | — |
+| `projects.yml` | /osk-init | /osk-spec, /osk-build |
+| `docs/architecture.md` | /osk-init | /osk-discover |
+| `specs/NNN/brief.md` | /osk-spec | — |
+| `specs/NNN/scenarios.md` | /osk-spec | — |
+| `specs/NNN/contracts.md` | /osk-spec | — |
+| `specs/NNN/tasks.md` | /osk-spec | — |
+| `specs/NNN/links.md` | /osk-spec | /osk-build |
+| `specs/NNN/audit-report.md` | /osk-spec | — |
+| `specs/NNN/conformance-report.json` | /osk-build | — |
 
 ## Labels de feature (fluxo sequencial)