dev:auto:plan

dev:auto:plan is a skill for Claude Code from atournayre/claude-marketplace. It costs 23 tokens per session (728 once invoked), scanned A, original, MIT.

An automatic workflow step that creates an implementation plan for a software feature. It reads saved workflow decisions and architecture choices, then writes a Markdown specification file.

In plain words
What is it for?
Use it after the earlier workflow phases to create a feature plan in docs/specs/feature-{name}.md.
Why use it?
It turns earlier feature and architecture decisions into a written plan without asking more questions.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Part of the dev plugin — 25 skills, 8 agents shipped together

Good fit Use it after the earlier workflow phases to create a feature plan in docs/specs/feature-{name}.md.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atournayre/claude-marketplace/auto-plan
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 atournayre/claude-marketplace --skill auto-plan
Clone the repo
git clone --depth 1 https://github.com/atournayre/claude-marketplace

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 25 skills, 8 agents.

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 dev:auto:plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-plan/github.svg)](https://agentmods.dev/skills/atournayre/claude-marketplace/auto-plan)
Your own site
<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-plan"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-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.

agentmods 80×15 button for dev:auto:plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/auto-plan"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/auto-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 728 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.00023 $0.00728
Opus 5 $0.00012 $0.00364
Sonnet 5 $0.00005 $0.00146
Haiku 4.5 $0.00002 $0.00073

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

Security

Grade A, and why

dev:auto: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 12d 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.

dev/skills/auto-plan/SKILL.md · 128 lines

How it starts

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

Objectif

Instructions à Exécuter

IMPORTANT : Exécute ce workflow étape par étape :

Phase 5 du workflow automatisé : générer un plan d'implémentation détaillé basé sur l'architecture choisie SANS interaction.

Instructions

1. Lire le contexte

Déterminer le chemin du workflow state :

workflow_state_file=".claude/data/workflows/issue-${issue_number}-dev-workflow-state.json"
  • Lire le workflow state pour récupérer :
    • La feature description
    • Les décisions de clarification (Phase 3)
    • L'architecture choisie (Phase 4)
  • Si phases précédentes non complétées, exit avec erreur code 1

2. Générer le plan

Créer le fichier docs/specs/feature-{nom-kebab-case}.md avec le contenu suivant :

# Plan d'implémentation : {Feature Name}

## Résumé

**Feature :** {description}
**Approche :** {nom de l'approche choisie}
**Date :** {date du jour}

## Contexte

### Problème résolu
{description du problème}

### Décisions prises
- {décision 1}
- {décision 2}

## Architecture

### Composants
| Composant | Responsabilité | Fichier |
|-----------|---------------|---------|
| {nom} | {description} | `{chemin}` |

### Diagramme de flux

{représentation ASCII du flux}


## Plan d'implémentation

### Étape 1 : {titre}
- [ ] {tâche 1}
- [ ] {tâche 2}

**Fichiers :**
- `{chemin}` : {description}

### Étape 2 : {titre}
- [ ] {tâche 1}
- [ ] {tâche 2}

**Fichiers :**
- `{chemin}` : {description}

...

## Tests

### Tests unitaires
- [ ] {test 1}
- [ ] {test 2}

### Tests d'intégration
- [ ] {test 1}

3. Sauvegarder le chemin du plan

Mettre à jour le workflow state :

{
  "currentPhase": 5,
  "phases": {
    "5": {
      "status": "completed",
      "completedAt": "{ISO timestamp}",
      "durationMs": {durée},
      "planPath": "docs/specs/feature-{nom-kebab-case}.md",
      "components": ["{liste des composants}"],
      "implementationSteps": {nombre}
    }
  }
}

Règles

  • Mode automatique : aucune interaction
  • Générer le plan basé sur les phases précédentes
  • Créer le fichier docs/specs/ avec chemin correct
  • Documenter chaque étape d'implémentation
  • Jamais demander confirmation
  • Exit 1 si phases précédentes manquantes

Read the full file on GitHub · 128 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. 12d ago First seen · 128 lines · 23 tokens per session scan A 100ae6ba6ba4

Subscribe to this mod's changes

dev:auto:plan is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 728 once invoked, about $0.0001 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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens