design

Guide architecture design decisions for software projects.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/NagasakaH/dev-process --skill design-nagasakah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/NagasakaH/dev-process/tree/main/.claude/skills/general-purpose/design
Command: npx skills add https://github.com/NagasakaH/dev-process --skill design-nagasakah

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architecture design often lacks structured guidance, causing inconsistent decisions and brittle systems. This Skill provides a repeatable design process that aligns requirements, interfaces, data models, and test strategies.

Core Features & Use Cases

  • Design governance: defines implementation direction, interfaces, data structures, and tests.
  • Use-case alignment: ensures architecture decisions match requirements and constraints.
  • Collaborative design: supports investigation reports and design documents to align teams.

Quick Start

Generate a complete architecture design document after the investigation phase.

Frequently Asked Questions about design

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

FAQPage Schema
How do I guide architecture design decisions from investigation to documentation?

Guide architecture design by applying a structured investigation-to-design workflow that synthesizes research, selects patterns, designs interfaces, models data, defines processing flows, and documents test strategies. This ensures requirement-driven architecture decisions are consistent and aligned across teams.

What is the best way to structure requirement-driven architecture design for a software project?

Requirement-driven architecture design is structured by defining implementation direction, interfaces, data structures, and test strategies. This approach aligns architecture decisions with project requirements and constraints, preventing brittle systems and ensuring consistent design governance.

Can I use this approach to generate a complete architecture design document after the investigation phase?

Yes, you can generate a complete architecture design document after the investigation phase. The workflow supports collaborative design by transforming research synthesis into formal documentation covering interface design, data modeling, processing flows, and test strategy.

How does data modeling and API design fit into the system design workflow?

Data modeling and API design are explicit steps within the system design workflow. They follow research synthesis and architecture pattern selection, ensuring that data structures and interfaces match the defined requirements and processing flows before test strategy documentation.

Why does software architecture design often lack structured guidance and produce brittle systems?

Software architecture design often produces brittle systems because it lacks a repeatable design process that aligns requirements, interfaces, data models, and test strategies. Without structured guidance from investigation to documentation, teams make inconsistent design decisions that fail to match constraints.

Do I need an investigation report before starting the system design process?

Yes, an investigation report is needed before starting system design. The workflow applies to investigation-to-design processes, using research synthesis to drive architecture pattern selection, interface design, data modeling, processing flows, and test strategy documentation.