system-design

Plan high-level architecture and component boundaries from reviewed requirements.

1|Updated Mar 17, 2026

Search Tags:#architecture #adr #system-design #architecture-decision #c4-model #component-boundaries

Ready to run

npx skills add https://github.com/yknothing/prodcraft --skill system-design-yknothing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: system-design
Source: https://github.com/yknothing/prodcraft/tree/main/skills/02-architecture/system-design
Command: npx skills add https://github.com/yknothing/prodcraft --skill system-design-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when reviewed requirements or specifications are ready and the team must decide high-level architecture, component boundaries, integration seams, or brownfield coexistence strategy before API design, technology selection, or task planning.

Core Features & Use Cases

Identify Architectural Drivers and rank quality attributes to shape the architecture.
Define component boundaries using a top-down C4 perspective (context, container, component) and document constraints for brownfield integration.
Create ADRs for significant decisions and outline trade-offs and fitness criteria to validate the design.
Use in brownfield, spec-driven, or agile workflows to ensure architecture is aligned with roadmap before implementation.

Quick Start

Review the provided requirements and spec documents, sketch the system context and container boundaries, and document the initial drivers and ADRs to begin architecture work.

Frequently Asked Questions about system-design

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

FAQPage Schema

How do I plan high-level architecture and define component boundaries from requirements?▼

To plan high-level architecture and define component boundaries, you sketch the system context and container boundaries from reviewed requirements, then document initial drivers and ADRs to begin architecture work.

What is the best way to document architecture decisions and trade-offs?▼

Documenting architecture decisions involves creating ADRs for significant choices, outlining trade-offs, and defining fitness criteria to validate the design against ranked quality attributes and architectural drivers.

How do I map component boundaries using the C4 model for system design?▼

Mapping component boundaries using the C4 model requires a top-down perspective spanning context, container, and component levels to structure the architecture and define clear integration seams before API design.

Can I use this architecture planning workflow for brownfield integration and coexistence?▼

Yes, this architecture planning workflow applies to brownfield coexistence by defining component boundaries and documenting integration constraints to ensure new components align with existing systems before technology selection.

When do I need to rank quality attributes and identify architectural drivers?▼

You need to rank quality attributes and identify architectural drivers when reviewed requirements or specifications are ready and the team must decide high-level architecture before proceeding to API design or task planning.