superpowers-sage:architecting

To define architecture for a Sage feature, you coordinate design-system validation, architecture discovery, and dependency-aware plan generation. This process establishes component boundaries and data-flow mapping while enforcing a hard no-implementation gate until you approve the architecture spec.

An ADR-oriented pre-implementation design workflow is a process that maps architecture decisions and dependency execution ordering before any coding begins. It generates a validated build plan and requires explicit user approval of the architecture spec to prevent misalignment and rework.

Yes, design tokens and a kitchensink route must exist before planning UI-heavy Sage features. The architecture workflow validates these design-system foundations exist as a prerequisite gate before proceeding with multi-block feature architecture discovery.

Dependency mapping in a Sage build plan works by analyzing component boundaries and data flows to determine execution ordering. The generated plan maps these dependencies and then hands off to execution-oriented skills for implementation after you approve the spec.

No, you cannot write implementation code during Sage architecture discovery because the workflow enforces a hard no-implementation gate. It requires explicit user approval of the produced architecture spec before transitioning to any execution-oriented build phase.

You should use an architecture planning skill for Acorn features when adding multi-block functionality that requires clear component boundaries and data-flow mapping. It prevents rework by validating design-system foundations and dependency ordering before you start coding.