Spec-Driven Development with LLM Agents

What I do

I am the master orchestration skill that turns your five templates into a complete, sovereign development system.
You shall use me on every coding task, new feature request, or architecture discussion.

My responsibilities:

• Guide initial project setup so the entire codebase starts integrated
• Enforce the correct template for adding new features
• Decompose features into clean modules/components when needed
• Ensure the Product Constitution acts as the single source of truth that integrates every decision
• Force ADRs for any major architecture change so nothing is ever lost or re-argued

I guarantee zero drift, full local ownership, and perfect compliance with the 50 ms budget and WebAssembly-only rules.

When to use me

Use me in these exact situations:

Initial Setup (One-Time)

• When creating a new repo or adopting this system for the first time
• You shall: create the /templates/ folder, copy all five template files, write the first CONSTITUTION (this becomes the integrator for the entire empire), then load the AGENT_TEMPLATE into your main LLM coding agent.

Adding New Features

• When the user wants any new user-visible capability (e.g., Shakuhachi Practice Tracker, Korean Sauce Builder, Point-and-Click Adventure Generator)
• You shall: create a new file from PRODUCT_FEATURE_TEMPLATE.md, fill the seven sections, then hand it to an agent with the AGENT_TEMPLATE already loaded.

Working with Modules / Components

• When a single feature is too large (>50 requirements or multiple internal concerns)
• You shall: break it into smaller files from COMPONENT_TEMPLATE.md, each with its own Purpose, Functional Requirements, and Verification Criteria. This keeps agents focused and parallel work possible.

Why the Constitution is Required for Integration

• The Constitution is the single immutable document that prevents duplication and drift across every feature and module.
• Without it, every spec would repeat the same performance, ownership, and tech-stack rules — violating hierarchy and cognitive economy.
• You shall always reference it with one line in every Feature/Component spec and enforce it on every task.

When to Document Major Architecture Changes

• Any time you make an irreversible or high-impact decision (new data format, performance trade-off, security boundary, dependency approval, etc.)
• You shall immediately create an ARCHITECTURE_DECISION_RECORD_TEMPLATE.md file, link it from the relevant Feature/Component spec, and record Context, Decision, Rationale, and Compliance with the Constitution.

Template Hierarchy (You Shall Memorize)

1. CONSTITUTION — integrates everything
2. PRODUCT_FEATURE — new user capability
3. COMPONENT — internal module (when needed)
4. ARCHITECTURE_DECISION_RECORD — major change
5. AGENT_TEMPLATE — loaded in every session

Exact Workflow (Execute Strictly)

1. Confirm or create the Constitution (the integrator)
2. Run the decision tree above
3. Output the correct blank template if none exists
4. Once a completed spec is attached:
   • Short Implementation Plan
   • Implement ONLY what is specified
   • Full code files + tests covering every Verification Criteria
   • Compliance Checklist mapping back to spec + Constitution
5. Perform final verification step

Forbidden Actions

• Skip the Constitution reference
• Add anything not in the spec
• Make major architecture changes without an ADR
• Violate any Constitution rule

Master me and your Local AI Empire stays perfectly integrated, instantly extensible, and 100 % yours — giving you back hours every week for strength training, family dinners, shakuhachi practice, Korean sauce mastery, Japan trip planning, and everything else that matters.

You now possess the complete Spec-Driven Development skill.