Guide

/guide recommends the smallest useful next move and stops. Read the relevant skill before making a consequential claim about its behavior. Both development workflows use project-owned documents, so switching between them preserves agreements and progress.

Choose the development workflow

Situation	Route
You want explicit planning and execution phases	Once per system, `/delineate → /architect`; then per capability, `/specify → /engineer → /taskify → /implement → /review-and-refactor`. Skip a step whose result already exists, and task decomposition when the selected work is small enough to implement directly.
You want to discover behavior while building a living application	`/iterate` clarifies, implements, and verifies one useful batch at a time.
You want to clarify a decision without starting development	`/interview`, the general interview discipline. The caller records useful results in the appropriate documents.

Planned development

Work is described on two levels, each from two sides. Functional comes before technical on each level; no step requires the one before it, but each reads what exists.