specify

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill specify-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/specify
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill specify-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design work often fails in translation to engineering: specs lack rationale, copy is left as placeholders, edge cases go undocumented, and handoffs cause rework. This Skill turns finished design work into implementation-ready documentation that preserves design intent through production. ## Core Features & Use Cases - Screen-by-screen specifications: Documents layout, styling, interaction logic, states, accessibility requirements, and exact copy for every screen, each tied to the user need it serves. - Handoff packages and copy matrices: Produces structured engineering handoffs with ownership, problem context, rejected alternatives, asset inventories, and copy variant tables covering markets, edge cases, and A/B tests. - Test plans and ethical review: Writes audience-specific test plans with measurable success criteria and checks designs against an anti-pattern catalog before handoff. - Use Case: A designer finishing a checkout flow asks for the handoff package; the Skill produces a spec covering every state (loading, error, empty), a copy matrix with market variants, pending engineering questions, and instrumentation needs. ## Quick Start Ask the AI to write the engineering handoff spec for your finished checkout flow design, including all states, copy variants, and edge cases.

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 for all states, interaction logic, and accessibility requirements. Include ownership, problem context, rejected alternatives, and a test plan with measurable success criteria so engineers build without guessing.

What should a design handoff package include?

A complete handoff includes the design spec, organized and versioned design files, a copy matrix covering variants and edge cases, a test plan with success criteria, and explicitly flagged open questions separated into design-owned and engineering-owned items.

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, document what the user sees, what copy appears, and what happens on success and failure, including empty, loading, and error states.

Does this skill make design decisions or write code?

No. It documents and organizes existing design decisions for implementation but does not make design choices, write code, conduct user research, or provide engineering estimates. Those belong to designers, engineers, and research skills.

When should I not use a full specification document?

Not every handoff needs every section. Use only the sections that serve the project and audience; small changes may need just copy and state documentation, while new features warrant the full spec, test plan, and ethical review.