software-design-lifecycle-tech-detailed-methodology

# Technical Detailed Methodology ## Overview This is the `architect` profile's **技术方案设计 → 详细设计 方法论 skill**. It is the second half of technical design and should only start on top of a stable overview design. The detailed-design stage is now intentionally kept **leaner**: - keep separate specialist companion skills only for the two highest-value recurring artifact classes - 技术架构图 - 关键流程图 / 状态机 - keep the other detailed-design surfaces inside this methodology skill as part of one integrated detailed-design packet That keeps the live skill family clearer and avoids over-splitting the stage into too many tiny children. ## When to Use Use when: - solution design and overview design have already been reviewed - the architect must define concrete technical realization surfaces for implementation - the task is about 技术架构、项目架构、关键流程、数据结构、接口、非功能需求、安全、备份恢复、风险、硬件、实施计划 ## Canonical Stage Doctrine (Full Preservation) | 详细设计 | 技术架构 | 系统设计中的功能通过什么技术栈实现？如何选型的？项目结构是什么样的？ <br>系统运行起来后，服务、进程、任务、调用链路如何协作，稳定性如何保障？<br><br>_依赖与组件等实现方式，基于需求调研中得到的业务解决方案，合理利用技术栈、工具链、中间件的组合、以实施落地为目的对该业务方案进技术细化_<br> | 技术架构图，示例如下： <br> | | | 项目架构 | 代码、模块、组件、依赖如何组织，如何保证可维护性与可扩展性？<br><br>*项目结构、模块分层、组件依赖、技术选型说明* | 项目架构图 ...