What is matilha-plan?

A planning skill for projects split into several subprojects or parallel workstreams. It creates a written specification and plan with ordered phases, work groups, merge order, and completion checks.

Use it to turn research into implementation plans, divide work into parallel waves, define what must be completed first, and record when each phase is ready to close.

Parallel development can create unclear dependencies and conflicts when people or agents work in the wrong order. This gives the work a shared structure before implementation begins.

matilha-plan — Skill for Claude Code by danilods

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add danilods/matilha-skills --skill matilha-plan

Clone the repo

git clone --depth 1 https://github.com/danilods/matilha-skills

Made for: Claude Code.

Or install matilha, the plugin that ships this one along with the rest of its 12 skills, 10 commands, 2 agents, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/danilods/matilha-skills/matilha-plan/github.svg)](https://agentmods.dev/skills/danilods/matilha-skills/matilha-plan)

Your own site

<a href="https://agentmods.dev/skills/danilods/matilha-skills/matilha-plan"><img src="https://agentmods.dev/badge/skills/danilods/matilha-skills/matilha-plan/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/danilods/matilha-skills/matilha-plan"><img src="https://agentmods.dev/badge/skills/danilods/matilha-skills/matilha-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,290 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.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.01290
Opus 5	$0.00021	$0.00645
Sonnet 5	$0.00008	$0.00258
Haiku 4.5	$0.00004	$0.00129

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

Security

Grade A, and why

matilha-plan 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 11d 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.

skills/matilha-plan/SKILL.md · 86 lines

How it starts

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

When this fires

User has Phase 10 research (or skips scout) and wants spec + plan artifacts before dispatching work. Produces docs/matilha/specs/<slug>-spec.md + docs/matilha/plans/<slug>-plan.md.

Preconditions

None. matilha-plan lazy-bootstraps project structure as needed.

Execution Workflow

Lazy bootstrap: Check for project-status.md and docs/matilha/. If absent, create minimally:
- mkdir -p docs/matilha/specs docs/matilha/plans docs/matilha/research
- If project-status.md missing, write a minimal stub with frontmatter current_phase: 10, phase_status: in_progress, project_slug: <derived from cwd or user-provided>, next_action: "matilha-plan in progress". User can later run matilha-init for fuller bootstrap.
- Then read project-status.md and any existing research in docs/matilha/research/.
Pack-aware brainstorming delegation (see matilha-compose for canonical template):
- (a) If superpowers:brainstorming is available, inspect the ambient skill list for skills with plugin namespace matching matilha-*-pack (installed companion packs). Group by plugin namespace.
- (b) Classify user intent semantically against each installed pack's domain using the pack skills' descriptions visible in the ambient list. Err inclusive — prefer injecting a marginally-relevant pack over omitting it.
- (c) Build preamble using the canonical template documented in skills/matilha-compose/SKILL.md Step 4 (per-pack mini-synthesis + skill list + guidance paragraph for the receiving skill).
- (d) Emit the preamble in the current turn output, then invoke superpowers:brainstorming via the Skill tool.
- (e) Fallback: if superpowers:brainstorming is absent OR zero packs are detected, run the condensed clarifying flow inline (existing behavior — ask 3–5 questions drawing on detected pack skills if any, else use methodology-core heuristics).
Write docs/matilha/specs/<slug>-spec.md with: purpose, context, design principles, target deliverables, architecture, data flow, open questions, exit criteria.
If superpowers:writing-plans available, invoke via Skill tool to generate the task-by-task plan. Otherwise, write the plan inline following methodology/40-execucao.md conventions.
Plan output lands at docs/matilha/plans/<slug>-plan.md with: goal, architecture, SPs, per-task steps, exit gates.
Update project-status.md: current_phase: 30, phase_status: complete, feature_artifacts appended, next_action: "Run /matilha-hunt <slug>".

Read the full file on GitHub · 86 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.

11d ago First seen · 86 lines · 42 tokens per session scan A aff999710eae

Subscribe to this mod's changes

matilha-plan is a skill published in the GitHub repository danilods/matilha-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,290 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.

Claude Code Planning agent-orchestration agentic-patterns ai-assisted-development anthropic claude-code-plugin matilha

skill-dev

Use this skill when creating or refining Claude Code skill definitions. Skills are model-invoked capabilities that Claude activates autonomously based on context. Helps design focused skills with discovery-optimized descriptions, proper directory structures, and supporting resources. Automatically invoked when user…

andisab/swe-marketplace · 86 tokens

command-dev

Use this skill when creating or refining custom Claude Code slash commands. Slash commands are user-invoked reusable prompts that can accept arguments, reference files, and execute bash operations. Helps design command syntax, argument handling, file references, bash execution, and frontmatter configuration.…

andisab/swe-marketplace · 85 tokens

plugin-dev

Use this skill when creating or refining Claude Code plugins. Plugins are bundled collections of agents, skills, commands, hooks, and MCP servers that provide cohesive functionality. Helps design proper directory structures, plugin.json configuration, marketplace distribution, and installation workflows. Automatically…

andisab/swe-marketplace · 76 tokens

agent-dev

Use this skill when creating or refining Claude Code sub-agent definitions. Helps design specialized AI assistants with proper YAML frontmatter, system prompts, tool access, and example-driven descriptions. Automatically invoked when user requests "create an agent", "design a sub-agent", "make a specialist", or…

andisab/swe-marketplace · 86 tokens

mcp-server-dev

Create MCP servers — multi-tool services exposed via Model Context Protocol. Use this skill whenever users mention MCP servers, building servers, server scaffolding, tool registration, or want to package tools for distribution via uvx or npx. Also use when the conversation involves stdio transport, server lifecycle…

andisab/swe-marketplace · 175 tokens

mcp-tool-dev

Create MCP tools — individual tool functions exposed via Model Context Protocol. Use this skill whenever users mention MCP tools, tool handlers, tool functions, tool definitions, or want to add capabilities to an MCP server. Also use when the conversation involves designing tool schemas, writing tool descriptions, or…

andisab/swe-marketplace · 158 tokens