agentmods.dev

spec-driven-dev-kit: Skill for Codex

.agents/skills/umsetzung-planen/SKILL.md

umsetzung-planen is a skill for Codex from trojava/spec-driven-dev-kit. It costs 70 tokens per session (1,338 once invoked), scanned A, original, MIT.

A planning aid for turning an approved feature specification into either a technical implementation plan or a task list. It works with project guidance, existing code, and the feature folder.

In plain words
What is it for?
Use it to create or complete plan.md or aufgaben.md for an approved feature. It maps requirements to plan steps and checks, and identifies decisions that need human approval.
Why use it?
It helps prevent missing requirements and separates planning from coding. It also makes decisions, tests, security, data changes, and rollback needs explicit before work begins.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md; $skill-name invocation.

This is trojava/spec-driven-dev-kit's own configuration. It tells Codex how to work on spec-driven-dev-kit 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 spec-driven-dev-kit configures →

not rated 9repo changed 1mo ago A scan 70 tokens original MIT
View source ↗ trojava/spec-driven-dev-kit
Reuse

Borrowing it

Nothing to install: this file belongs to trojava/spec-driven-dev-kit. 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/trojava/spec-driven-dev-kit/main/.agents/skills/umsetzung-planen/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/trojava/spec-driven-dev-kit

Made for: Codex.

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 umsetzung-planen

README.md
[![agentmods](https://agentmods.dev/badge/skills/trojava/spec-driven-dev-kit/umsetzung-planen/github.svg)](https://agentmods.dev/skills/trojava/spec-driven-dev-kit/umsetzung-planen)
Your own site
<a href="https://agentmods.dev/skills/trojava/spec-driven-dev-kit/umsetzung-planen"><img src="https://agentmods.dev/badge/skills/trojava/spec-driven-dev-kit/umsetzung-planen/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 umsetzung-planen

Your own site · 80×15
<a href="https://agentmods.dev/skills/trojava/spec-driven-dev-kit/umsetzung-planen"><img src="https://agentmods.dev/badge/skills/trojava/spec-driven-dev-kit/umsetzung-planen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,338 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.00070 $0.01338
Opus 5.5 $0.00028 $0.00535
Sonnet 5.5 $0.00014 $0.00268
Haiku 4.5 $0.00007 $0.00134

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

Security

Grade A, and why

umsetzung-planen 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 1mo 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.

.agents/skills/umsetzung-planen/SKILL.md · 115 lines

How it starts

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

Umsetzung planen

Rolle

Du bist ein erfahrener Software-Entwickler mit Planungserfahrung. Du entwirfst aus freigegebenen Anforderungen einen tragfähigen Lösungsweg und schneidest ihn in einzeln prüfbare Aufgaben.

Voraussetzungen

  • Lies AGENTS.md, die Projektdokumente einschließlich docs/ui-ux.md, alle Dateien des Feature-Ordners und den Schnittstellenvertrag unter api/.
  • Beginne nur, wenn der Benutzer den Plan ausdrücklich beauftragt hat und spezifikation.md und adr.md den Status Freigegeben haben und keine blockierenden Fragen enthalten. Fehlen die Architekturentscheidungen, stoppe und verweise auf $architektur-festlegen.

Plan erstellen

Der Plan besteht aus zwei Teilen in einer Datei: der Lösungsskizze, die beantwortet, wie das Feature gebaut wird, und der Aufgabenliste, die die Arbeit in prüfbare Schritte schneidet und ordnet. Beide entstehen in einem Durchgang und werden gemeinsam freigegeben.

Lösungsweg

  1. Untersuche den bestehenden Code und die betroffenen Schnittstellen.
  2. Beschreibe unter Lösungsweg in fünf bis zehn Zeilen den technischen Weg.
  3. Nenne unter Betroffene Bereiche als Stichpunkte, was sich ändert: Dateien, Komponenten, Schnittstellen, Datenmodell.
  4. Beschreibe unter Prüfung das Vorgehen, nicht die Zuordnung je Anforderung.
  5. Nimm Sicherheit, Datenschutz, Datenänderungen, Betrieb und Rücknahme nur auf, wenn dort etwas gilt. Begründe nicht, was nicht zutrifft.
  6. Setze die Entscheidungen AD-xx und die Vorgaben A-xx und U-xx um, ohne sie zu wiederholen. Ergibt sich eine neue wesentliche Entscheidung, stoppe und lasse sie zuerst in adr.md klären. Ist eine Abweichung von U-xx nötig, stoppe und verweise auf $ui-ux-festlegen.
  7. Setze eine Schnittstelle nach dem Vertrag unter api/ um, ohne sie neu zu entwerfen. Braucht der Lösungsweg eine Änderung am Vertrag, stoppe und verweise auf $architektur-festlegen.
  8. Plane bei Oberflächenarbeit für jede betroffene Ansicht die fachlich möglichen Zustände aus docs/ui-ux.md mit ein.

Read the full file on GitHub · 115 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago Changed · +5 lines · +2 tokens per session d9da45fc2236
  2. 1mo ago Changed · +46 lines 722be02bc5e1
  3. 2mo ago First seen · 64 lines · 68 tokens per session scan A 36be34e1661a

Subscribe to this mod's changes

umsetzung-planen is a skill published in the GitHub repository trojava/spec-driven-dev-kit (9 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 1,338 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-08-31.

Planning
Related

Other skills, from other repositories

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

systematic-debugging

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

obra/superpowers · 21 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