Talk Martinelli Spec Driven Development
Answers questions about, summarises key insights from, and helps apply concepts from Simon Martinelli's talk "Lessons from Spec-driven Development" — providing verbatim-grounded explanations, audits, and artifact drafts. Use when the user asks about the AI Unified Process, system use cases as specs (vs user stories), self-contained systems vs microservices, skills/MCP servers/guardrails, AI-assisted ERP modernization, drift management, how architecture style impacts AI coding agents, or applying his spec-driven approach to current work.
Install
npx skills add jscraik/Agent-Skills --skill talk-martinelli-spec-driven-developmentgit clone --depth 1 https://github.com/jscraik/Agent-Skills.git /tmp/Agent-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/Agent-Skills/Plugins/aidevcon/skills/talk-martinelli-spec-driven-development ~/.claude/skills/talk-martinelli-spec-driven-developmentPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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.
Details
- Skill name
talk-martinelli-spec-driven-development- Repository
- jscraik/Agent-Skills
- Path
Plugins/aidevcon/skills/talk-martinelli-spec-driven-development/SKILL.md- License
- Apache-2.0
- Repo updated
- 16 November 2026
FAQ
What does the Talk Martinelli Spec Driven Development skill do?
Answers questions about, summarises key insights from, and helps apply concepts from Simon Martinelli's talk "Lessons from Spec-driven Development" — providing verbatim-grounded explanations, audits, and artifact drafts. Use when the user asks about the AI Unified Process, system use cases as specs (vs user stories), self-contained systems vs microservices, skills/MCP servers/guardrails, AI-assisted ERP modernization, drift management, how architecture style impacts AI coding agents, or applying his spec-driven approach to current work.
How do I install the Talk Martinelli Spec Driven Development skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jscraik/Agent-Skills --skill talk-martinelli-spec-driven-development. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Talk Martinelli Spec Driven Development popular?
It lives in jscraik/Agent-Skills, which has 9 GitHub stars and 4 forks.
Related skills
1password
9jscraik/Agent-Skills
Plan, diagnose, and validate 1Password CLI workflows. Use when tasks need op CLI sign-in, secret references, op run, op inject, item reads, env injection, or service-account secret access.
Agentation
9jscraik/Agent-Skills
Audit, validate, and troubleshoot Agentation integrations in frontend apps. Use when annotations, MCP registration, endpoint sync, webhook delivery, or watch mode readiness are failing.
Agents Md
9jscraik/Agent-Skills
Use when reviewing, creating, shrinking, or refactoring AGENTS.md and directly linked instruction guidance for stale or conflicting rules against current model documentation, scoped routing, deduplication, or progressive disclosure.
Talk Podjarny Skills Are the New Code
9jscraik/Agent-Skills
Assists with questions about Guy Podjarny's talk "Skills are the new Code". Use when the user wants to understand, apply, audit, or explore frameworks from this keynote — including the five engineering disciplines for skills (static analysis, evals, security testing, dependency management, observability), the three challenge buckets, the agentic development stack, or concepts like skill authoring, context engineering, agent harnesses, and skill quality scoring.
Talk Foxwell Reinvention Dev Team
9jscraik/Agent-Skills
Assists with questions about Hannah Foxwell's talk 'The Reinvention of the Dev Team'. Use when a user asks about Foxwell's arguments on agentic software development, engineering team composition, AI-driven velocity, dev-to-PM ratios, the three anchors (build something worth building, speed requires safety, people matter), the Keep/Trash/Try inventory, on-call sustainability, broken-comb skills, or wants to audit their own team against Foxwell's framework.
Talk Sloan Harness Engineering Beyond Code
9jscraik/Agent-Skills
Summarizes Rob Sloan's harness-engineering talk and creates safe design artifacts for agent context beyond code: product-intent packets, design constraints, acceptance criteria, context ownership, and review gates. Use when the user asks about making non-code context agent-ready or improving AI work with product/design intent.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.