RAPID handbook
Direction is the new delivery skill.
AI agents do the building. Engineers set direction, review the evidence and authorise the irreversible. RAPID keeps enterprise rigour inside that faster loop.
Pipeline once
Loop forever
- 01Definitionresearch → PFD
- 02Designflows · data · screens
- 03Tech selectionstack + tools
- 04Buildsoftware + docs/tests
- 05Refinementacceptable → good
- 06Flow-statefriction → flow
- 07Productionsecure · shipped · operable
Documentation, tests and security run through every phase.
Start where you are.
RAPID has an adoption programme, a product lifecycle and an operational toolkit. Choose the question in front of you; the site will take you to the right layer.
Work phase by phase.
Pick the phase you are in. The outcome, gate and first operational artefacts stay together, so the process becomes a workspace rather than a reading exercise.
01
research → PFD
Definition
Turn raw insight into a plan an agent can build from without inventing the domain.
- Outcome
- A research-backed, testable Product Feature Definition.
Start with these
- TemplatePFD →
- TemplatePFD rubric →
- PromptPFD first draft →
- SkillPFD drafting →
64
The work already has a shape.
There are 64 core gate cards, templates, prompts, skill specs and register schemas, plus the scaffold, radar, training and metrics foundations. Status is shown honestly: available does not always mean proven.
Browse by phase and job →The human stops typing, not deciding.
RAPID moves execution to the agent and judgement up to the people accountable for the outcome. The boundary stays visible at every gate.
Humans
- Set direction and define the acceptable outcome.
- Make domain, taste and trade-off decisions.
- Review evidence and challenge test honesty.
- Authorise irreversible actions.
Agents
- Investigate the codebase, domain and options.
- Build and verify in bounded, reviewable loops.
- Keep documentation and tests with the change.
- Capture memory, runbooks and reusable skills.
Adoption is not a lifecycle phase.
STOP · GO · BUILD changes the organisation. Definition → Production delivers a product. The toolkit supports both. Keeping those systems separate makes the next decision obvious.
One bounded change is enough to begin.