Journeys
How the stages combine.
Not every piece of work takes the same route. These are three common starting points, and the path each one takes through discovery, refinement, planning, implementation, validation, and review. The red outlines mark where you make the decision.
Brainstorm
Round out one bounded facet with you
Round out one bounded facet with you
Research, prototype
Evidence for open questions
Evidence for open questions
Configure
Ground agents in the project. You confirm.
Ground agents in the project. You confirm.
Discovery
A large, foggy idea mapped over many sessions
A large, foggy idea mapped over many sessions
Refine work
Shaped level by level until it is ready to build
Shaped level by level until it is ready to build
Sequence work
Order, parallel work, and blockers
Order, parallel work, and blockers
Plan
A technical plan for the next ready item
A technical plan for the next ready item
Implement
One bounded change, test-driven
One bounded change, test-driven
Validate
Evidence against the acceptance criteria
Evidence against the acceptance criteria
Review
Independent judgement on the change
Independent judgement on the change
You merge
Or ask for another cycle
Or ask for another cycle
Evaluate session
Learn from how the work went
Learn from how the work went
Throughout: domain terms and architecture decisions are recorded as they settle, and handoffs let any session continue where the last one stopped.
facet
settled
ask
evidence
gaps
next item
fix
look back
remediation
Journey 1 · Greenfield
From a large idea to working software
A broad idea becomes a mapped system, then ready work, then reviewed changes.
You decide
Loops back
Journey 1 · Greenfield
From a large idea to working software
A broad idea becomes a mapped system, then ready work, then reviewed changes.
You decide Loops back
- 01ConfigureGround agents in the project. You confirm.
- 02DiscoveryA large, foggy idea mapped over many sessionsfacet ⇄ settledBrainstormRound out one bounded facet with you
- 03Refine workShaped level by level until it is ready to buildask ⇄ evidenceResearch, prototypeEvidence for open questions↺ gaps: back to Discovery
- 04Sequence workOrder, parallel work, and blockers
- 05PlanA technical plan for the next ready item
- 06ImplementOne bounded change, test-driven
- 07ValidateEvidence against the acceptance criteria↺ fix: back to Implement
- 08ReviewIndependent judgement on the change↺ remediation: back to Implement
- 09You mergeOr ask for another cycle↺ next item: back to Sequence work
- 10Evaluate sessionLearn from how the work went
Throughout: domain terms and architecture decisions are recorded as they settle, and handoffs let any session continue where the last one stopped.
Rationale
Why the system took its shape
Why the system took its shape
Inspect environment
What is really deployed
What is really deployed
Configure
Ground agents in the project. You confirm.
Ground agents in the project. You confirm.
Understand codebase
How it actually works today
How it actually works today
Assess architecture
Structural problems, prioritised
Structural problems, prioritised
Record decisions
Target decisions you make, kept as ADRs
Target decisions you make, kept as ADRs
Discovery
The rework mapped across sessions
The rework mapped across sessions
Refine work
Slices you agree, ready to build
Slices you agree, ready to build
Sequence work
Which slice can ship next
Which slice can ship next
Plan
A technical plan for one slice
A technical plan for one slice
Implement
Test-driven, old and new side by side
Test-driven, old and new side by side
Validate
Evidence against the acceptance criteria
Evidence against the acceptance criteria
Review
Independent judgement on the change
Independent judgement on the change
You merge
Or ask for another cycle
Or ask for another cycle
Throughout: decisions are recorded as ADRs when they are made, and the project profile stays current as the system changes.
why?
history
check
observed
fix
remediation
next slice
Journey 2 · Modernisation
Reworking an existing codebase
Understand what exists, decide the target, then replace it one slice at a time.
You decide
Loops back
Journey 2 · Modernisation
Reworking an existing codebase
Understand what exists, decide the target, then replace it one slice at a time.
You decide Loops back
- 01ConfigureGround agents in the project. You confirm.
- 02Understand codebaseHow it actually works todaywhy? ⇄ historyRationaleWhy the system took its shape
- 03Assess architectureStructural problems, prioritisedcheck ⇄ observedInspect environmentWhat is really deployed
- 04Record decisionsTarget decisions you make, kept as ADRs
- 05DiscoveryThe rework mapped across sessions
- 06Refine workSlices you agree, ready to build
- 07Sequence workWhich slice can ship next
- 08PlanA technical plan for one slice
- 09ImplementTest-driven, old and new side by side
- 10ValidateEvidence against the acceptance criteria↺ fix: back to Implement
- 11ReviewIndependent judgement on the change↺ remediation: back to Implement
- 12You mergeOr ask for another cycle↺ next slice: back to Sequence work
Throughout: decisions are recorded as ADRs when they are made, and the project profile stays current as the system changes.
Prototype
Try an idea before committing
Try an idea before committing
Test-driven
Red, green, refactor
Red, green, refactor
Brainstorm
Round out the feature with you
Round out the feature with you
Refine work
Requirements and criteria you agree
Requirements and criteria you agree
Sequence work
Slices, dependencies, and what can wait
Slices, dependencies, and what can wait
Plan
Fits the existing design and conventions
Fits the existing design and conventions
Implement
One bounded change at a time
One bounded change at a time
Validate
New behaviour and regressions checked
New behaviour and regressions checked
Review
Independent judgement on the change
Independent judgement on the change
PR description
What a reviewer needs, nothing more
What a reviewer needs, nothing more
You merge
Or ask for another cycle
Or ask for another cycle
Evaluate session
Learn from how the work went
Learn from how the work went
Along the way: agents check how the product works and what the feature will touch, and report anything outside its scope instead of changing it.
try it
learn
test
green
intent changed
next item
fix
look back
Journey 3 · New feature
A major feature for an established product
A bounded idea is rounded out, refined, and delivered as reviewed changes.
You decide
Loops back
Journey 3 · New feature
A major feature for an established product
A bounded idea is rounded out, refined, and delivered as reviewed changes.
You decide Loops back
- 01BrainstormRound out the feature with youtry it ⇄ learnPrototypeTry an idea before committing
- 02Refine workRequirements and criteria you agree
- 03Sequence workSlices, dependencies, and what can wait
- 04PlanFits the existing design and conventions↺ intent changed: back to Refine work
- 05ImplementOne bounded change at a timetest ⇄ greenTest-drivenRed, green, refactor
- 06ValidateNew behaviour and regressions checked↺ fix: back to Implement
- 07ReviewIndependent judgement on the change
- 08PR descriptionWhat a reviewer needs, nothing more
- 09You mergeOr ask for another cycle↺ next item: back to Sequence work
- 10Evaluate sessionLearn from how the work went
Along the way: agents check how the product works and what the feature will touch, and report anything outside its scope instead of changing it.