AI-Driven Development for Claude Code: Ideate -> Research -> a human decision gate in the browser -> Execute. Apply, Infer, or Innovate past every researched option.
AI-Driven Development framework: Ideate -> Research -> human decision gate in the browser -> Execution. Research produces a themed HTML gate where every option can be Applied, Inferred, or Innovated on; submitting compiles the choices into a binding markdown contract that drives the build.
Implements one vertical slice of an AIDD build under the decision contract. Reads decisions.md, respects APPLY/INFER/INNOVATE/DEFERRED stances, verifies by running the code. Use for parallel slices during the execution phase.
Themes the research gate HTML page for a specific project — palette, type, motif, hero — without touching the submission mechanism. Use during the AIDD gate phase after options.json validates.
Researches one decision segment exhaustively (docs, GitHub repos and code, registries, critiques, prior art) and returns a validated JSON fragment of options with pros, cons, and real sources. Use one scout per segment, launched in parallel, during the AIDD research phase.
Surveys an existing codebase before an AIDD run — what stack is in place, what conventions hold, what constraints bind, and which decisions are already closed. Use at the start of any AIDD run in brownfield mode, before research derives segments.
The AI-Driven Development framework — three phases (Ideate, Research, Execute) separated by a human decision gate rendered in the browser. Load when starting, resuming, or reasoning about an AIDD run, or when .aidd/ exists in the project.
The execution-phase quality bar — use the strongest technique the domain actually offers, and clear a real craft bar instead of shipping default-looking output. Domain-agnostic, with worked examples for visual/web, CLI, data, mobile, games, backend, and embedded work. Load during the AIDD execution phase.
How the AIDD browser decision gate works — the options.json schema, the submission payload contract, theming rules, and the serve-and-wait loop. Load when building, theming, serving, or debugging the research gate page.
How to turn a passed AIDD decision gate into a build — reading the contract, honouring APPLY/INFER/INNOVATE/DEFERRED, writing the charter, slicing the work, and handling contract drift. Load during the AIDD execution phase.
Protocol for the AIDD research sweep — deriving decision segments, multi-directional searching, source discipline, and writing options.json plus dossier.md. Load during the AIDD research phase or when building gate options.
2 24d agoA45 tokens
originalMIT
At most 3 mods per repository are shown here — the rest are on their repository pages: