Just Try It

Just Try It

You don't want to read documentation. You want to see something happen. That's fine.

One-minute setup

Install AIWG and deploy it to your project:

npm install -g aiwg
cd /path/to/any/project     # or make an empty folder
aiwg use sdlc

Open Claude Code in that directory:

claude .

That's it — `aiwg use` already wired AIWG into the project (it wrote `CLAUDE.md` + `AIWG.md`), so it loads as the AIWG orchestrator on start.

If you pointed at an existing project (not an empty folder), run this once inside the tool first, so AIWG reconciles its context with what's already there:

/aiwg-regenerate

(No slash command? Ask it: "run aiwg-regenerate to wire AIWG into this project.")

Now ask it anything about your project:

What does this codebase do?
Find the most complex function and explain it.
What tests are missing?
Where would a security reviewer look first?

AIWG has pre-loaded 50+ specialized agents and rules. The AI will answer with the knowledge of a test engineer, security auditor, or architect — not a generic chatbot.

If you don't have a project to try it on

Make a folder, drop in one or two files, and run:

mkdir my-test && cd my-test
echo "console.log('hello')" > index.js
aiwg use sdlc
claude .

Then (this is a brand-new folder, so nothing to reconcile — just ask):

What would a senior engineer say about this code?

It will answer as one. That's what AIWG does.

What you just installed

`aiwg use sdlc` copied agent definitions, slash commands, skills, and behavioral rules into `.claude/` — and wrote `CLAUDE.md` + `AIWG.md`, the context that primes the AI as the AIWG orchestrator. Claude Code reads all of it automatically on start. On a fresh project it just works — no extra configuration.

On an existing project, or to pull in the latest AIWG on a project you set up earlier, run `/aiwg-regenerate` inside the tool: it re-tailors that context to your actual codebase and preserves any edits you've made.

What to explore next

Once you've seen it in action, pick a path: