@guilhermefsousa/open-spec-kit 0.0.10 → 0.0.11

package/templates/agents/rules/ownership.instructions.md

@@ -14,52 +14,52 @@ This rule exists to prevent the "duplicate responsibility" anti-pattern where mu
 
 | Artifact | Owner (creates) | Updater | Readers | Validators |
 |----------|----------------|---------|---------|------------|
-| Demandas/ labels | /setup | — | /discovery | — |
-| Visão do Produto | /setup | — | all | — |
-| Glossário | /setup | /discovery (exit gate), /dev (post-merge only) | /spec | /spec (read-only validate) |
-| DD (Design Document) | /spec (via `design-doc` agent) | /dev (post-merge, via `design-doc` agent) | — | — |
-| Domínio/Regras | /setup | /dev (post-merge only) | /discovery, /spec | — |
-| Domínio/Fluxos | /setup | /dev (post-merge only) | /discovery | — |
-| Domínio/Tabelas | /setup | — | /discovery | — |
-| Domínio/Integrações | /setup | /dev (post-merge only) | /discovery | — |
-| Features/ (parent) | /setup | — | all | — |
-| Feature pages (content) | /setup + /discovery | /discovery | /spec, /dev | — |
+| Demandas/ labels | /osk-init | — | /osk-discover | — |
+| Visão do Produto | /osk-init | — | all | — |
+| Glossário | /osk-init | /osk-discover (exit gate), /osk-build (post-merge only) | /osk-spec | /osk-spec (read-only validate) |
+| DD (Design Document) | /osk-spec (via `design-doc` agent) | /osk-build (post-merge, via `design-doc` agent) | — | — |
+| Domínio/Regras | /osk-init | /osk-build (post-merge only) | /osk-discover, /osk-spec | — |
+| Domínio/Fluxos | /osk-init | /osk-build (post-merge only) | /osk-discover | — |
+| Domínio/Tabelas | /osk-init | — | /osk-discover | — |
+| Domínio/Integrações | /osk-init | /osk-build (post-merge only) | /osk-discover | — |
+| Features/ (parent) | /osk-init | — | all | — |
+| Feature pages (content) | /osk-init + /osk-discover | /osk-discover | /osk-spec, /osk-build | — |
 | Feature labels | each skill at its transition | — | all | — |
-| Arquivados/ | /setup | — | — | — |
+| Arquivados/ | /osk-init | — | — | — |
 
-**Glossário conflict rule**: if /dev (post-merge) needs to update a term that /discovery defined, /dev's update wins — it reflects implemented reality. /dev adds a note: "Atualizado pós-merge: {reason}".
+**Glossário conflict rule**: if /osk-build (post-merge) needs to update a term that /osk-discover defined, /osk-build's update wins — it reflects implemented reality. /osk-build adds a note: "Atualizado pós-merge: {reason}".
 
-**DD update coordination**: /spec updates the DD FIRST (during spec phase), /dev updates AFTER MERGE (during Phase D). If /dev needs to change something /spec wrote, /dev overwrites with implemented reality (code is source of truth post-merge). No locking needed — the sequential workflow prevents simultaneous updates.
+**DD update coordination**: /osk-spec updates the DD FIRST (during spec phase), /osk-build updates AFTER MERGE (during Phase D). If /osk-build needs to change something /osk-spec wrote, /osk-build overwrites with implemented reality (code is source of truth post-merge). No locking needed — the sequential workflow prevents simultaneous updates.
 
 ## Local Artifacts
 
 | Artifact | Owner (creates) | Updater | Readers | Validators |
 |----------|----------------|---------|---------|------------|
-| `projects.yml` | /setup | /spec (adds planned repos), /dev (repo URLs + status) | all | — |
-| `docs/architecture.md` | /setup | /discovery (resolves decisions), /dev (adds resolved decisions post-merge) | /spec, /dev | /spec (validates no blockers) |
-| `docs/lessons/` | /dev | /dev | all | — |
+| `projects.yml` | /osk-init | /osk-spec (adds planned repos), /osk-build (repo URLs + status) | all | — |
+| `docs/architecture.md` | /osk-init | /osk-discover (resolves decisions), /osk-build (adds resolved decisions post-merge) | /osk-spec, /osk-build | /osk-spec (validates no blockers) |
+| `docs/lessons/` | /osk-build | /osk-build | all | — |
 | `docs/decisions/` | manual / spec-agent | — | all | — |
 | `docs/pending-confluence-updates.md` | any skill (on MCP failure) | any skill (on retry) | all | — |
-| `specs/NNN/brief.md` | /spec | — | /dev | — |
-| `specs/NNN/scenarios.md` | /spec | /dev (post-merge sync D.1.5 — only if conformance report shows intentional divergence) | /dev | — |
-| `specs/NNN/contracts.md` | /spec | /dev (post-merge sync D.1.5 — only if conformance report shows intentional divergence) | /dev | — |
-| `specs/NNN/tasks.md` | /spec | — | /dev | — |
-| `specs/NNN/links.md` | /spec (template) | /dev (MR links) | — | — |
-| `specs/NNN/audit-report.md` | /spec (self-review) | — | /dev (reads before Phase B, blocks if ❌) | — |
-| `specs/NNN/openapi.yaml` | /spec (optional, if REST endpoints) | /dev (may extend) | — | — |
-| `specs/NNN/conformance-report.json` | /dev (Phase C.3) | /dev (overwrites per run) | CI Guard | — |
-| `specs/NNN/conformance-history.log` | /dev (Phase C.3) | /dev (appends per run) | — | — |
-| `CHANGELOG.md` (impl repo) | /dev (Phase D.4.5) | /dev | all | — |
-
-**Conformance versioning**: `conformance-report.json` is overwritten on each /dev run. To preserve history, /dev appends a summary line to `specs/NNN/conformance-history.log`: `{timestamp} | {result} | {matching}/{total} endpoints | {matching}/{total} fields`
+| `specs/NNN/brief.md` | /osk-spec | — | /osk-build | — |
+| `specs/NNN/scenarios.md` | /osk-spec | /osk-build (post-merge sync D.1.5 — only if conformance report shows intentional divergence) | /osk-build | — |
+| `specs/NNN/contracts.md` | /osk-spec | /osk-build (post-merge sync D.1.5 — only if conformance report shows intentional divergence) | /osk-build | — |
+| `specs/NNN/tasks.md` | /osk-spec | — | /osk-build | — |
+| `specs/NNN/links.md` | /osk-spec (template) | /osk-build (MR links) | — | — |
+| `specs/NNN/audit-report.md` | /osk-spec (self-review) | — | /osk-build (reads before Phase B, blocks if ❌) | — |
+| `specs/NNN/openapi.yaml` | /osk-spec (optional, if REST endpoints) | /osk-build (may extend) | — | — |
+| `specs/NNN/conformance-report.json` | /osk-build (Phase C.3) | /osk-build (overwrites per run) | CI Guard | — |
+| `specs/NNN/conformance-history.log` | /osk-build (Phase C.3) | /osk-build (appends per run) | — | — |
+| `CHANGELOG.md` (impl repo) | /osk-build (Phase D.4.5) | /osk-build | all | — |
+
+**Conformance versioning**: `conformance-report.json` is overwritten on each /osk-build run. To preserve history, /osk-build appends a summary line to `specs/NNN/conformance-history.log`: `{timestamp} | {result} | {matching}/{total} endpoints | {matching}/{total} fields`
 
 ## Key Rules
 
 1. **One Owner per artifact** — each artifact has exactly one Owner that creates it. Updaters are explicitly designated in the matrix above with conditions (e.g., "post-merge only"). If a skill writes to an artifact where it is not listed as Owner or Updater, it is wrong.
 
-2. **Validate ≠ Update** — /spec validates the Glossário (checks all terms are present) but does NOT add terms. If terms are missing, it stops and asks the dev to re-run /discovery.
+2. **Validate ≠ Update** — /osk-spec validates the Glossário (checks all terms are present) but does NOT add terms. If terms are missing, it stops and asks the dev to re-run /osk-discover.
 
-3. **Post-merge = reality** — when /dev updates Confluence post-merge, it reflects what WAS IMPLEMENTED (merged code), not what was planned. If the implementation diverged from the spec, Confluence must match the code, not the spec.
+3. **Post-merge = reality** — when /osk-build updates Confluence post-merge, it reflects what WAS IMPLEMENTED (merged code), not what was planned. If the implementation diverged from the spec, Confluence must match the code, not the spec.
 
 4. **DD ownership** — the Design Document is owned by the `design-doc` agent (Labs). Skills delegate to it. Only use direct MCP as a fallback when the agent is unavailable.
 
@@ -87,7 +87,7 @@ This rule exists to prevent the "duplicate responsibility" anti-pattern where mu
 
 ## Label Transitions
 
-### Demandas/ labels (owned by /setup)
+### Demandas/ labels (owned by /osk-init)
 ```
 (none) → novo → processando → processado
 ```
@@ -100,16 +100,16 @@ em-discovery → aguardando-po → prd-review → prd-aprovado → em-spec → e
 ```
 
 - `prd-aprovado` is added by the **PO manually** (human gate)
-- `prd-rejeitado` is added by the **PO manually** (triggers /discovery re-run)
+- `prd-rejeitado` is added by the **PO manually** (triggers /osk-discover re-run)
 - All other labels are added by the respective skill automatically
 
 ## MCP Failure Recovery
 
 All 4 skills must handle MCP failures:
-- /setup: re-execution checks existing pages, creates only missing ones
-- /discovery: saves pending operations to `docs/pending-confluence-updates.md`
-- /spec: saves pending operations to `docs/pending-confluence-updates.md`
-- /dev: saves pending updates to `docs/pending-confluence-updates.md`, retries on next execution
+- /osk-init: re-execution checks existing pages, creates only missing ones
+- /osk-discover: saves pending operations to `docs/pending-confluence-updates.md`
+- /osk-spec: saves pending operations to `docs/pending-confluence-updates.md`
+- /osk-build: saves pending updates to `docs/pending-confluence-updates.md`, retries on next execution
 
 ## Architecture Decisions Format
 
@@ -121,7 +121,7 @@ The `docs/architecture.md` "Decisões em Aberto" table uses this schema:
 
 Status values: `aberta`, `resolvida — [decisão tomada]`
 
-/discovery updates this column during its exit gate. /dev may also add resolved decisions post-merge (Phase D.4) when new decisions are discovered during implementation. /spec validates that no `aberta` decision blocks /dev.
+/osk-discover updates this column during its exit gate. /osk-build may also add resolved decisions post-merge (Phase D.4) when new decisions are discovered during implementation. /osk-spec validates that no `aberta` decision blocks /osk-build.
 
 ## links.md PR Table Format
 
@@ -132,7 +132,7 @@ Status values: `aberta`, `resolvida — [decisão tomada]`
 |------|--------|-------|--------|
 ```
 
-Status values: `open`, `em-review`, `merged`, `closed`. Created empty by /spec, filled by /dev.
+Status values: `open`, `em-review`, `merged`, `closed`. Created empty by /osk-spec, filled by /osk-build.
 
 ## Shared Types Between Features
 
@@ -142,7 +142,7 @@ When `contracts.md` defines types that other features will reuse (e.g., ErrorRes
 
 ## Feature Scope Thresholds
 
-Both /discovery and /spec use the same criteria:
+Both /osk-discover and /osk-spec use the same criteria:
 - More than **15 behaviors/requirements** → flag as potentially large
 - Spans **4+ repos** → flag as potentially large
 - This is a suggestion, not a blocker. The PO/dev decides whether to break it up.

package/templates/agents/skills/dev-orchestrator/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: dev-orchestrator
+name: osk-build
 description: "Orchestrates feature implementation: reads approved spec, selects the right coding agent by stack, creates branches, runs TDD cycle, handles test failures, creates MRs, and updates living docs on Confluence post-merge."
 metadata:
   works_on: [copilot, antigravity, claude]
@@ -16,10 +16,10 @@ Take an approved spec and orchestrate its implementation end-to-end: select the
 
 ### Validate prerequisites
 
-1. Check that `specs/NNN-name/` exists and contains all 5 files (brief.md, contracts.md, scenarios.md, tasks.md, links.md). If any file is missing: **stop** with message: "Spec incompleta. Execute /spec antes de /dev."
-2. In Confluence (via MCP — same as /setup), check the feature page labels:
-   - If label `em-spec` is NOT present: **stop** — "Feature não passou pelo /spec. Execute /discovery e /spec antes de /dev."
-   - If label `prd-rejeitado` is present AND its addition date is MORE RECENT than `em-spec`: **stop** — "PRD foi rejeitado após a spec. Execute /discovery novamente para resolver." (Check via MCP — page metadata or label order.)
+1. Check that `specs/NNN-name/` exists and contains all 5 files (brief.md, contracts.md, scenarios.md, tasks.md, links.md). If any file is missing: **stop** with message: "Spec incompleta. Execute /osk-spec antes de /osk-build."
+2. In Confluence (via MCP — same as /osk-init), check the feature page labels:
+   - If label `em-spec` is NOT present: **stop** — "Feature não passou pelo /osk-spec. Execute /osk-discover e /osk-spec antes de /osk-build."
+   - If label `prd-rejeitado` is present AND its addition date is MORE RECENT than `em-spec`: **stop** — "PRD foi rejeitado após a spec. Execute /osk-discover novamente para resolver." (Check via MCP — page metadata or label order.)
    - Otherwise: proceed
 3. Check for concurrent execution: if there's an active branch `feat/NNN-*` in any repo, **WARN and PAUSE** — display message: "Branch ativa `feat/NNN-*` encontrada. Continuar mesmo assim? (pode causar conflitos)". Only proceed with explicit dev confirmation.
 
@@ -69,7 +69,7 @@ Read from `projects.yml` → `agents` section:
 ### Phase A — Preparation
 
 1. Read the full spec (contracts.md, scenarios.md, tasks.md)
-2. Read `specs/NNN-name/audit-report.md` — if it contains ⚠️ items, evaluate whether they block implementation. If it contains ❌ items, **stop**: "Spec não passou no audit. Execute /spec novamente."
+2. Read `specs/NNN-name/audit-report.md` — if it contains ⚠️ items, evaluate whether they block implementation. If it contains ❌ items, **stop**: "Spec não passou no audit. Execute /osk-spec novamente."
 3. Parse tasks.md to identify:
    - Task groups per repo
    - Dependencies between groups
@@ -186,7 +186,7 @@ C.2. **If tests fail:**
         ```
       - Save failure context to `docs/lessons/` for future reference
       - SKIP to next task
-      - **Unblocking**: to resume a blocked task, the dev re-runs `/dev NNN`. The agent detects tasks with `blocked` status, displays the saved context from `docs/lessons/`, and asks the dev whether to retry. If the dev confirms, the 3-retry counter resets. If the same task blocks again after another 3 retries, escalate to TL via GChat and mark the task as `blocked-permanent`. Do NOT auto-retry without dev confirmation — this prevents infinite loops.
+      - **Unblocking**: to resume a blocked task, the dev re-runs `/osk-build NNN`. The agent detects tasks with `blocked` status, displays the saved context from `docs/lessons/`, and asks the dev whether to retry. If the dev confirms, the 3-retry counter resets. If the same task blocks again after another 3 retries, escalate to TL via GChat and mark the task as `blocked-permanent`. Do NOT auto-retry without dev confirmation — this prevents infinite loops.
 
 C.3. **Conformance check** (inspired by OpenSpec's `/opsx:verify`)
 
@@ -260,7 +260,7 @@ Also append a summary line to `specs/NNN-name/conformance-history.log` (create i
 ```
 {timestamp} | {result} | {matching}/{total} endpoints | {matching}/{total} fields
 ```
-This preserves history across multiple /dev runs.
+This preserves history across multiple /osk-build runs.
 
 C.4. **Run extension hooks** (if any)
 
@@ -316,7 +316,7 @@ If the code reviewer (human or agent) rejects the MR:
 
 ### Phase D — Post-merge (after human CR approves)
 
-**How to trigger Phase D**: the dev re-executes `/dev NNN` after merging the MR. The agent detects merged MRs by checking links.md (MRs without "merged" status) or by querying the VCS API. Alternatively, the dev can run `/dev NNN --post-merge` to explicitly trigger Phase D.
+**How to trigger Phase D**: the dev re-executes `/osk-build NNN` after merging the MR. The agent detects merged MRs by checking links.md (MRs without "merged" status) or by querying the VCS API. Alternatively, the dev can run `/osk-build NNN --post-merge` to explicitly trigger Phase D.
 
 After the dev merges the MR:
 
@@ -328,14 +328,14 @@ If the conformance report (Phase C.3) detected INTENTIONAL divergences (spec was
 - `scenarios.md`: update Given/When/Then if behavior changed
 - Commit: `fix(NNN): sync spec with implementation — {summary of changes}`
 
-This ensures specs remain the source of truth for FUTURE features that reference them. Without this update, /discovery and /spec for next features read stale contracts.
+This ensures specs remain the source of truth for FUTURE features that reference them. Without this update, /osk-discover and /osk-spec for next features read stale contracts.
 
 If conformance report shows NO divergences → skip (specs already match).
 
 D.2. Move VCS Issue → `done`
 D.3. **Update living docs on Confluence** (via MCP):
 
-> **Ownership rule**: /dev is the LAST to touch living docs. Its updates reflect what WAS IMPLEMENTED (merged code), not what was planned in the spec. If the implemented behavior diverged from the spec (e.g., rule adjusted during dev), Confluence must reflect the REALITY of the code, not the original spec. Code is the source of truth post-merge.
+> **Ownership rule**: /osk-build is the LAST to touch living docs. Its updates reflect what WAS IMPLEMENTED (merged code), not what was planned in the spec. If the implemented behavior diverged from the spec (e.g., rule adjusted during dev), Confluence must reflect the REALITY of the code, not the original spec. Code is the source of truth post-merge.
 
 | Document | What to update | When |
 |----------|---------------|------|
@@ -351,13 +351,13 @@ D.3. **Update living docs on Confluence** (via MCP):
 **Confluence unavailable fallback**: if Confluence access (MCP or REST API) is down during post-merge:
 - Save pending updates to `docs/pending-confluence-updates.md` with: target page, content to add, date
 - Notify the dev with message: "Confluence indisponível — atualizações salvas em docs/pending-confluence-updates.md. Execute manualmente quando o Confluence voltar."
-- On the next /dev execution, check if `docs/pending-confluence-updates.md` exists and attempt to apply pending updates
+- On the next /osk-build execution, check if `docs/pending-confluence-updates.md` exists and attempt to apply pending updates
 
 D.4. **Post-implementation discoveries:**
 
 If implementation revealed:
 - a) A SURPRISE (unexpected behavior, edge case) → save to `docs/lessons/NNN-title.md` with template below
-- b) A NEW ARCHITECTURE DECISION (chose a pattern, discovered a constraint) → add to `docs/architecture.md` "Decisões em Aberto" table with Status: `resolvida — [decisão tomada durante implementação de {SIGLA}-NNN]`. This ensures architecture.md reflects decisions made during /dev, not just during /discovery.
+- b) A NEW ARCHITECTURE DECISION (chose a pattern, discovered a constraint) → add to `docs/architecture.md` "Decisões em Aberto" table with Status: `resolvida — [decisão tomada durante implementação de {SIGLA}-NNN]`. This ensures architecture.md reflects decisions made during /osk-build, not just during /osk-discover.
 
 Lessons template:
     ```
@@ -413,7 +413,7 @@ D.5. Notify Google Chat (rich card format):
 
 ### Phase E — Infrastructure validation (optional, recommended before release)
 
-**How to trigger Phase E**: dev runs `/dev --validate`, or automatically after the last feature of the cycle. Not executed per feature — only when the dev wants to validate the complete system against real infrastructure.
+**How to trigger Phase E**: dev runs `/osk-build --validate`, or automatically after the last feature of the cycle. Not executed per feature — only when the dev wants to validate the complete system against real infrastructure.
 
 **Prerequisite**: the project has a `docker-compose.yml` (or equivalent infra) declared in `projects.yml`. If not, skip this phase.
 
@@ -509,7 +509,7 @@ Add a step to your CI pipeline (GitHub Actions, GitLab CI, etc.) that reads the
 
 ### When to adopt
 
-- **Now**: run conformance check manually during /dev (Phase C.3) — already implemented
+- **Now**: run conformance check manually during /osk-build (Phase C.3) — already implemented
 - **Next**: add CI Guard when the team sets up CI/CD pipelines
 - **Future**: add custom hooks for domain-specific validations
 
@@ -523,7 +523,7 @@ To add support for a new programming language or framework:
 
 1. Create an agent definition in `padrao-labs-agents/.agents/agents/{name}.agent.md`
 2. Add the stack → agent mapping in `projects.yml` → `agents.coding` (e.g., `go: my-go-engineer`)
-3. The /dev automatically selects the new agent when a repo in `projects.yml` declares that stack
+3. The /osk-build automatically selects the new agent when a repo in `projects.yml` declares that stack
 
 ### 2. Rules (cross-cutting concerns)
 
@@ -535,7 +535,7 @@ To add rules that apply across all skills:
 
 ### 3. Hooks (custom validations)
 
-To add custom validation steps to the /dev pipeline:
+To add custom validation steps to the /osk-build pipeline:
 
 1. Create a `hooks/` directory in the spec repo
 2. Add executable scripts to `hooks/pre-merge/` — they run in Phase C.4 before MR creation

package/templates/agents/skills/discovery/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: discovery
+name: osk-discover
 description: "Reads PO demands and project context, identifies gaps and ambiguities, generates structured questions or a PRD. Handles the Q&A loop with the PO via Confluence."
 metadata:
   works_on: [copilot, antigravity, claude]
@@ -18,13 +18,13 @@ Read all available inputs (PO demand, domain docs, architecture, existing code),
 
 Before anything, verify that the project was set up correctly:
 
-1. Read `projects.yml` — if empty or has only template content, **stop** with message: "/setup não foi executado. Execute /setup antes de /discovery."
+1. Read `projects.yml` — if empty or has only template content, **stop** with message: "/osk-init não foi executado. Execute /osk-init antes de /osk-discover."
 2. **Confluence access — ALWAYS use MCP:**
    - All Confluence operations (read pages, create pages, labels) MUST use the MCP server (`confluence` in `.mcp.json`).
    - **Do NOT use curl, fetch, or direct REST calls** — even if `.env` has credentials.
    - If MCP is not responding → **STOP**: "MCP Confluence não disponível. Execute 'open-spec-kit doctor' para diagnosticar."
 3. Verify these pages exist under the project root (`root_page_id` from `projects.yml`):
-   - `Visão do Produto` — if not found, **stop** with message: "Página 'Visão do Produto' não encontrada. Execute /setup primeiro."
+   - `Visão do Produto` — if not found, **stop** with message: "Página 'Visão do Produto' não encontrada. Execute /osk-init primeiro."
    - `Glossário` — if not found, **stop** with same message pattern
    - `Domínio/` (with children: Regras, Fluxos, Tabelas, Integrações) — if not found, **stop**
    - `Features/` — if not found, **stop**
@@ -32,7 +32,7 @@ Before anything, verify that the project was set up correctly:
 
 ### Feature selection (BUG-032)
 
-If NO argument was passed (user ran `/discovery` without a feature name):
+If NO argument was passed (user ran `/osk-discover` without a feature name):
 
 1. List ALL features under `Features/` in Confluence
 2. For each feature, read the metadata table ("Depende de" field)
@@ -40,7 +40,7 @@ If NO argument was passed (user ran `/discovery` without a feature name):
 4. **Check dependencies**: a feature can only enter discovery if ALL features it depends on already have label `em-spec` or `done`. Features with unsatisfied dependencies: mark as "(blocked — depends on {SIGLA}-NNN)"
 5. Present the dev with the list of available (non-blocked) features, sorted by ID:
    ```
-   Features disponíveis para /discovery:
+   Features disponíveis para /osk-discover:
    1. ⚙️ TFB-000 - Infraestrutura e Scaffold
    2. 🚀 TFB-001 - Importação de Faturas
    3. 🚀 TFB-003 - Consulta de Faturas
@@ -55,7 +55,7 @@ If NO argument was passed (user ran `/discovery` without a feature name):
 7. Ask: "Qual feature deseja trabalhar?"
 8. Proceed with the chosen feature.
 
-If argument WAS passed (e.g., `/discovery TFB-001`):
+If argument WAS passed (e.g., `/osk-discover TFB-001`):
 - Locate the corresponding feature page and proceed normally.
 - If the feature has unsatisfied dependencies, **warn** but continue (dev may be working out of order intentionally).
 
@@ -73,7 +73,7 @@ Read these files FIRST:
 ### 1. Compile all information
 
 From Confluence (via MCP), read:
-- The feature page in `Features/` (demand extracted by /setup). Read the metadata table — especially the "Seções do PO" field, which tells you exactly which PO document sections are relevant for this feature. Use this to focus your gap analysis.
+- The feature page in `Features/` (demand extracted by /osk-init). Read the metadata table — especially the "Seções do PO" field, which tells you exactly which PO document sections are relevant for this feature. Use this to focus your gap analysis.
 - `Dominio/` — business rules, flows, reference tables, integrations
 - `Visao do Produto` — product scope and success metrics
 - Previous Q&A rounds on the feature page (if any)
@@ -209,13 +209,13 @@ Before deciding questions vs PRD, assess the scope:
 
 Before generating questions or PRD, find the feature page:
 
-1. Search for an existing feature page in `Features/` matching the feature name/argument (created by /setup in Step 4.5)
+1. Search for an existing feature page in `Features/` matching the feature name/argument (created by /osk-init in Step 4.5)
 2. **If found**: use it (read existing content, detect previous Q&A rounds)
-3. **If NOT found**: the /setup may have failed to create it. Create it under `Features/` as fallback:
+3. **If NOT found**: the /osk-init may have failed to create it. Create it under `Features/` as fallback:
    - Title: `{SIGLA}-NNN - Feature name` (next sequential number, using project sigla from projects.yml)
    - Content: 1-2 paragraphs describing the feature (from PO documents or argument context)
    - Label: `em-discovery`
-   - Log: "Feature page not found — created as fallback. Check if /setup ran correctly."
+   - Log: "Feature page not found — created as fallback. Check if /osk-init ran correctly."
 4. The feature page is the SINGLE source of truth for this feature's discovery process
 
 ### 6. Decision: questions or PRD?
@@ -254,7 +254,7 @@ Then:
   Replace `{}` placeholders with actual values. Notifications always in pt-BR.
 - STOP and wait for PO to respond
 
-**Timeout and escalation:** if the PO does not respond in a reasonable time, the dev can re-run /discovery on the same feature. The agent must detect previous questions (existing "Dúvidas & Decisões — Rodada N" section) and:
+**Timeout and escalation:** if the PO does not respond in a reasonable time, the dev can re-run /osk-discover on the same feature. The agent must detect previous questions (existing "Dúvidas & Decisões — Rodada N" section) and:
 - Check the page's `modified` field (via MCP). If the last modification was more than 3 business days ago and responses still contain "_aguardando_": escalate.
 - If there are pending responses but within the deadline: re-notify via Google Chat (same command as the previous step)
 - If more than 3 business days have passed: escalate to TL:
@@ -273,13 +273,13 @@ Then:
 
 For architectural trade-offs, read `projects.yml` → `agents.principal`. If configured (not null), consult that agent to validate options. Document the decision in the PRD.
 
-**Fallback**: if `principal-engineer` agent is not available, document the options with trade-offs in the PRD and mark as "DECISÃO TÉCNICA — a validar com TL antes do /spec".
+**Fallback**: if `principal-engineer` agent is not available, document the options with trade-offs in the PRD and mark as "DECISÃO TÉCNICA — a validar com TL antes do /osk-spec".
 
 After documenting technical decisions, **return to step 6** and re-evaluate: if no gaps remain, proceed to generate the full PRD.
 
 **IF no gaps remain (or all answered):**
 
-Generate the PRD on the feature page in Confluence. **IMPORTANT: APPEND the PRD section BELOW the existing metadata table and Escopo section created by /setup — do NOT replace or remove them.**
+Generate the PRD on the feature page in Confluence. **IMPORTANT: APPEND the PRD section BELOW the existing metadata table and Escopo section created by /osk-init — do NOT replace or remove them.**
 
 ```
 ## PRD
@@ -415,9 +415,9 @@ If a Confluence operation fails mid-flow (publishing questions, updating PRD, ch
 
 ## Exit gate (BLOCKING — cannot close the loop without these)
 
-The /discovery CANNOT be considered done until ALL of the following are true. If any item fails, fix it before proceeding.
+The /osk-discover CANNOT be considered done until ALL of the following are true. If any item fails, fix it before proceeding.
 
-1. **Glossary updated on Confluence** — if the PRD section "GLOSSÁRIO: termos novos" lists any terms, they MUST be added to the Glossário page on Confluence BEFORE closing. Read the current page, add the terms, update. Do NOT leave this for /spec.
-2. **All "A CONFIRMAR" in Glossário resolved** — if any term in the Glossário still has "A CONFIRMAR" and the /discovery answered that question (e.g., PO confirmed enum values), update the Glossário to remove the "A CONFIRMAR" and replace with the confirmed value.
+1. **Glossary updated on Confluence** — if the PRD section "GLOSSÁRIO: termos novos" lists any terms, they MUST be added to the Glossário page on Confluence BEFORE closing. Read the current page, add the terms, update. Do NOT leave this for /osk-spec.
+2. **All "A CONFIRMAR" in Glossário resolved** — if any term in the Glossário still has "A CONFIRMAR" and the /osk-discover answered that question (e.g., PO confirmed enum values), update the Glossário to remove the "A CONFIRMAR" and replace with the confirmed value.
 3. **Decisions attributed correctly** — business decisions (scope, enums, features) marked as "PO". Technical decisions (cascade, notification rules, filtering) marked as "Dev". Never mix them.
-4. **architecture.md updated** — if the /discovery resolved any open decision listed in architecture.md, update the Status column from `aberta` to `resolvida — [decisão tomada]`. Do NOT leave stale "A CONFIRMAR" when the answer exists.
+4. **architecture.md updated** — if the /osk-discover resolved any open decision listed in architecture.md, update the Status column from `aberta` to `resolvida — [decisão tomada]`. Do NOT leave stale "A CONFIRMAR" when the answer exists.

package/templates/agents/skills/setup-project/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: setup-project
+name: osk-init
 description: "Bootstraps a new project from Confluence demands. Reads PO inputs, generates living docs (Vision, Glossary, Domain), and prepares the spec repo."
 metadata:
   works_on: [copilot, antigravity, claude]
@@ -16,7 +16,7 @@ Bootstrap a new project from raw PO inputs on Confluence. Generate the initial l
 
 1. Read `projects.yml` — if already filled (has repos with status != template):
    - If argument contains `--force`: proceed (will overwrite existing config and re-create missing pages)
-   - Otherwise: **stop** with message: "Projeto já configurado. Para re-executar, passe `--force` (ex: `/setup MFS --force`)."
+   - Otherwise: **stop** with message: "Projeto já configurado. Para re-executar, passe `--force` (ex: `/osk-init MFS --force`)."
 2. **Confluence access — ALWAYS use MCP:**
    - All Confluence operations (read pages, create pages, labels) MUST use the MCP server (`confluence` in `.mcp.json`).
    - **Do NOT use curl, fetch, or direct REST calls** — even if `.env` has credentials.
@@ -336,11 +336,11 @@ If the concern IS already an explicit PO section (identified in Phase A as its o
    ## Escopo
    {bullet list of what this feature includes — extracted from PO docs, not invented}
    ```
-3. Add label `em-discovery` (ready for /discovery to process)
+3. Add label `em-discovery` (ready for /osk-discover to process)
 
-If the PO documents describe a SINGLE monolithic system without clear feature boundaries, create ONE feature page covering the full scope and note: "Feature única — considerar quebra em sub-features durante /discovery."
+If the PO documents describe a SINGLE monolithic system without clear feature boundaries, create ONE feature page covering the full scope and note: "Feature única — considerar quebra em sub-features durante /osk-discover."
 
-This step ensures /discovery always finds a feature page to work with.
+This step ensures /osk-discover always finds a feature page to work with.
 
 ### 4. Set up the spec repo
 
@@ -356,7 +356,7 @@ In the local spec repo:
 - Confluence space key and root_page_id (if multi-project layout)
 
 **Create directories:**
-- `docs/lessons/` — empty (used by /dev to log surprises)
+- `docs/lessons/` — empty (used by /osk-build to log surprises)
 - `docs/decisions/` — empty (used for ADRs)
 
 **Generate `docs/architecture.md` draft:**
@@ -377,16 +377,16 @@ In the local spec repo:
   ```
 - Events identified (table: event, generates notification?, generates history?)
 - Environment/infrastructure (how it runs)
-- **Decisoes em aberto**: list ALL "A CONFIRMAR" items from all Confluence pages, ranked by impact. High impact = blocks /spec or /dev. Format:
+- **Decisoes em aberto**: list ALL "A CONFIRMAR" items from all Confluence pages, ranked by impact. High impact = blocks /osk-spec or /osk-build. Format:
 
 ```
 | # | Decisao | Impacto | Bloqueia | Status |
 |---|---------|---------|----------|--------|
-| 1 | Worker separado ou parte da API? | Alto — define repos e CI | /spec | aberta |
-| 2 | Valores do enum de Status | Médio — afeta model e validação | /dev | aberta |
+| 1 | Worker separado ou parte da API? | Alto — define repos e CI | /osk-spec | aberta |
+| 2 | Valores do enum de Status | Médio — afeta model e validação | /osk-build | aberta |
 ```
 
-Status values: `aberta`, `resolvida — [decisão tomada]`. The /discovery updates this column when resolving decisions (exit gate).
+Status values: `aberta`, `resolvida — [decisão tomada]`. The /osk-discover updates this column when resolving decisions (exit gate).
 
 Mark sections as "DRAFT — validar com o time"
 
@@ -395,7 +395,7 @@ Mark sections as "DRAFT — validar com o time"
 If a Confluence page creation fails mid-flow:
 1. Log which pages were successfully created and which failed
 2. Save pending page creations to `docs/pending-confluence-updates.md` with: target parent page, page title, content summary, date
-3. Report to dev: "Setup parcial — {N} de {total} páginas criadas. Páginas faltantes: {list}. Re-execute /setup para tentar criar as faltantes."
+3. Report to dev: "Setup parcial — {N} de {total} páginas criadas. Páginas faltantes: {list}. Re-execute /osk-init para tentar criar as faltantes."
 4. On re-execution, check if `docs/pending-confluence-updates.md` exists and attempt to apply pending operations FIRST. Also check which pages already exist (by listing children of the parent page) and only create the missing ones — never duplicate. Remove applied entries from the file.
 
 ### 5. Self-review
@@ -436,7 +436,7 @@ Before closing the loop, the agent MUST do a self-review:
       📊 <b>Métricas:</b>
       • {rule_count} regras de negócio
       • {flow_count} fluxos documentados
-      • {open_decisions_count} decisões em aberto ({high_impact_count} alto impacto)" --next "Resolver decisões de alto impacto e rodar /discovery" --button-text "Abrir Visão do Produto" --button-url "{confluence_vision_page_url}"
+      • {open_decisions_count} decisões em aberto ({high_impact_count} alto impacto)" --next "Resolver decisões de alto impacto e rodar /osk-discover" --button-text "Abrir Visão do Produto" --button-url "{confluence_vision_page_url}"
 
   Replace `{}` placeholders with actual values from the execution context.