What is feature-spezifizieren?

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

Use it to create or revise specifications under specs/, document scope and exclusions, write user stories, and cover relevant normal, error, and edge cases.

It helps clarify what a feature should do, identify unanswered questions, and define how completion will be checked before implementation.

feature-spezifizieren — Skill by trojava

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.

agentmods

npx agentmods add skills/trojava/spec-driven-dev-kit/feature-spezifizieren

Any agent

npx skills add trojava/spec-driven-dev-kit --skill feature-spezifizieren

Clone the repo

git clone --depth 1 https://github.com/trojava/spec-driven-dev-kit

Made for: Claude Code, Codex.

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

When invoked 628 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00070	$0.00628
Opus 5	$0.00035	$0.00314
Sonnet 5	$0.00014	$0.00126
Haiku 4.5	$0.00007	$0.00063

Measured 2d ago against content hash 3d64e102ef52, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 56 lines

How it starts

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

Feature spezifizieren

Klärung

Prüfe, welches einzelne Feature spezifiziert werden soll.
Prüfe, ob docs/vision.md fachlich ausgefüllt ist. Wenn die Projektvision noch leer oder nur als Vorlage vorhanden ist, stoppe und unterstütze zuerst die Klärung der Projektvision.
Stelle zuerst gezielte Rückfragen zu Ziel, Umfang, Verhalten und relevanten Qualitätsanforderungen. Gib jeweils einen konkreten Vorschlag mit.
Warte auf die Antworten. Erstelle oder ändere in diesem Schritt noch keine Feature-Dateien.

Ablauf

Lies AGENTS.md, docs/vision.md, docs/prinzipien.md und specs/_vorlage/spezifikation.md.
Ermittle den Feature-Ordner. Falls er noch nicht existiert, lege ihn nach dem Muster specs/NNN-kurzer-name/ an und kopiere die drei Vorlagendateien hinein.
Erfasse Ziel, Nutzen, Umfang, Beteiligte und ausdrücklich ausgeschlossene Punkte.
Formuliere funktionale Anforderungen als User Stories mit eindeutigen, beobachtbaren Akzeptanzkriterien. Fasse zusammengehöriges Verhalten in einer Anforderung zusammen. Berücksichtige Normal-, Fehler- und Randfälle nur, wenn sie fachlich relevant sind.
Prüfe die Kategorien der nichtfunktionalen Anforderungen. Begründe kurz, wenn eine Kategorie nicht relevant ist.
Dokumentiere Annahmen, offene Fragen und Risiken in der Spezifikation. Stelle notwendige Rückfragen und gib jeweils einen konkreten Vorschlag mit.
Prüfe die Freigabekriterien am Dateiende. Setze den Status erst nach ausdrücklicher menschlicher Bestätigung auf Freigegeben.
Stoppe nach der Spezifikation. Erstelle weder Plan noch Aufgaben und beginne keine Umsetzung.

Grenzen

Ändere nur spezifikation.md sowie bei einem neuen Feature die aus der Vorlage kopierten Dateien.
Erstelle keinen technischen Plan und ändere keinen Quellcode.
Ersetze fehlende Informationen nicht durch erfundene Details.
Wiederhole keine Information in mehreren Abschnitten, wenn ein Verweis genügt.
Spezifiziere nicht automatisch weitere erkannte Features.

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

agents/openai.yaml 234 B

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.

2d 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 (5 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 628 once invoked, about $0.0003 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.

Documents Planning Productivity

systematic-debugging

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

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

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

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens