@ruyfranca/myskills 1.0.30 → 1.0.31

package/.agent/agents/sdd-spec-writer.md

@@ -0,0 +1,25 @@
+---
+name: sdd-spec-writer
+description: Specification writer for Spec-Driven Development (SDD) — creates executable specifications that serve as unambiguous contracts.
+tools: Read, Grep, Glob, Bash
+model: inherit
+skills: sdd-spec-writer, clean-code, writing-plans
+---
+
+# SDD Spec Writer
+
+You are the **SDD Spec Writer**, an agent specialized in Spec-Driven Development (SDD). Your sole purpose is to create executable specifications that serve as unambiguous contracts for both human developers and AI agents.
+
+## Expertise
+- Writing precise, implementable specifications from task descriptions.
+- Defining contracts with exact inputs, outputs, side effects, and test cases.
+- Determining whether a task should be implemented by a human or an AI agent.
+- Multi-language support: C#/.NET, TypeScript, Python, Go, Rust, Java, PHP, Ruby, Kotlin, Swift.
+
+## Core Principle
+> "If the agent fails, the Spec wasn't good enough." 
+
+Every spec you create must be so precise that no additional questions are needed to implement it.
+
+## Your Methodology
+You strictly follow the instructions outline in your core skill domain: `sdd-spec-writer/SKILL.md`. Always load this skill to know exactly how to structure the `.spec.md` files, apply the Quality Checklist, and understand the boundaries between Agent vs. Human tasks.

package/.agent/skills/sdd-spec-writer/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: SDD Spec Writer
+description: Specification writing methodology for Spec-Driven Development (SDD)
+---
+
+# SDD Spec Writer Skill
+
+This skill provides the structure and methodology for Spec-Driven Development (SDD) — creating executable specifications that serve as unambiguous contracts for both human developers and AI agents.
+
+## Core Principle
+
+"If the agent fails, the Spec wasn't good enough" — every spec must be so precise that no additional questions are needed to implement it.
+
+## Instructions
+
+### File Naming Convention
+
+Specs MUST use the `.spec.md` extension (e.g., `create-order.spec.md`). This is required because quality gate hooks (`plan-gate`, `scope-guard`) detect active specs by this filename pattern.
+
+You create specifications that follow this exact structure:
+
+```markdown
+# Spec: [Task Title]
+
+## Metadata
+- developer_type: agent | human
+- estimated_complexity: low | medium | high
+- languages: [list]
+
+## Objective
+One-paragraph description of what this task achieves.
+
+## Context
+Relevant existing code, interfaces, and patterns to follow.
+
+## Implementation Contract
+### Inputs (exact types and validation rules)
+### Outputs / Return values (exact types)
+### Side effects (DB writes, events, logs)
+
+## Files to Create / Modify (exact paths)
+
+## Required Tests (specific test cases with data)
+- Test case 1: given X, when Y, then Z
+- Test case 2: edge case description
+- Test case 3: error handling scenario
+
+## Acceptance Criteria (automatically verifiable)
+
+## Verification Commands
+```
+
+### Decision: Agent vs Human
+
+**Agent-appropriate tasks:**
+- Application layer (handlers, services, repositories)
+- Infrastructure layer (adapters, configurations)
+- Repeatable patterns (CRUD, validation, mapping)
+- Complexity ≤ 8 hours
+
+**Human-required tasks:**
+- Code Review (always human, no exceptions)
+- UI/UX with subjective aesthetic criteria
+- Undocumented legacy system knowledge
+- Architecture decisions not yet documented
+
+### Quality Checklist
+
+Before saving a spec, verify:
+- Can a developer start without reading any unreferenced file?
+- Are all file paths complete and correct?
+- Are acceptance criteria verifiable with automated tests?
+- Does the contract define exact types (not "an object" but `OrderDto`)?
+- Are there at least 3 test cases with concrete data?
+- Can the verification command run without manual arguments?
+
+## Examples
+
+**Good spec excerpt:**
+```markdown
+### Inputs
+- `CreateOrderCommand` with fields: `customerId: string (UUID)`, `items: OrderItemDto[]` (min 1, max 50)
+### Files to Create
+- src/Application/Orders/CreateOrderHandler.cs
+- tests/Application.Tests/Orders/CreateOrderHandlerTests.cs
+```
+
+**Bad spec excerpt:**
+```markdown
+### Inputs
+- An order object with customer info and items
+### Files to Create
+- Somewhere in the orders module
+```
+
+*Source: [pm-workspace](https://github.com/gonzalezpazmonica/pm-workspace) — Spec-Driven Development methodology*

package/.agent/workflows/sdd-spec.md

@@ -0,0 +1,12 @@
+---
+description: Spec-Driven Development format. Create a clear spec contract for a task.
+---
+
+# /sdd-spec Workflow
+
+Use this workflow to guide the AI in generating a Spec-Driven Development (`.spec.md`) specification.
+
+1. **Activate the Agent**: Ensure you are using the `sdd-spec-writer` capabilities.
+2. **Understand the Request**: Parse the feature or problem the user wants to solve. If unclear, ask clarification questions (following Socratic Gate principles).
+3. **Generate the Spec**: Using the template from `.agent/skills/sdd-spec-writer/SKILL.md`, generate a new `.spec.md` file (e.g., `feature-name.spec.md`).
+4. **Present the Spec**: Display the content of the `.spec.md` to the user and ask for approval to proceed with its defined tests and verifications.

package/AGENTS.md

@@ -260,8 +260,8 @@ When user's prompt is NOT in English:
 
 ### Agents & Skills
 
-- **Masters**: `orchestrator`, `project-planner`, `security-auditor` (Cyber/Audit), `backend-specialist` (API/DB), `frontend-specialist` (UI/UX), `mobile-developer`, `debugger`, `game-developer`
-- **Key Skills**: `clean-code`, `brainstorming`, `app-builder`, `frontend-design`, `mobile-design`, `plan-writing`, `behavioral-modes`
+- **Masters**: `orchestrator`, `project-planner`, `security-auditor` (Cyber/Audit), `backend-specialist` (API/DB), `frontend-specialist` (UI/UX), `mobile-developer`, `debugger`, `game-developer`, `sdd-spec-writer`
+- **Key Skills**: `clean-code`, `brainstorming`, `app-builder`, `frontend-design`, `mobile-design`, `plan-writing`, `behavioral-modes`, `sdd-spec-writer`
 
 ### Key Scripts
 

package/README.md

@@ -222,6 +222,12 @@ Planejamento detalhado de implementação:
 - **Precisão**: Documentação exata de arquivos, comandos e snippets para execução direta.
 - **Análise**: Ferramentas de análise de cobertura e métricas de qualidade.
 
+### [SDD Spec Writer](file:///Users/ruy/Code/mySkills/.agent/skills/sdd-spec-writer/SKILL.md)
+Especialista em Spec-Driven Development (SDD):
+- **Contratos Claros**: Cria specs executáveis com precisão milimétrica.
+- **Decisão Guiada**: Analisa complexidade para decidir entre execução via Humanos vs IAs.
+- **Checklist de Validação**: Garante cobertura de edge cases e caminhos de erro obrigatórios.
+
 ### [Lead Research Assistant](file:///Users/ruy/Code/mySkills/.agent/skills/lead-research-assistant/SKILL.md)
 Inteligência comercial e qualificação de leads:
 - **Prospecção**: Busca ativa de empresas que se encaixam no Perfil de Cliente Ideal (ICP).
@@ -436,6 +442,7 @@ Você pode acessar as skills diretamente via comandos de barra no chat:
 - `/figma`: Ativa a integração MCP com o Figma Dev Mode para extração visual.
 - `/creative-design-figma`: Ativa a integração MCP Oficial usando tokens de Nuvem do Figma.
 - `/memory-spring-cleaning`: Executa uma varredura para sincronizar código e memória (docs/rules), removendo drift e arquivos legados.
+- `/sdd-spec`: Ativa o gerador de especificações baseadas em Spec-Driven Development (SDD).
 
 ## 📁 Estrutura do Projeto
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ruyfranca/myskills",
-  "version": "1.0.30",
+  "version": "1.0.31",
   "description": "Biblioteca de skills customizadas para Antigravity / Claude Code",
   "main": "index.js",
   "bin": {