architecture-solution-strategy

Document core ideas and solution approaches for new systems.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/pkuppens/pkuppens --skill architecture-solution-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-solution-strategy
Source: https://github.com/pkuppens/pkuppens/tree/main/skills/architecture/architecture-solution-strategy
Command: npx skills add https://github.com/pkuppens/pkuppens --skill architecture-solution-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents the core ideas, fundamental decisions, and solution approaches for a new system.

Core Features & Use Cases

  • Capture goals, constraints, and context to align stakeholders (arc42 §1-§3).
  • Define core architectural ideas and the solution approach to guide subsequent blocks.
  • Reference ADRs when available to ensure traceability and coherence across architectural decisions.

Quick Start

Write a concise arc42 §4 style solution strategy and append it to docs/architecture/04-solution-strategy.md.

Frequently Asked Questions about architecture-solution-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a solution strategy for a new greenfield software architecture?

A solution strategy captures core architectural ideas, fundamental decisions, and solution approaches for a new system, guiding subsequent design blocks and ensuring stakeholder alignment across the project.

Can I consolidate existing ADRs into a single coherent architecture strategy?

Yes, you can consolidate existing ADRs into a coherent architecture strategy by referencing them within the solution strategy document, ensuring traceability and consistency across all architectural decisions in the generated arc42 §4 file.

What is the best way to structure an arc42 section 4 solution strategy document?

Structure an arc42 §4 solution strategy by documenting core architectural ideas and the solution approach concisely, then write the generated content to docs/architecture/04-solution-strategy.md to guide subsequent architecture blocks.

Do I need to capture context and constraints before writing a solution strategy?

Yes, capturing goals, constraints, and context from arc42 §1-§3 aligns stakeholders before defining the core architectural ideas and solution approach in the subsequent solution strategy document.

When should I write a solution strategy instead of just keeping individual ADRs?

Write a solution strategy during greenfield projects or when individual ADRs require consolidation into a coherent strategy, aligning stakeholders on fundamental approaches to guide broader architecture decisions.

What format and file path does the solution strategy document get written to?

The solution strategy document is written in arc42 §4 style format and saved to the file path docs/architecture/04-solution-strategy.md, providing a concise reference for the system's core strategy.