specify

Generates design specifications, engineering handoff packages, copy matrices, and test plans.

Updated May 5, 2026
One-click install
npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill specify-thegeekosaurus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/TheGeekosaurus/blogging-platform-2/tree/main/.agents/skills/specify
Command: npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill specify-thegeekosaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design work often loses intent when moving into engineering, causing rework and misalignment. This Skill turns existing design decisions into structured, implementation-ready documentation so engineers can build without guessing. ## Core Features & Use Cases - Screen-by-screen specifications: Document layout, styling, copy, interaction logic, states, and accessibility requirements for every screen. - Engineering handoff packages: Organize ownership, problem context, use cases, assets, and test criteria into a complete deliverable. - Copy matrices and edge cases: Capture primary copy, microcopy, market variants, A/B test variants, and edge cases like empty states and network failures. - Use Case: A designer finishes a checkout flow and needs it built. Use this Skill to produce a full spec with per-screen behavior, a copy matrix, an ethical review, and a test plan with measurable success criteria. ## Quick Start Ask the AI to write the engineering handoff spec for your completed design, including screen specifications, copy matrix, edge cases, and a test plan.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I write a design specification for engineering handoff?▼

Document each screen with its intent, layout and styling measurements, exact copy, interaction logic, accessibility requirements, and all states including error, loading, and empty. Pair the spec with ownership, problem context, use cases, and a test plan so engineers can implement without guessing.

What should a design handoff package include?▼

A complete handoff includes the design spec, design file links, a copy matrix covering all variants, a test plan with measurable success criteria, and organized assets with naming conventions. It should also flag pending design and engineering questions explicitly.

How do I document edge cases in a design spec?▼

Write specific scenarios rather than generic ones, such as network timeout during payment or a cart with 200+ items. For each case, document what the user sees, what copy appears, and what happens on success or failure.

Does this skill make design decisions or write code?▼

No. It documents existing design decisions and organizes them for implementation. It does not make design choices, write code, conduct user research, provide engineering estimates, or define success metrics from scratch.

How do I create a copy matrix for multiple markets?▼

List every copy element in a table with columns for primary copy, edge cases like character limits, market variants with tone and regulatory language, and A/B test variants. Include microcopy such as labels, hints, errors, and empty states.