design

Generate design documents from feature board specifications and codebase exploration.

Updated Mar 20, 2026

Search Tags:#code analysis #software design #development automation #design documentation #project specifications

Ready to run

npx skills add https://github.com/KevounC/claude-kanban --skill design-kevounc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/KevounC/claude-kanban/tree/main/.claude/skills/design
Command: npx skills add https://github.com/KevounC/claude-kanban --skill design-kevounc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of detailed design documents for software implementations, significantly reducing the ambiguity in specifications and ensuring clear guidance for developers.

Core Features & Use Cases

Automated Design Documentation: Generates design documents from feature board specifications, exploring codebases and relevant research.
Codebase Exploration: Utilizes parallel agents to map code structures, interface types, and test patterns.
Implementation Order and Dependencies: Determines the order of implementation units and manages dependencies for smooth development.

Quick Start

Use the design skill on the feature board 'my-feature' to generate a design document for the 'Auth Overhaul' feature.

Frequently Asked Questions about design

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

FAQPage Schema

How do I generate design documents from feature board specifications?▼

You can generate design documents by analyzing feature board specifications, exploring the project codebase, and incorporating project-specific guidelines to produce structured implementation specifications. The process maps code structures and interface types to reduce ambiguity.

How does code analysis map project dependencies for software design?▼

Code analysis for software design maps project dependencies by utilizing parallel agents to explore the codebase, identifying code structures, interface types, and test patterns. This determines the implementation order of units and manages dependencies for smooth development.

What's the best way to automate development documentation for a software pipeline?▼

Automating development documentation is best achieved by analyzing feature specifications and exploring the codebase to produce structured design specifications. This approach ensures clear guidance for developers by incorporating project-specific patterns and architecture.

Does automated design documentation work with existing project architecture?▼

Automated design documentation works with existing project architecture by requiring an understanding of the project structure, dependencies, and user-provided context. It explores the codebase to incorporate project-specific guidelines and patterns into the final specifications.

When do I need structured design specifications for a software implementation?▼

You need structured design specifications when a software development pipeline requires clear guidance for developers and reduced ambiguity in feature implementation. It is essential when mapping implementation order and managing dependencies across complex project architectures.

Can I determine implementation order and dependencies from codebase exploration?▼

You can determine implementation order and dependencies by exploring the codebase to map code structures and interface types. The design process analyzes these patterns alongside feature specifications to manage dependencies and sequence implementation units smoothly.