skills.rest
ishfuseini
ishfuseiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

specify

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

Updated Aug 20, 2026
Search Tags:#documentation#edge cases#design specification#ux#test plan#engineering handoff#copy matrix
One-click install
npx skills add https://github.com/ishfuseini/usecase-gen --skill specify-ishfuseini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/ishfuseini/usecase-gen/tree/main/agent/skills/specify
Command: npx skills add https://github.com/ishfuseini/usecase-gen --skill specify-ishfuseini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design work often fails to survive the transition to engineering because documentation is incomplete, ambiguous, or missing edge cases. This Skill converts design decisions into implementation-ready specifications, handoff packages, and test plans so engineers can build without guessing. ## Core Features & Use Cases - Screen-by-screen specifications: Documents layout, styling, interaction logic, copy, states, and accessibility requirements for every screen. - Engineering handoff packages: Organizes ownership, problem context, design rationale, assets, and pending questions into a structured deliverable. - Copy matrices and edge cases: Captures all copy variants, market adaptations, A/B test versions, and edge-case behavior in one place. - Use Case: A designer finishing a checkout flow asks for a handoff package; the Skill produces a full spec with per-screen intent, interaction logic, error states, a copy matrix, and a test plan with measurable success criteria. ## Quick Start Ask the assistant to write the engineering handoff spec for your current 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 values, exact copy, interaction logic, and all states including error, loading, and empty. Add ownership, problem context, pending questions, and a test plan so engineers can implement without guessing.

What should a design handoff package include?▼

A complete handoff includes the design spec, organized design files, a copy matrix covering variants and edge cases, a test plan with measurable success criteria, and explicit pending questions split between design and engineering ownership.

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

Write specific scenarios rather than generic ones, such as network timeout during payment or 200 items in a cart. For each, describe 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, or provide engineering estimates.

When should I not use a full specification document?▼

Skip sections that do not serve the project or audience; not every handoff needs all sections. For early exploration or unresolved design questions, flag open questions instead of documenting unsettled decisions as final.

Related Skills

Explore More Design & Creative Skills→
Productfculty-aipmProductfculty-aipm
70

problem-framing

Articulate ambiguous product hypotheses into testable problem statements.

Community
Intermediate
OM-bit-hubOM-bit-hub

metrics-define

Define feature measurement plans with goals, metrics, and instrumentation.

Community
Advanced
ghaidaghaida
116

evaluate

Evaluate UX issues and route findings to responsible Intent skills.

Community
Advanced
791994545791994545
4

prototype

Build disposable terminal apps or multi-variant UI prototypes for design testing.

Community
Intermediate