# Build a technology plan

Use this chain for every recommendation:

1. **Vocational goal** — the work outcome.
2. **Work tasks** — observable activities required by that goal.
3. **Functional barriers** — conditions that make a task inaccessible or unreliable.
4. **Required capabilities** — what the solution must do.
5. **Minimum configuration** — the least configuration that can perform the work safely and reliably.
6. **Preferred configuration** — capabilities that materially improve access, durability, or workflow.
7. **Alternatives** — lower-cost, borrowed, public-access, or differently configured paths.
8. **Current costs and quotes** — dated evidence kept outside the architecture.

Classify each requested capability as **essential**, **preferred**, or **optional**. Never make price or brand the reason for a requirement. Use the [technology-plan template](../templates/technology-plan.md) and verify current products and prices with the [technology-research prompt](../prompts/research-technology.md).