kanbanize-sdk: Skill for Claude Code

.claude/skills/spec-fechar/SKILL.md

spec-fechar is a skill for Claude Code from darcivieira/kanbanize-sdk. It costs 97 tokens per session (779 once invoked), scanned A, original, MIT.

A workflow for closing a completed software change by comparing the written specification with the actual code, checking the definition of done, and updating project records.

In plain words
What is it for?
Use it when a feature is implemented, ready for a pull request, or needs its specifications, decisions, and active work records synchronized.
Why use it?
It prevents project specifications and checklists from becoming outdated or claiming work was finished without verification.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is darcivieira/kanbanize-sdk's own configuration. It tells Claude Code how to work on kanbanize-sdk itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kanbanize-sdk configures →

Reuse

Borrowing it

Nothing to install: this file belongs to darcivieira/kanbanize-sdk. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/darcivieira/kanbanize-sdk/main/.claude/skills/spec-fechar/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/darcivieira/kanbanize-sdk

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for spec-fechar

README.md
[![agentmods](https://agentmods.dev/badge/skills/darcivieira/kanbanize-sdk/spec-fechar/github.svg)](https://agentmods.dev/skills/darcivieira/kanbanize-sdk/spec-fechar)
Your own site
<a href="https://agentmods.dev/skills/darcivieira/kanbanize-sdk/spec-fechar"><img src="https://agentmods.dev/badge/skills/darcivieira/kanbanize-sdk/spec-fechar/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for spec-fechar

Your own site · 80×15
<a href="https://agentmods.dev/skills/darcivieira/kanbanize-sdk/spec-fechar"><img src="https://agentmods.dev/badge/skills/darcivieira/kanbanize-sdk/spec-fechar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 779 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00097 $0.00779
Opus 5 $0.00048 $0.00390
Sonnet 5 $0.00019 $0.00156
Haiku 4.5 $0.00010 $0.00078

Measured 7d ago against content hash 9b2c7984da6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

spec-fechar scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/spec-fechar/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

spec-fechar

Sem este passo o sistema apodrece: specs de estado congelam e viram mentira.

Passo 1 — Verificar de verdade

Não confie nas caixas marcadas em tasks.md. Compare o spec.md com o código real:

Verificação Como
Cada RF foi implementado? Localize o código que o satisfaz. Cite arquivo e linha.
Cada critério de aceite tem teste? Localize o teste.
O que foi feito além da spec? Escopo extra é achado, não bônus — reporte.
O que ficou faltando? Liste explicitamente.

Divergência entre spec e código não é erro de spec por padrão. Pergunte qual dos dois está certo antes de mexer.

Passo 2 — Rodar o DoD

Percorra specs/governanca/04-definition-of-done.md item por item, marcando só o que você verificou. Item não verificado fica desmarcado e é reportado — nunca marcado por otimismo.

Passo 3 — Absorver no estado

Mudou Atualize
Endpoint, regra de negócio modulos/<mod>.md — checklists e contratos
Entidade, campo, migration dados/entidades/<mod>.md e dados/INDICE.md
Tela, rota, estado de UI ui/telas/<tela>.md
Componente compartilhado ui/COMPONENTES.md
Topologia, camada, fluxo arquitetura/VISAO_TECNICA.md
Termo novo do domínio visao/GLOSSARIO.md
Entrega de roadmap visao/ROADMAP.md

Respeite a propriedade de fatos de governanca/02-convencoes.md: um fato, um dono. Se você está prestes a escrever a mesma informação em dois arquivos, pare — um deles deve referenciar.

Passo 4 — ADRs

Para cada linha de plan.md marcada "vira ADR: sim", e para toda decisão tomada durante a implementação que um revisor questionaria: use a skill spec-adr.

Decisão que revoga ADR anterior não edita o anterior — cria sucessor e marca o antigo como substituído.

Passo 5 — Encerrar

  1. spec.mdstatus: concluida
  2. specs/ACTIVE.mdnenhuma
  3. Mantenha mudancas/NNN-*/ no repositório. É o histórico do porquê.
  4. Rode python3 scripts/spec_status.py e reporte.

Read the full file on GitHub · 65 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 65 lines · 97 tokens per session scan A 9b2c7984da6d

Subscribe to this mod's changes

spec-fechar is a skill published in the GitHub repository darcivieira/kanbanize-sdk (2 stars, last pushed 29d ago), licensed MIT. It adds 97 tokens to every session and 779 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

magpie-security-issue-import-from-md

Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.

apache/magpie · 73 tokens