Fr-e-d

GAAI Framework — Testing skill for Claude Code

Testing community intermediate

95+ Drop-in governance layer (.gaai/ folder) -- backlog authorization, cross-session memory, decision tracking, QA gates, autonomous delivery daemon.

How to install GAAI Framework

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

What GAAI Framework does

A `.gaai/` folder you drop into any project. Markdown + YAML + bash. No SDK. No package. No external services.

Alternatives in Testing

Deliver — Delivery phase - Review, validate, and test with multi-AI quality assurance 2.8k ★
Agent Skills Spec — A skill is a folder of instructions, scripts, and resources that agents can discover and load dynamically to p 1.9k ★
Spec Driven Develop — Spec-driven development workflow for AI coding agents: architecture-first planning, task decomposition, GitHub 975 ★

README

GAAI — Governed Agentic AI Infrastructure

A `.gaai/` folder you drop into any project. Markdown + YAML + bash. No SDK. No package. No external services.

**GAAI turns AI coding tools into reliable agentic software delivery systems.**

See It in Action

You:        /gaai-discover
Discovery:  "What do you want to build?"
You:        "Add rate limiting — 100 req/min per user, 429 on exceeded."
Discovery:  "Got it. Checking memory for existing middleware patterns..."
            → Generates Epic E03 + Story E03S01 with acceptance criteria
            → Runs validation: artefact complete, criteria testable, no scope drift
            → Adds to backlog: status: refined
Discovery:  "Done. E03S01 is ready. Run /gaai-deliver when you're ready."

You:        /gaai-daemon
            → Launches the Delivery Daemon (polls backlog, delivers in parallel via tmux)
Delivery:   → Reads E03S01 from backlog
            → Loads middleware conventions from memory
            → Planning Sub-Agent: produces execution plan
            → Implementation Sub-Agent: adds rate-limiting middleware
            → QA Sub-Agent: all acceptance criteria PASS
            → Story marked done, PR merged to staging
Delivery:   "E03S01 complete. No further Stories in backlog."

Two slash commands. Two **isolated contexts**. Discovery reasons — it never executes. Delivery executes — it never decides scope. They never share a context window — Delivery runs as a separate OS process (`claude -p` via tmux), so system prompts can't contaminate each other. The backlog is the contract between them.

`/gaai-deliver` delivers a single Story in the current session. `/gaai-daemon` launches a background daemon that polls the backlog and delivers multiple Stories in parallel (each in its own tmux session). [See Delivery Daemon →](#delivery-daemon)