Skill

DesignSpec

Write a formal design spec from brainstorming output or requirements. USE WHEN design approved, write spec, formalize design, spec document.

npx claudepluginhub n4m3z/forge-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Produce a formal design specification from approved brainstorming output or direct requirements. The spec is the contract between design and implementation — WritePlan and DeveloperSprint consume it.

Supporting Assets

SKILL.yaml

SKILL.md

Similar Skills

cache-components

139.4k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

pdf

131.6k

Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.

11 files

document-skills

Stats

Stars4

Forks2

Last CommitApr 16, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

DesignSpec

Gather input — read the approved design (from Brainstorming output or user description)
Write the spec — structured markdown covering all sections below
Self-review — run the checklist before presenting
Save — write to docs/specs/YYYY-MM-DD-<topic>-design.md
User review — present for approval. No implementation until approved.

Spec Structure

Scale sections to complexity. Simple specs skip sections that don't apply.

Problem Statement — what exists today, why it's insufficient
Proposed Approach — what we're building, key design decisions
API / Interface Design — public surface, data shapes, commands
Data Flow — how data moves through the system
Edge Cases — known boundary conditions and how they're handled
Test Strategy — what to test, how to verify correctness
Out of Scope — what this spec explicitly does NOT cover

Self-Review Checklist

Before presenting the spec, verify:

Check	Question
Completeness	Could someone implement this without asking questions?
Consistency	Do all sections agree with each other?
Clarity	Is every term unambiguous? No "should", "might", "maybe"?
Scope	Does this solve the stated problem without gold-plating?
YAGNI	Is every feature justified by a stated requirement?

Red Flags

Thought	Reality
"The design is clear enough, skip the spec"	If it's clear, the spec writes fast. If not, you need it more.
"I'll fill in the details during coding"	That's not a spec, it's a wish list.
"Edge cases can wait"	Edge cases found during coding cost 10x more to handle.
"The user already approved the design"	Design approval is not spec approval. Write it down.
"This spec is too short"	Short specs for simple problems are correct. Don't pad.

Constraints

Every section must be concrete — no placeholders, TBD, or TODO
Spec must be saved as a file, not just presented in conversation
User must approve the spec before implementation begins
Hand off to WritePlan or DeveloperSprint after approval