design

Generate structured design.md documents with components, interfaces, and decisions for a user story.

Updated Aug 27, 2026

Search Tags:#design #architecture #architecture-patterns #software-design #system-design #data-flow #component-design

Ready to run

npx skills add https://github.com/sofer/.agents --skill design-sofer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/sofer/.agents/tree/main/skills/design
Command: npx skills add https://github.com/sofer/.agents --skill design-sofer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan architecture and components for implementing a user story to produce design guides that enable stubs and implementation.

Core Features & Use Cases

Generates architecture patterns (Layered, Hexagonal, Clean, Event-driven) tailored to the story
Produces component definitions, interfaces, and data flows to guide development
Use Case: When starting a new story, generate a formal design document outlining controllers, services, repositories, and data contracts

Quick Start

Provide a complete design plan for the current user story.

Frequently Asked Questions about design

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

FAQPage Schema

How do I generate a software design document from a user story spec?▼

Software architecture planning for a user story generates a design.md file detailing components, interfaces, and data flows. It requires a clear spec frontmatter input to map out controllers, services, and repositories effectively.

Can I use Clean architecture or Hexagonal patterns for component design?▼

Yes, you can use Clean architecture or Hexagonal patterns for component design. The system supports multiple architecture patterns including Layered, Hexagonal, Clean, and Event-driven, tailoring the generated blueprint to the specific story requirements.

What is included in a generated system design blueprint for a new story?▼

A system design blueprint includes structured component definitions, interfaces, data flows, and architecture decisions. It maps out controllers, services, and repositories to provide a clear, scalable development guide.

Do I need to provide a complete spec before planning architecture and components?▼

Yes, providing a complete spec with clear frontmatter inputs is required before planning architecture and components. The system uses these structured inputs to generate the design document and define necessary software components.

When should I use an Event-driven architecture pattern over Layered design?▼

Use an Event-driven architecture pattern over Layered design when your user story requires asynchronous data flow and decoupled components. The system evaluates your spec to recommend the most suitable pattern for your requirements.