architecture-discovery

Run a discovery pass that reads project context files, inspects existing repo conventions, compares practical options including keeping the current approach, and documents the recommendation in an Architecture Brief with risks and acceptance criteria.

Use discovery for new projects, major modules, stack selection, API or schema design, and risky refactors. Skip it for small bugfixes, doc-only edits, minor UI changes, or tasks that already have an approved implementation plan.

The brief covers the problem statement, existing system findings, research sources, options considered, recommended approach and stack, data and storage model, API contracts, security constraints, risks, acceptance criteria, and the next SDD Work Block.

No. The workflow is read-only and hard-stops on package installs, real credentials, production API calls, migrations, deploys, destructive git operations, and production code changes unless the owner explicitly approves.

The brief hands off to normal SDD planning, where Control Tower creates a scoped Work Block. The next step is task decomposition or the Plan and Discover stage of the SDD protocol.