iuripereira
UserSpec-Driven Development por delta specs, com gates determinísticos — plugin do Claude Code
Categories
Indexed Skills (9)
descoberta
Use when a project needs discovery BEFORE any spec exists — mining raw inputs (meeting transcript/summary, video, legacy spreadsheet, scattered docs) into an as-is dossier with explicit confidence levels, populated glossary/data dictionary, divergences against an existing baseline and a stakeholder validation agenda. Triggers include "/deltaspec:descoberta", "processo de descoberta", "discovery", "minerar transcrição", "reunião de kickoff", "documentar processo legado", "as-is", "levantar requisitos com stakeholder", or entering the deltaspec cycle without a validated PRD.
doc-entregavel
Use when producing or exporting a frozen client deliverable — a PDF/DOCX with signature cover and embedded diagrams from a project whose doc-profile.yaml declares publico.cliente true, or a legal-commercial document (NDA, IT services contract, client requirements/vision document). Triggers include "/deltaspec:doc-entregavel", "exportar entregável", "gerar PDF para o cliente", "documento para assinatura", "congelar o PRD", "gerar NDA", "acordo de confidencialidade", "minuta de contrato", "contrato de prestação de serviços", "documento de requisitos para o cliente", "proposta com orçamento e cronograma", or the visual-documentation gate of the deltaspec spec flow.
eu-tenho-tdah
Perfil de estilo de escrita do Iuri (meu estilo de escrita / my writing style). Baseado em ayghri/i-have-adhd, com regras de economia de token (caveman) e comunicação concisa (Matt Pocock). Aplique este estilo em TODA resposta e TODO rascunho — código, debug, explicação, planejamento e conversa casual — a menos que o Iuri peça explicitamente formato diferente. Use também quando o Iuri mencionar "modo direto", "sem enrolação", "estilo tdah" ou reclamar de verbosidade.
guarding-doc-integrity
Use when editing docs in a repo that has a deps.toml manifest; when a business-rule value duplicated across files (PRD, CLAUDE.md, data dictionary) changed; when the user asks to set up doc integrity tracking, canonical-source governance, or mirrored-value validation; or before committing changes to canonical docs.
projeto-infra
Use when setting up or auditing repository infrastructure on GitHub — branch protection rulesets, CI workflows, Conventional Commits enforcement (husky/commitlint), release-please, CodeRabbit or claude-code-action review. Triggers include "/deltaspec:projeto-infra", "proteger a main", "configurar branch protection", "setup de CI", "automação de release", or the optional infra step offered by projeto-init. Requires gh CLI authenticated and a GitHub remote.
projeto-init
Use when initializing or standardizing a repository and a CLAUDE.md plus documentation scaffold is needed — CHANGELOG, STATE, DEBT, ADRs, specs, glossary. Triggers include "/deltaspec:projeto-init", "init personalizado", "gerar CLAUDE.md canônico", "scaffold de documentação", or setting up Keep a Changelog / SemVer / Conventional Commits / SDD conventions in a project.
spec-feature
Use when starting, resuming, or archiving a feature increment in a project that follows the deltaspec cycle (specs/NNN-name/ with delta specs). Triggers include "/deltaspec:spec-feature", "nova feature", "delta spec", "specify", "clarify", "analyze", "arquivar a delta", "consolidar no TRUTH.md", or the sdd-ciclo module in the project's CLAUDE.md.
status-pmo
Use when a project or portfolio needs a recurring PMO status site — weekly status report, schedule vs. contract deadlines (gantt with milestones), % progress dashboard with per-project phase and traffic light, printable per-project one-page — generated as self-contained HTML from canonical repo files and published behind restricted access, ready to swap the data source for Jira later. Triggers include "/deltaspec:status-pmo", "site de status", "status report semanal", "report para a gestão", "dashboard de projetos", "acompanhamento de portfólio", "one-page do projeto", "cronograma com marcos".
spec-review
Use when a delta spec and plan (specs/NNN-name/) deserve adversarial review before implementation — especially when the spec touches security, persistent data, external contracts, or new dependencies. Triggers include "/deltaspec:spec-review", "revisão adversarial", "stress-test da spec", "essa spec aguenta", or a user asking for extra scrutiny on a spec/plan before implement.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.