kanbanize-sdk: Skill for Claude Code

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

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

A planning guide that turns an approved change specification into a technical plan and ordered tasks. It requires checking the existing code before proposing new structures.

In plain words
What is it for?
Use it to create plan.md and tasks.md for an approved change, including alternatives, delivery order, migrations, and links between requirements and tests.
Why use it?
It exposes reuse opportunities, migration and deployment risks, and missing tests before implementation begins.

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-plano/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-plano

README.md
[![agentmods](https://agentmods.dev/badge/skills/darcivieira/kanbanize-sdk/spec-plano/github.svg)](https://agentmods.dev/skills/darcivieira/kanbanize-sdk/spec-plano)
Your own site
<a href="https://agentmods.dev/skills/darcivieira/kanbanize-sdk/spec-plano"><img src="https://agentmods.dev/badge/skills/darcivieira/kanbanize-sdk/spec-plano/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-plano

Your own site · 80×15
<a href="https://agentmods.dev/skills/darcivieira/kanbanize-sdk/spec-plano"><img src="https://agentmods.dev/badge/skills/darcivieira/kanbanize-sdk/spec-plano.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 584 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.00083 $0.00584
Opus 5.5 $0.00033 $0.00234
Sonnet 5.5 $0.00017 $0.00117
Haiku 4.5 $0.00008 $0.00058

Measured 2mo ago against content hash 94a1fa9facb3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-plano 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 2mo 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-plano/SKILL.md · 55 lines

What it actually says

spec-plano

Converte requisito em desenho técnico e tarefas ordenadas. Aqui entra o como.

Pré-condições

  • specs/mudancas/NNN-*/spec.md existe, com status: aprovada
  • Nenhum [PRECISA DECISÃO] pendente

Se qualquer uma falhar, pare e diga qual.

Passo 1 — Reconhecimento antes do desenho

Antes de propor qualquer estrutura nova, leia o código real dos módulos e telas listados em "Impacto no que já existe". Delegue para subagente se for extenso.

Preencha a tabela "O que é reusado" antes da tabela "O que é criado". Essa ordem não é estilística: criar sem ter procurado é violação da constituição, e a ordem das tabelas é o que força a busca.

Passo 2 — plan.md

Use specs/_templates/MUDANCA-plan.md. Regras:

  • Toda criação nova precisa de justificativa de por que não reusar
  • Alternativa considerada e descartada com peso real → marque "vira ADR: sim"
  • Migration: declare reversibilidade e backfill explicitamente
  • Backend + frontend: declare a ordem de entrega e como não quebrar durante o deploy
  • Amarre cada nível de teste aos RFs que ele cobre — RF sem teste é buraco

Se o desenho exigir camada, padrão ou biblioteca nova, isso é 🔴 RED: pare e sinalize.

Passo 3 — tasks.md

Use specs/_templates/MUDANCA-tasks.md. Regras:

  • Ordem por dependência real, não por conveniência
  • Cada tarefa toca poucos arquivos e cita os caminhos
  • "Pronto quando" verificável — não "implementado corretamente"
  • Cada RF da spec aparece em pelo menos uma tarefa; conferir cobertura ao final
  • [P] só onde não há conflito de arquivo
  • Checkpoints onde algo passa a funcionar ponta a ponta

Passo 4 — Parar para aprovação

Apresente: abordagem em 3 frases, o que é reusado, o que é criado, os riscos, e a contagem de tarefas. Peça aprovação explícita.

Não implemente. A caixa de aprovação em plan.md só é marcada pelo humano.

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. 2mo ago First seen · 55 lines · 83 tokens per session scan A 94a1fa9facb3

Subscribe to this mod's changes

spec-plano is a skill published in the GitHub repository darcivieira/kanbanize-sdk (2 stars, last pushed 2mo ago), licensed MIT. It adds 83 tokens to every session and 584 once invoked, about $0.0003 per session on Opus 5.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

spec-plano compared with skills from other repositories

spec-plano next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spec-planodarcivieira/kanbanize-sdkSkill22mo agoMITA83Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code