What's inside

One SKILL.md (the playbook) + one starter template. A preview:

Spec-Driven Agent Workflow

The idea in one paragraph

Vibe coding asks an agent to write code from a feeling. Spec-driven development asks it to write code from a document. The pattern is simple: write requirements, write a design, break the work into tasks, then let the agent implement task by task. This skill adapts that pattern — visible in AWS Kiro's requirements.md/design.md/tasks.md flow and GitHub Spec Kit's specify/plan/tasks/implement stages — into a workflow any developer can run with any capable coding agent.

What it is built on

• "Vibe coding" was coined by Karpathy in February 2025 and named Collins's word of the year at the end of 2025 (per Imran Khan's November 2026 essay on Medium).
• Khan's essay argues the field is shifting to spec-driven development: AWS Kiro (July 2025, successor to Amazon Q Developer) starts from requirements.md, design.md, and tasks.md; GitHub Spec Kit (September 2025) adds specify, plan, tasks, and implement stages.
• The pressure behind the shift includes quality data: Veracode's 2025 report found roughly 45% of AI-generated code contained OWASP Top 10 vulnerabilities, with an 86% failure rate on XSS; METR research found developers using AI tools took 19% longer (while self-estimating they were 20% faster).

Workflow

1. Specify the requirements (input: feature idea -> output: requirements doc). Write what the feature must do, in testable statements, before any code exists. Include the non-goals: what this feature will not do. The agent never sees code until this exists.
2. Write the design (input: requirements -> output: design doc). Sketch the architecture, data flow, and interfaces the implementation must follow. The design is the contract the agent codes against; keep it short enough to fit in context.
3. Break into tasks (input: design -> output: task list). Split the work into tasks small enough to implement and verify one at a time. Order them so each task's output is the next task's input, and mark which tasks need your review.
4. Implement task by task (input: task list -> output: code). Feed the agent one task at a time with the requirements and design attached. Do not let it jump ahead; each task is reviewed before the next begins.
5. Verify against the spec (input: finished code -> output: pass/fail per requirement). Check every requirement statement against the implementation. Anything unmet goes back as a new task, not as a vague "fix it."
6. Freeze and file (input: verified code -> output: archived spec pack). Store the requirements, design, and task list with the code. The next person — or the next agent — inherits the reasoning, not just the output.

What good looks like

Template preview

Spec-Driven Feature Worksheet

1. Specify — requirements

Non-goals (what this feature will NOT do): -

2. Plan — design

Architecture sketch:

Data flow:

Interfaces:

3. Tasks

4. Implement — verification log

Buy the full skill pack — $4.99 Pro — all 531 skills