design-doc

Draft structured design documents with goals, constraints, decisions, and acceptance criteria.

27|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/maragudk/fabrik --skill design-doc-maragudk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-doc
Source: https://github.com/maragudk/fabrik/tree/main/skills/design-doc
Command: npx skills add https://github.com/maragudk/fabrik --skill design-doc-maragudk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams produce precise design documents and specifications after brainstorming or feature design sessions, ensuring alignment and documentation for future work.

Core Features & Use Cases

  • Rapid drafting of design docs from brainstorm outputs.
  • Clear structure guidelines and best practices for design specs.
  • Use Case: after a design session, generate a concise document that captures decisions, rationale, and acceptance criteria.

Quick Start

Draft a concise design doc outlining goals, constraints, and acceptance criteria for the new feature.

Frequently Asked Questions about design-doc

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

FAQPage Schema
How do I create a design document after a brainstorming session?

To create a design document after brainstorming, draft a structured specification that captures goals, constraints, decisions, rationale, and acceptance criteria to ensure team alignment for future implementation.

What should be included in a feature specification for system architecture?

A feature specification for system architecture should include goals, constraints, decisions, and acceptance criteria. This documentation ensures alignment across product design, system architecture, and feature scoping tasks.

Can I use markdown and YAML frontmatter for design documentation?

Yes, you can use markdown and YAML frontmatter for design documentation. The skill uses YAML frontmatter for metadata like name and description, and the Markdown body provides actionable guidance for implementation and collaboration.

What is the best way to structure design specs for handoffs and reviews?

The best way to structure design specs for handoffs and reviews is to apply clear structure guidelines and best practices. Draft concise documents outlining goals, constraints, and acceptance criteria for the new feature.

Does this approach work for both product design and feature scoping tasks?

Yes, this approach works for both product design and feature scoping tasks. It applies across ideation, reviews, and handoffs to help teams produce precise design documents and specifications after brainstorming sessions.