grace-planlisted

Run the GRACE architectural planning phase. > **Architecture handoff (Phase 2b):** use `docs/human/ARCHITECTURE-GUIDE.md` for the required > inputs, decisions, output fields and re-entry checklist. The user may choose any architecture > method, tool or reasoning surface; this skill owns the GRACE artifact formats. ## Prerequisites - `docs/requirements.xml` must exist and have at least one UseCase - `docs/technology.xml` must exist; stack decisions may be `pending` on entry - `docs/verification-plan.xml` should exist as the shared verification artifact template - If requirements or the technology template are missing, tell the user to run `/grace-init` first - If the verification plan template is missing, recreate it before finalizing the planning artifacts ## Architectural Principles When designing the architecture, apply these principles: ### Contract-First Design Every module gets a MODULE_CONTRACT before any code is written: - PURPOSE: one sentence, what it does - SCOPE: what operations are included - DEPENDS: list of module dependencies - LINKS: knowledge graph node references ### Module Taxonomy Classify each module as one of: - **ENTRY_POINT** — where execution begins (CLI, HTTP handler, event listener) - **CORE_LOGIC** — business rules and domain logic - **DATA_LAYER** — persistence, queries, caching - **UI_COMPONENT** — user interface elements - **UTILITY** — shared helpers, configuration, logging - **INTEGRATION** — external service adapters ### Semantic Ancho