specify

Convert design work into engineering-ready specification documents with test criteria.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/snuffomega/pricechart --skill specify-snuffomega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/snuffomega/pricechart/tree/main/.agents/skills/specify
Command: npx skills add https://github.com/snuffomega/pricechart --skill specify-snuffomega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents rework and misalignment by translating design intent into implementation-ready documentation that engineers and cross-functional stakeholders can follow without guessing.

Core Features & Use Cases

  • Detailed, implementation-ready specifications: Produce screen-by-screen and state-by-state specs that document visuals, interaction logic, constraints, and accessibility requirements.
  • Organized engineering handoff packages: Bundle specs with ownership/context, asset inventories, and clear rationale so engineering knows what to build and why.
  • Copy, variants, and edge-case coverage: Create copy matrices and document behaviors for default, loading, empty, error, and success states, including market and edge variations.
  • Test plans tied to measurable success: Define what to test for each audience and how success is measured, aligned to an external measurement framework.
  • Stakeholder-ready presentations and open-question tracking: Summarize decisions, what was not done, and explicitly flag design and engineering questions that remain.

Quick Start

Use the specify skill to produce a complete engineering handoff spec for a feature you are designing, including UX states, exact copy, accessibility notes, 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 create engineering handoff specs from design intent?

To create engineering handoff specs, translate design intent into structured documents detailing screen-by-screen visuals, interaction logic, accessibility requirements, and state behaviors so developers know exactly what to build.

What is a UX copy matrix and how is it used in design documentation?

A UX copy matrix is a structured document mapping exact interface text across default, loading, empty, error, and success states. It ensures engineering handoff covers all edge-case variations and market-specific copy requirements.

How do I document edge-case states for UI design handoff?

Document edge-case states by specifying behaviors for loading, empty, error, and success scenarios within your UX specs. This ensures engineering handoff packages cover all interaction logic and accessibility constraints for every state.

What is the best way to align stakeholders during a design handoff?

Align stakeholders by generating handoff packages that summarize design decisions, explicitly flag pending questions, and outline what was excluded. This provides clear rationale and tracks open design and engineering questions.

Can I include test plans and success criteria in UX specs?

Yes, you can include test plans in UX specs by defining what to test for each audience and how success is measured. This ties implementation-ready instructions directly to an external measurement framework.

Do I need specific design tools to generate implementation-ready documentation?

No specific design tools are required to generate implementation-ready documentation. The process relies on YAML-frontmatter grounding to produce structured screen behaviors, asset inventories, and accessibility notes regardless of your platform.