Quick start

Install the blueprint for your tool, as described in Install.

Set up a project. Open a session in your project and run the ab-project-start skill, first thing in a new project or when you bring the blueprint into an existing one. Set up your project shows how to call it in each tool, and Codex offers it right after install. It adds AGENTS.md (with a one-line CLAUDE.md that imports it), docs/context/, BACKLOG.md and .agent-blueprint/.gitignore, merging into what is already there, then fills in conventions, goals and status from your code and a short conversation. It refuses to run in your home folder, and in a folder with files that is not a git repository it asks before writing. To add only the files without a session, run this from a clone of the repository:

bash install.sh --scaffold /path/to/your/project

Design your first feature. Ask for the ab-brainstorming skill with your idea. It checks what the repository already answers, compares two or three approaches, asks you to approve a design, and saves a plan under docs/plans/. It asks for that approval once, and a design you already approved, or told it to build, goes ahead without a second question. Read the plan before anything runs, because it holds the details the design left open.

Build it, choosing how much you want to watch:

• ab-build-pipeline runs the plan with a checkpoint after every stage.
• ab-ship-pipeline runs it end to end with no checkpoints.
• ab-orchestrate runs it as team work, in parallel waves.

Take the short path for small changes. A bug fix with an obvious cause, a typo, a config change or a test for existing behavior, touching under three files, goes through ab-quick-fix: a failing test, the fix, the whole test suite, a commit.

Hand over to the next session. Ask for ab-session-wrap at the end. It updates docs/context/STATUS.md from git history and the file system. Next time, ab-resume-session reads it back and tells you whether anything moved in between.