Digital Solution Designer

Problem

Government and enterprise digitalization projects often start with a vague request: design a platform, plan a business scenario, or evaluate a system upgrade. Without a clear solution type, planning, project proposals, feasibility studies, and bid documents can easily mix together, while architecture, budgeting, and implementation plans drift apart. This skill turns such requests into structured digital solution design documents.

How it works

• Identify the solution type first: planning, project proposal, feasibility study, bidding, or progress report; the source requires waiting for user confirmation instead of inferring from keywords.
• Collect key constraints: domain, budget, timeline, existing systems, core problems, then draft an outline before expanding sections.
• Expand by stage: policy context, requirements analysis, design approach, four-dimensional architecture, technology selection, build scope, implementation plan, risk assessment, benefit analysis, and investment estimation.
• Architecture visualization: can use generate-architecture-diagram.py to produce business, functional, data, and technical diagrams.
• Quality review: run a type-specific checklist and validate consistency across business, functional, data, and technical architecture.

Boundaries

• Useful for digital government, enterprise systems, project proposals, feasibility studies, and bid documents.
• Not a substitute for contract commitments, final budget audit, or official compliance sign-off; verify pricing, staffing qualifications, and regulatory details manually.
• Government work should consider classified protection, Xinchuang, data security, and procurement rules; enterprise work should consider ROI, technology stack fit, and operations scope.