Section 5
Module 5: Tooling and Ecosystem
Agent OS for the feature lifecycle, high-rigor agentic IDEs like Amazon Kiro, and MCP as the runtime bridge to your stack.
"Specs define intent. Tooling enforces the lifecycle and connects agents to reality at runtime.
Lessons
Lesson 1 · ~6 min
Agent OS
Persistent project memory (/plan product), shape-spec, requirements gate, atomic tasks, and implement vs orchestrate — Builder Methods AgentOS discipline.
Lesson 2 · ~6 min
Amazon Kiro
High-rigor agentic IDE — Requirements, Design, Tasks; EARS; mission/roadmap/tech-stack artifacts; enforcement with evidence.
Kiro spec triad
requirements · design · tasks
steering.md, requirements.md, design.md, tasks.md — needs, must-include rules, and readiness on the execution spine.
Lesson 3 · ~6 min
Model Context Protocol (MCP)
Runtime diagnostic bridge — bounded autonomy, JSON-RPC tools, Playwright journeys, and evidence like LCP metrics.
Kiro spec triad
requirements.md (what), design.md (how), tasks.md (steps) — each with clear must-include rules.
requirements.mdWhatDefines what is being built — user outcomes and acceptance criteria (EARS).
design.mdHowArchitecture and approach before implementation — structure agents must follow.
tasks.mdStepsConcrete, ordered work the AI executes one task at a time with verification.
Feature lifecycle (Agent OS)
Each stage is a system call — agents and humans run the same pipeline.
/plan product
Once at project start — plan.md, roadmap.md, techstack.md as durable context.
High-rigor documentation artifacts
| File | Problem it prevents |
|---|---|
| plan.md | Feature drift |
| roadmap.md | Priority hallucinations |
| techstack.md | Stack guessing |
Practical Takeaways
- 1AgentOS: /plan product → plan.md, roadmap.md, techstack.md; shape-spec → requirements gate; /create-tasks → atomic tasks.md.
- 2Choose implement tasks (control) or orchestrate tasks (speed) — specialists see only relevant context.
- 3Kiro-class rigor: requirements.md + design.md + tasks.md with EARS and evidence before code.
- 4plan.md, roadmap.md, techstack.md prevent feature drift, priority hallucinations, and stack guessing.
- 5steering.md: persistent memory (stack, standards); requirements.md: the what for one feature on the execution spine.
- 6MCP + Runtime Gateflow: Playwright → DevTools evidence → map to spec → propose verified fix.
- 7High-rigor tooling turns SDD from philosophy into repeatable, auditable practice.