design

Generate design documents specifying interfaces, file paths, and acceptance criteria.

7|4|Updated Mar 2, 2026

Search Tags:#design #architecture #documentation #interfaces #acceptance-criteria #code-structure

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces a precise design document that defines exact interfaces, file paths, and acceptance criteria for multi-file features, reducing ambiguity and rework during implementation.

Core Features & Use Cases

Precise interfaces, types, and signatures for features that span multiple files or modules.
Explicit file-structure plans and dependency resolution to guide implementers.
Acceptance criteria that are testable and unambiguous, with notes for non-obvious logic and edge cases.

Quick Start

Provide a project vision and existing code context to begin generating a detailed implementation blueprint.

Frequently Asked Questions about design

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

FAQPage Schema

How do I create a design document for a multi-file feature with exact interfaces and file paths?▼

A design document for complex features is needed when scope is unclear before coding or upfront decisions are too complex to inline. It resolves ambiguity by specifying exact file paths, types, and testable acceptance criteria for multi-file modules.

How do I define testable acceptance criteria for code structure and interfaces before implementation?▼

You define testable acceptance criteria by generating a precise design document that outlines unambiguous conditions, notes for non-obvious logic, and edge cases, ensuring clear validation standards before implementation begins.

Can I use this architecture documentation approach for features where scope is unclear before coding?▼

Yes, you can use this architecture documentation approach specifically when scope is unclear before coding or when a feature spans multiple files. It produces explicit file-structure plans and dependency resolution to guide implementers.

What's the best way to plan code structure and dependency resolution for multi-file modules?▼

The best way to plan code structure for multi-file modules is generating an implementation blueprint that defines explicit file-structure plans and dependency resolution, reducing ambiguity and rework during the actual coding phase.

When should I not use upfront design documents for software engineering tasks?▼

You should avoid upfront design documents for simple, single-file modifications where scope is already clear, as generating explicit file-structure plans and complete function signatures for trivial changes introduces unnecessary overhead.