research-plan-implement is an archived example, not installed by init. Copy it from examples/init-pack/ with its dependency closure, or ask create-workflow for one, then run it:
research-plan-implement is a full pipeline for changes that need context before code, using the same ValidationLoop as implement (see How It Runs).
The research-plan-implement UI chains research and planning into the shared validation loop as one pipeline.
Inputs
When
tdd is true, planning leads with test steps, and implementation writes or updates tests before production code.
Pass structured input for test-first planning:
How It Runs
- Research gathers repo context, prior art, and implementation details.
- Planning turns the request and research into concrete steps.
- Implementation receives the original prompt plus research and plan context.
- Validation and review decide whether another implementation pass is needed.
Use it when
- The change needs repo context and a plan before code, and you want research, planning, and validated implementation in one run.
Use something else when
- Already know what to build: use
implement. - Only need context or a plan, not code: use
researchorplan. - The scope spans many units or milestones: use
tickets-createwithkanban, ormission.
Resume & retry
Runs are durable and resume withup --resume; completed research and planning aren’t re-run. Implementation uses the same validation loop as implement: up to 3 iterations, stopping on validation pass plus synthesized review verdict approval.