software-design-lifecycle-delivery

# Architect Lifecycle Delivery ## Overview This is the `architect` profile's **lifecycle backbone and routing skill**. It now belongs entirely to the new `arch-lifecycle-*` system. Its role is not to duplicate each stage methodology skill, but to: - decide the correct lifecycle entry point - keep stage boundaries clear - preserve the integrated delivery-chain doctrine that gives the whole family coherence Core principle: **architecture is a staged reduction of uncertainty, not one giant diagram and not a late cleanup after coding starts.** ## When to Use Use when: - the user asks for 架构方案、设计方案、概要设计、详细设计、技术方案、设计交付包, but the current stage is not yet explicit - the architect must take work from 0 or from a midstream stage and choose the correct entry point - the team is mixing business framing, solution design, overview design, detailed design, and deploy/ops handoff responsibilities together - the architect needs one top-level delivery chain to coordinate survey, diagrams, risk, and handoff Do not use when: - the current stage is already explicit and the correct methodology skill can be loaded directly - the main question is a cross-stage specialist judgment such as DDD boundary modeling or code-structure refactoring rather than lifecycle routing ## Lifecycle Family Map Primary methodology skills: - `arch-lifecycle-demand-survey-methodology` - `arch-lifecycle-solution-design-methodology` - `arch-lifecycle-tech-overview-methodology` - `arch-lifecycle-tech-detailed-metho...