code-ai-template: Skill for Claude Code

.claude/skills/planejar-fase/SKILL.md

planejar-fase is a skill for Claude Code from FHDumont/code-ai-template. It costs 41 tokens per session (651 once invoked), scanned A, original, MIT.

A planning workflow for opening the next development phase by reviewing project notes, auditing the existing code, and writing a specification.

In plain words
What is it for?
Use it to review open findings and project context, inspect migrations and data when needed, coordinate code audits, and prepare docs/SETUP.md without changing code.
Why use it?
It reduces planning errors caused by stale documentation, missed technical debt, or assumptions about how the code and stored data work.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is FHDumont/code-ai-template's own configuration. It tells Claude Code how to work on code-ai-template 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 code-ai-template configures →

Reuse

Borrowing it

Nothing to install: this file belongs to FHDumont/code-ai-template. 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/FHDumont/code-ai-template/main/.claude/skills/planejar-fase/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/FHDumont/code-ai-template

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 planejar-fase

README.md
[![agentmods](https://agentmods.dev/badge/skills/fhdumont/code-ai-template/planejar-fase.svg)](https://agentmods.dev/skills/fhdumont/code-ai-template/planejar-fase)
Your own site
<a href="https://agentmods.dev/skills/fhdumont/code-ai-template/planejar-fase"><img src="https://agentmods.dev/badge/skills/fhdumont/code-ai-template/planejar-fase.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 651 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.00041 $0.00651
Opus 5 $0.00020 $0.00326
Sonnet 5 $0.00008 $0.00130
Haiku 4.5 $0.00004 $0.00065

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

Security

Grade A, and why

planejar-fase 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/planejar-fase/SKILL.md · 20 lines

What it actually says

Ritual de abertura do plan mode. As regras vivem em AGENTS.md (§O loop, §Docs vivos, §Inbox de achados); aqui está a ordem de execução.

Entre em plan mode antes do passo 1 — esta passada raciocina e escreve spec, e não toca em código.

  1. Esvazie o inbox. gh issue list --label achado --state open e leia o que houver. Deixe a triagem pro passo 6: o achado pode caber na fase que você está prestes a desenhar, e você só saberá depois de auditar.
  2. Carregue os vivos quentes. docs/SETUP.md (a fase atual — se tiver spec aberta, a fase ainda não fechou: pare e diga isso ao dono), docs/ROADMAP.md (o que vem) e CONTEXT.md (o vocabulário). Toque em área com débito conhecido? Some docs/DEBITO-TECNICO.md. CHANGELOG e DECISOES são frios: grep pelo ID quando precisar de um.
  3. Audite o código real. A fase candidata mexe em schema, enum ou estado persistido? Leia migrations, tipos e dados antes de qualquer pergunta — spec que presume estado inexistente custa uma fase inteira. Nomes de arquivo e símbolo que entrarem na spec saem daqui verificados. Dispare subagentes pra varrer em paralelo.
  4. Declare seu model/effort ao dono e, se ele estiver sub ou superdimensionado pra esta fase, peça a troca antes de seguir — sem esperar ele perguntar (CLAUDE.md §Model e effort).
  5. Rode o grilling com o material dos passos 1–3 na mão: os achados abertos entram na árvore de decisão como galhos candidatos ao escopo. O grilling fecha gravando a spec em docs/SETUP.md.
  6. Feche o inbox. Cada achado lido no passo 1 tem agora um destino: escopo da spec, linha nova no ROADMAP.md, item de DEBITO-TECNICO.md, ou ADR — inclusive ADR rejeitado, quando a resposta foi "não vamos fazer". gh issue close em cada um, citando pra onde foi.
  7. Entregue ao dono: a spec gravada, os achados fechados e o que cada um virou, e o Model/effort de execução recomendado. Ele aprova, dá /clear, e a execução é outra sessão.

Pronto = docs/SETUP.md com uma spec, zero issue achado aberta sem destino, e o dono sabendo qual model/effort abrir.

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 · 20 lines · 41 tokens per session scan A 965af672664a

Subscribe to this mod's changes

planejar-fase is a skill published in the GitHub repository FHDumont/code-ai-template (2 stars, last pushed 27d ago), licensed MIT. It adds 41 tokens to every session and 651 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens