talk-martinelli-spec-driven-development

talk-martinelli-spec-driven-development is a skill for Codex from jscraik/Agent-Skills. It costs 112 tokens per session (1,668 once invoked), scanned A, original, Apache-2.0.

A reference guide to a process where system use cases act as the main specifications and AI agents generate or regenerate code from them. A specification is a written description of required system behaviour.

In plain words
What is it for?
Use it to learn about spec-driven development, system use cases, architectural guardrails, and AI-assisted code generation.
Why use it?
It helps keep requirements stable while code changes, especially during large system modernisations.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to learn about spec-driven development, system use cases, architectural guardrails, and AI-assisted code generation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jscraik/agent-skills/talk-martinelli-spec-driven-development
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 jscraik/Agent-Skills --skill talk-martinelli-spec-driven-development
Clone the repo
git clone --depth 1 https://github.com/jscraik/Agent-Skills

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 talk-martinelli-spec-driven-development

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jscraik/agent-skills/talk-martinelli-spec-driven-development"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/talk-martinelli-spec-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 112 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,668 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.00112 $0.01668
Opus 5 $0.00056 $0.00834
Sonnet 5 $0.00022 $0.00334
Haiku 4.5 $0.00011 $0.00167

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

Security

Grade A, and why

talk-martinelli-spec-driven-development 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 8d 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.

Plugins/aidevcon/skills/talk-martinelli-spec-driven-development/SKILL.md · 104 lines

How it starts

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

Lessons from Spec-driven Development — Simon Martinelli

Simon Martinelli (Java Champion, owner of Martinelli LLC) presents the AI Unified Process: a process-centric, spec-driven approach where system use cases (Jacobson, 1987) are the central, stable artifact and code is generated/regenerated from them via AI agents equipped with skills, MCP servers, and architectural guardrails. He argues the approach works best when paired with self-contained systems (not microservices, not modular monoliths) and shares lessons from six customer projects including a large ERP modernization.

Grounding rules — MUST follow when answering

  1. Before answering any specific question, read outline.md to locate the relevant section, then read that section of transcript.md.
  2. When attributing words, quote short, non-sensitive excerpts from transcript.md. Never put quotation marks around paraphrased content.
  3. If a claim isn't in transcript.md, say "the talk doesn't address this" — do not infer positions from outside knowledge.
  4. Cite by transcript line range whenever possible.
  5. Speaker attribution is unreliable for Q&A portions — the source has no per-speaker labels. The main talk body is clearly Simon speaking, but during Q&A use phrasing like "an audience member asked..." and "Simon replied..." only when context makes the turn-taking clear. Do not invent attributions.
  6. The transcript has significant speech-to-text artifacts (garbled names, malapropisms like "spectrum development" for "spec-driven development", "music search" likely for something else, "Tessl" appears, "Ivar Jakob's own" for "Ivar Jacobson"). Quote short, non-sensitive excerpts but you may note [likely: X] when meaning is clearly garbled.

Standard lookup procedure

All task workflows below share this common first step — execute it before proceeding to task-specific instructions:

LOOKUP: Open quote.md for pre-extracted highlights relevant to the topic. If sufficient, use those. Otherwise open outline.md to locate the relevant section, then read that section of transcript.md. Always anchor answers in safe excerpts with line citations.

Read the full file on GitHub · 104 lines

Files

What ships with it

4 files 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. 8d ago First seen · 104 lines · 112 tokens per session scan A 8beb80c4e419

Subscribe to this mod's changes

talk-martinelli-spec-driven-development is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 112 tokens to every session and 1,668 once invoked, about $0.0006 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-09-03.