specify

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

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/rakedzior/rootine --skill specify-rakedzior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/rakedzior/rootine/tree/main/agent/skills/specify
Command: npx skills add https://github.com/rakedzior/rootine --skill specify-rakedzior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design work often fails during implementation because intent, edge cases, and copy variations are never documented. This Skill turns finished design work into structured, implementation-ready specifications so engineering teams can build without guessing and stakeholders stay aligned. ## Core Features & Use Cases - Screen-by-screen specifications: Documents layout, styling, interaction logic, states, accessibility requirements, and exact copy for every screen. - Engineering handoff packages: Organizes ownership, problem context, design rationale, assets, and pending questions into a complete deliverable. - Copy matrices and edge cases: Captures primary copy, microcopy, market variants, A/B test variants, and failure scenarios in one place. - Test plans and measurement: Defines success criteria, counter-metrics, and instrumentation needs per audience. - Use Case: After finalizing a checkout flow in Figma, ask for a handoff package and receive a full spec with per-screen behavior, error-state copy, accessibility notes, ethical review, and a test plan ready for engineering. ## Quick Start Ask the assistant to write the engineering handoff spec for your current design, including screen specifications, copy matrix, edge cases, and 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, use cases, a copy matrix, 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 with naming conventions, a copy matrix covering variants and edge cases, a test plan with success criteria, and explicitly flagged open questions separated into 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 and 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.

When should I not use a full specification template?

Not every section is required for every handoff. Use only the sections that serve the project and audience; small changes may need only a screen spec and copy updates rather than a full package with presentations and test plans.