dev-design

Generate design specifications from investigation results and setup.yaml.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineering teams convert research findings and investigation outputs into concrete software design artefacts, streamlining the handoff from discovery to implementation.

Core Features & Use Cases

  • Input-driven design: reads setup.yaml, design-document, and dev-investigation to produce detailed design artifacts.
  • Output generation: creates docs/{target_repo}/dev-design/ and updates the design-document with architecture, interfaces, and data structures.
  • Reuse through SSOT: references the description.requirements as design constraints.

Quick Start

Follow the instruction to trigger design generation using the project’s investigation results and setup yaml.

Frequently Asked Questions about dev-design

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

FAQPage Schema
How do I convert dev-investigation results into a software design document?

You generate a design document by feeding dev-investigation results and setup.yaml into this skill, which then outputs architecture, interfaces, and data structure specifications under the target repository's docs directory.

What is the SSOT rule for system design and architecture?

The SSOT rule enforces description.requirements as the single source of truth for deriving architecture, interfaces, data structures, and process flows within the generated design specification.

How to generate API design and data structure specifications from research findings?

Generate API design and data structure specifications by passing research findings through the dev-design skill, which updates the design-document with concrete interface definitions and structural layouts based on established requirements.

Do I need a setup.yaml file to generate architecture and interface design artifacts?

Yes, you need a setup.yaml file along with a design-document and dev-investigation inputs, because the skill reads these specific files to produce the target repository's design specification and update the existing documentation.

Where does the generated design specification output get saved in the repository?

The generated design specification output gets saved under the docs/{target_repo}/dev-design/ directory path, and the skill simultaneously updates the main design-document with the newly created architecture and interface sections.

What are the limitations of using automated design generation from investigation outputs?

A limitation of automated design generation is that the output quality strictly depends on the input dev-investigation results and description.requirements, meaning incomplete research inputs will yield inadequate architecture and data structure design artifacts.