solution-design
Guides the Solutions Architect through converting business requirements into a full technical solution design. Covers requirements decomposition, architecture option comparison, trade-off analysis, and implementation roadmap with explicit dependency mapping and risk levels. Mandatory output includes dependency map and risk register for handoff to delivery-manager.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- solution-design
- owner
- solutions-architect
- scope
- co-consult
- status
- active
- version
- 1.0.0
- metadata
- { "type": "process", "triggers": [ "solution design", "technical design", "solution architecture", "architecture options", "implementation roadmap", "requirements decomposition" ] }
- relates_to
- [ { "type": "follows", "skill": "financial-modeling" }, { "type": "composes_with", "skill": "stakeholder-alignment" }, { "type": "follows", "skill": "technical-feasibility" } ]
- description
- Guides the Solutions Architect through converting business requirements into a full technical solution design. Covers requirements decomposition, architecture option comparison, trade-off analysis, and implementation roadmap with explicit dependency mapping and risk levels. Mandatory output includes dependency map and risk register for handoff to delivery-manager.
- last_reviewed
- 1781308800000
- prerequisites
- none
03 SKILL.md 正文
Context
Use in Phase 3 after Phase 2 approval. The implementation roadmap produced here must include dependency mapping and risk levels to enable Delivery Manager to build the execution plan directly.
When to Use
Invoke this skill when Phase 2 has been approved and the Solutions Architect is ready to translate business requirements into a concrete technical design and implementation roadmap.
Execution Steps
- Requirements Decomposition:
- Functional requirements (what the solution must do)
- Non-functional requirements (performance, scalability, security, compliance)
- Constraints (budget, timeline, existing technology stack, organizational capabilities)
- Architecture Options: Define 2-3 viable technical approaches. For each:
- High-level architecture description
- Technology stack / components
- Integration points with existing systems
- Pros and cons
- Trade-off Analysis: Compare options on: cost, complexity, time-to-value, risk, maintainability, vendor dependency
- Recommended Architecture: Select and justify the recommended option
- Implementation Roadmap:
- Phase-by-phase breakdown (each phase: objective, deliverables, duration estimate)
- Dependency Map (mandatory for Delivery Manager):
- List all task dependencies (what must be complete before each phase starts)
- External dependencies (vendor contracts, data availability, regulatory approval)
- Risk Register (mandatory for Delivery Manager):
- Risk, probability (H/M/L), impact (H/M/L), risk level, mitigation action, owner
- Handoff Package: Structured output ready for Delivery Manager to convert to execution plan
Output Format
- Architecture Decision Record (ADR): Context, Options Considered, Decision, Consequences
- Implementation Roadmap: Phase, Objective, Deliverables, Duration, Dependencies, Owner
- Dependency Map (table or diagram)
- Risk Register: Risk, Probability, Impact, Level, Mitigation, Owner
Related Skills
- technical-feasibility
- project-delivery
- narrative-framework
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.