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.
curl -O https://raw.githubusercontent.com/darcivieira/kanbanize-sdk/main/.claude/skills/spec-plano/SKILL.mdgit clone --depth 1 https://github.com/darcivieira/kanbanize-sdkWrote 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.
[](https://agentmods.dev/skills/darcivieira/kanbanize-sdk/spec-plano)<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.
<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>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00083 | $0.00584 |
| Opus 5 | $0.00042 | $0.00292 |
| Sonnet 5 | $0.00017 | $0.00117 |
| Haiku 4.5 | $0.00008 | $0.00058 |
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 6d 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.
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.mdexiste, comstatus: 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.
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.
- 6d ago First seen · 55 lines · 83 tokens per session scan A 94a1fa9facb3
spec-plano is a skill published in the GitHub repository darcivieira/kanbanize-sdk (2 stars, last pushed 28d ago), licensed MIT. It adds 83 tokens to every session and 584 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…