Plan guide
What are plans and workflows?
Plans turn an approved direction into ordered work. Workflows capture procedures the team expects to repeat. Together, they make implementation easier to review and verify.
Plans versus workflows
Plan
A plan is tied to a specific piece of work. It names steps, acceptance criteria, verification, and current status.
Workflow
A workflow is a repeatable operating procedure. It explains how to do a kind of work again without reinventing the process.
Why Amistio chose plans
Implementation prompts are safer when the sequence is visible first. Plans give humans a place to review what will happen, what counts as done, and which checks matter. They also give the local runner a narrower task surface.
A plan is not bureaucracy for its own sake. It is the handrail between intent and execution, especially when a tool can edit many files quickly.
What good plans include
- A goal that describes the user-visible or system-visible outcome.
- A short list of ordered steps, each with a clear purpose.
- Acceptance criteria that a reviewer can check.
- Verification commands or smoke checks.
- Notes for blockers, skipped checks, and final results.
Where workflows fit
Workflows are useful when the same shape of work repeats: release checks, onboarding a repository, importing legacy docs, or responding to runner issues. In Amistio, workflows keep operational knowledge out of one person's head and inside the project brain.