specify

Generate implementation-ready design specifications and handoff packages in HTML or Markdown.

116|9|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ghaida/intent --skill specify-ghaida
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/ghaida/intent/tree/main/skills/specify
Command: npx skills add https://github.com/ghaida/intent --skill specify-ghaida

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bridges design and engineering by producing detailed specs, organized handoff packages, asset inventories, and cross-functional documentation that preserves design intent through to production.

Core Features & Use Cases

  • Detailed, screen-by-screen specifications including visuals, interaction logic, and exact copy
  • Organized handoff packages with ownership, problem context, constraints, use cases, assets, and test criteria
  • Copy matrices and variant documentation covering markets, edge cases, and accessibility considerations
  • References to design system tokens and component constraints to guide implementation
  • Support for stakeholder presentations and measurement-aligned documentation

Quick Start

Generate a complete design specification package ready for engineering from the current design artifacts.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I create implementation-ready design specifications for engineering handoff?

Implementation-ready design specifications are generated by automating detailed, screen-by-screen specs with interaction logic, exact copy, and organized asset inventories to bridge design work directly to engineering.

What should be included in a design handoff package for developers?

A design handoff package should include problem context, ownership, constraints, use cases, asset inventories, test criteria, and references to design system tokens to guide implementation accurately.

How do I document edge cases and accessibility variants for design systems?

Edge cases and accessibility variants are documented using copy matrices and variant documentation that cover different markets, constraints, and specific accessibility considerations for engineering implementation.

Can I generate living design specs in HTML or Markdown for version control?

Living design specs can be produced in HTML or Markdown formats, enabling versioned decisions, organized references, and direct links to measurement plans for continuous validation.

Does the design specification process support stakeholder presentations and measurement plans?

The design specification process supports stakeholder presentations by aligning documentation with measurement plans, ensuring that design intent and validation criteria are clearly communicated across cross-functional teams.

What is the best way to preserve design intent through to production?

Preserving design intent through to production is achieved by producing detailed specs, organized handoff packages, and cross-functional documentation that explicitly link design system tokens and component constraints to implementation.