GrillerGeek

Idd Framework — AI skill for Claude Code

AI community

A process framework for teams building software with AI coding agents.

How to install Idd Framework

This entry records only its repository, not the path inside it, so there is no exact command to give. Open GrillerGeek/idd-framework and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Idd Framework does

A process framework for teams building software with AI coding agents. Replaces Epics/Features/Stories with Product → Intentions → Expectations → Specs.

Alternatives in AI

  • Codebase Digest — 🗜️ Codebase-digest is your AI-friendly codebase packer and analyzer 375 ★
  • Gem Team — Turn AI coding into an engineering process 210 ★
  • Stacklit — One command gives AI agents instant codebase context 102 ★

README

Intent-Driven Development Framework

[![License: CC BY-SA 4.0](https://img.shields.io/badge/License-CC_BY--SA_4.0-lightgrey.svg)](https://creativecommons.org/licenses/by-sa/4.0/) [![Claude Code Plugin](https://img.shields.io/badge/Claude_Code-plugin-blueviolet.svg)](https://claude.com/claude-code) [![Framework](https://img.shields.io/badge/framework-v1.3-green.svg)](docs/framework.md)

**A process framework that gives developers and AI agents enough context to make decisions autonomously — without waiting for someone to tell them what to do.**


The Problem

In most agile teams, knowledge lives in the Product Owner's head. Developers wait for clarification. AI agents guess when context is missing. Every ambiguous user story becomes a decision bottleneck — someone has to ask a question, wait for an answer, or make an assumption and hope it's right.

Traditional agile methodologies were also designed for a world where human coding capacity was the primary constraint. AI coding agents have changed that equation. When the build phase compresses 5–10x, the bottleneck shifts from *building* to *defining, reviewing, and validating* — and every gap in context produces wrong output at machine speed.

The frameworks haven't caught up. Teams are using 2-week sprints to manage work that takes 2 hours to build. They're estimating story points for tasks where effort is no longer the dominant variable. They're holding planning meetings to decompose work that AI agents can execute from a well-written specification.

The Framework

Intent-Driven Development (IDD) replaces work-decomposition with purpose-decomposition. Instead of asking *"what should developers work on this sprint?"* IDD asks *"what does this product need to be, and how do we know it's right?"*

**The core principle:** The IDD hierarchy is not a chain of command — it's a **chain of context**. Each layer gives developers and AI agents the information they need to make implementation decisions independently