> ## Documentation Index
> Fetch the complete documentation index at: https://smithers.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# research-plan-implement

> Research, plan, implement, validate, and review in one run.

`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).

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
bunx smthrs workflow run research-plan-implement --prompt "Replace the auth cookie format"
```

<Frame caption="The research-plan-implement UI chains research and planning into the shared validation loop as one pipeline.">
  <img src="https://mintcdn.com/smithers/py7ertgBTLCgQQDl/images/workflow-ui/research-plan-implement.png?fit=max&auto=format&n=py7ertgBTLCgQQDl&q=85&s=ecc454571c8ad5003debe2abf9762ed6" alt="research-plan-implement workflow UI showing research, plan, and validation-loop stages in sequence" width="1280" height="832" data-path="images/workflow-ui/research-plan-implement.png" />
</Frame>

## Inputs

| Input    | Type    | Default                             |
| -------- | ------- | ----------------------------------- |
| `prompt` | string  | `"Implement the requested change."` |
| `tdd`    | boolean | `false`                             |

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:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
bunx smthrs workflow run research-plan-implement \
  --input '{"prompt":"Add invite-only signup","tdd":true}'
```

## How It Runs

1. Research gathers repo context, prior art, and implementation details.
2. Planning turns the request and research into concrete steps.
3. Implementation receives the original prompt plus research and plan context.
4. 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`](/workflows/implement).
* Only need context or a plan, not code: use [`research`](/workflows/research) or [`plan`](/workflows/plan).
* The scope spans many units or milestones: use [`tickets-create`](/workflows/tickets-create) with [`kanban`](/workflows/kanban), or [`mission`](/workflows/mission).

## Resume & retry

Runs are durable and resume with `up --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.