5d-spec

Included with Lifetime

$97 forever

Convert refined plan into technical specification with architectural decisions. Use when: (1) After REFINE phase in 5D-SDD workflow, (2) User is ready for technical design, (3) Moving from 'what' to 'how,' (4) User asks for 'technical spec,' 'architecture,' or 'design doc.' This phase bridges business intent and implementation detail.

Design

What this skill does


# SPEC Phase

Formalize the plan into technical specification.

## Spec Structure

### 1. Overview

One paragraph linking back to the plan. What is being built and why (from PLAN.md).

### 2. Architecture

Describe the technical approach:
- Components and their responsibilities
- Data flow between components
- External integrations
- Key technical decisions with rationale

Use diagrams where helpful (mermaid, ASCII, or description).

### 3. Data Model

Define data structures:
- Entities and relationships
- Key fields and types
- Validation rules
- Storage approach

### 4. Interface Contracts

For each boundary (API, UI, integration):
- Inputs (with types and constraints)
- Outputs (with types and error cases)
- Behavior specification

### 5. Domain Bridge (Width)

Explicitly connect technical decisions to business/user intent:

| Business Need | Technical Implementation |
|---------------|-------------------------|
| [need from plan] | [how spec addresses it] |

This prevents spec drift from plan intent.

### 6. Quadrant Coverage

Ensure spec addresses all perspectives:

| Quadrant | Spec Element |
|----------|--------------|
| Individual Outer | Components, interfaces, data structures |
| Individual Inner | Skills/knowledge required to implement |
| Collective Outer | System integrations, infrastructure |
| Collective Inner | Team alignment, review needs |

### 7. Skill Dependencies (Height)

Document implementation prerequisites:
- What capabilities must the team have?
- What domain expertise is required?
- What learning must happen before or during implementation?

### 8. Identity Trap Check

Flag where spec might be protecting assumptions rather than solving problems:
- Are any technical decisions "because we always do it this way"?
- What alternatives were dismissed too quickly?

### 9. Testability Criteria

For each spec item, define how correctness is verified:

| Spec Item | Verification Method |
|-----------|-------------------|
| [item] | [how we know it's right] |

If you can't define verification, the spec is too vague.

### 10. Transcend and Include (Time)

Document what existing code/patterns are being:
- **Kept:** [what stays unchanged]
- **Extended:** [what's being built upon]
- **Replaced:** [what's being deprecated]

## Output Format

Produce a standalone document titled `SPEC.md` with sections above.

Include enough detail that implementation is unambiguous, but no more.

## Exit Criteria

Proceed to GAP ANALYSIS when:
- Every plan item maps to spec item
- All interfaces are defined
- Verification criteria exist for each component
- User confirms spec matches intent

Files: 1

Size: 3.0 KB

Complexity: 13/100

Category: Design

Source: https://github.com/tapania/5d-skills/tree/main/skills/5d-spec

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts