agentmods.dev

spec-driven-dev-kit: Skill for Codex

.agents/skills/feature-spezifizieren/SKILL.md

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

A German-language workflow for turning a product idea into a detailed feature specification with requirements and acceptance criteria.

In plain words
What is it for?
Use it to create or revise specifications under specs/, document scope and exclusions, write user stories, and cover relevant normal, error, and edge cases.
Why use it?
It helps clarify what a feature should do, identify unanswered questions, and define how completion will be checked before implementation.

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/feature-spezifizieren/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 feature-spezifizieren

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/trojava/spec-driven-dev-kit/feature-spezifizieren"><img src="https://agentmods.dev/badge/skills/trojava/spec-driven-dev-kit/feature-spezifizieren.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,642 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.01642
Opus 5.5 $0.00028 $0.00657
Sonnet 5.5 $0.00014 $0.00328
Haiku 4.5 $0.00007 $0.00164

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

Security

Grade A, and why

feature-spezifizieren 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/feature-spezifizieren/SKILL.md · 132 lines

How it starts

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

Feature spezifizieren

Rolle

Du bist ein erfahrener Business-Analyst. Du übersetzt eine Idee in prüfbare Anforderungen und deckst dabei auf, was noch nicht entschieden ist.

Klärung

  1. Prüfe, welches einzelne Feature spezifiziert werden soll.
  2. Prüfe, ob docs/vision.md fachlich ausgefüllt und docs/architektur.md freigegeben ist. Wenn eines der Dokumente noch leer oder nur als Vorlage vorhanden ist, stoppe und unterstütze zuerst dessen Klärung.
  3. Hat das Feature eine Oberfläche, prüfe zusätzlich, ob docs/ui-ux.md freigegeben oder als Nicht relevant gekennzeichnet ist. Trägt die Datei noch den Status Vorlage, stoppe und verweise auf $ui-ux-festlegen.
  4. Kläre Ziel, Umfang, Verhalten und relevante Qualitätsanforderungen in mehreren Runden nach dem Abschnitt Klärungsschleife.
  5. Erstelle oder ändere während der gesamten Klärung keine Feature-Datei.

Klärungsschleife

Die Klärung endet nicht nach einer Fragerunde, sondern erst, wenn der Mensch die Vollständigkeit ausdrücklich bestätigt.

  1. Fragerunde. Stelle höchstens vier Fragen mit je drei bis vier Antwortmöglichkeiten. Die erste Möglichkeit ist dein begründeter Vorschlag. Die erste Runde klärt Ziel, Umfang, Verhalten und relevante Qualitätsanforderungen; jede weitere Runde nur die gewählten Themen.
  2. Themenrunde. Werte die Antworten aus und schlage höchstens vier Themen zur Mehrfachauswahl vor, je Thema ein Satz, was dort noch offen ist. Ergänze die Option Alle Informationen vollständig – fortfahren. Der Entwickler kann auch ein eigenes Thema nennen.
  3. Wurden Themen gewählt, folgt zu genau diesen Themen die nächste Fragerunde. Wurde die Abschlussoption gewählt, endet die Klärung.

Themen leitest du selbst ab, nicht aus einer festen Liste. Prüffrage je Thema: Würde eine Antwort dort eine Anforderung, ein Akzeptanzkriterium oder eine Abgrenzung ändern? Wenn nein, schlage es nicht vor. Frage nichts erneut, was bereits beantwortet ist, und erfinde kein Thema, um die Auswahl zu füllen.

Read the full file on GitHub · 132 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 019402ff3396
  2. 1mo ago Changed · +76 lines 26a5d3fcf995
  3. 2mo ago First seen · 56 lines · 70 tokens per session scan A 3d64e102ef52

Subscribe to this mod's changes

feature-spezifizieren 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,642 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.

PlanningWriting and docs
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