Guides
Knowledge compounding
ab-knowledge-compounding writes each solved problem up with its root cause, the solution, the approaches that failed and the terms to search for. ab-build-pipeline and ab-ship-pipeline run it after review when the work solved a non-trivial problem, and you can ask for it after any fix whose lesson the code, the tests and the commit message do not carry.
Each solved problem becomes a searchable document in docs/, which ab-brainstorming and ab-deep-research search before new work.
Skills in this guide
- Completion
ab-knowledge-compounding
Records a solved problem in
docs/solutions/with search terms and cross-linksUse when: After a non-trivial problem
- Pipelines
ab-build-pipeline
Runs a feature through eight supervised stages (discuss, brainstorm, plan, execute, review, verify, optional deploy check, knowledge capture) with a checkpoint after each
Use when: A feature you approve stage by stage
- Pipelines
ab-ship-pipeline
Ships a feature end to end with no checkpoints, tracked in
.agent-blueprint/run/state.json; the ship runner drives it unattendedUse when: A well-defined feature you want built hands-off
- Design
ab-brainstorming
Turns an idea into an approved design: settles what the repository answers, challenges the premise, compares two or three approaches, saves the plan. Never asks twice for a design you approved
Use when: Before any new feature
- Design
ab-deep-research
Researches a topic with five helpers in parallel and writes one synthesized brief
Use when: Before planning something unfamiliar