delivery-handoff

Generate Storybook handoff pages with UI flow diagrams, component inventories, and per-screen specs.

5|9|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ajenchen/design-system --skill delivery-handoff-ajenchen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delivery-handoff
Source: https://github.com/ajenchen/design-system/tree/main/.agents/skills/delivery-handoff
Command: npx skills add https://github.com/ajenchen/design-system --skill delivery-handoff-ajenchen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a product feature is confirmed final, teams lack a single inspectable delivery package for engineering, PM, QA, and design stakeholders. This Skill produces a Figma-like handoff package so every audience gets component usage, token consumption, UI flows, and per-screen specs without manual documentation work. ## Core Features & Use Cases - Deterministic Inventory Generation: Scans feature code to produce component usage tables, design token consumption reports, layout primitive counts, and an accessibility checklist using grep-based mechanical counting. - Mermaid UI Flow Diagrams: Auto-generates flowcharts from routes, click handlers, and navigation logic, including error paths and edge cases, renderable directly in Storybook. - Per-Screen Spec Sheets and Storybook Handoff Page: Creates a five-tab Features/{Feature}/Handoff Storybook page with overview, UI flow, inventory, screen previews, and detailed spec sheets covering states, interactions, a11y, and business rules. - Use Case: After a checkout feature passes audit and stakeholders confirm it is final, invoke the Skill to deliver a complete handoff package that engineering uses for implementation reference and QA uses for edge-case test planning. ## Quick Start Run /delivery-handoff for the checkout feature and generate the Storybook handoff package for the engineering team.

Frequently Asked Questions about delivery-handoff

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

FAQPage Schema
How do I generate design handoff documentation for a finished feature?

Invoke the delivery-handoff workflow after the feature is confirmed final and audit issues are resolved. It scans the feature code to build component and token inventories, generates a Mermaid UI flow diagram, and assembles a Storybook Handoff page with per-screen spec sheets.

What does a Storybook handoff page include?

The handoff page contains five tabs: an Overview with audience and status, a Mermaid UI flow diagram, an Inventory of components, tokens, and a11y results, a Screens grid with previews and links, and per-screen Spec Sheets covering states, interactions, edge cases, and business rules.

When should I not run the delivery handoff workflow?

Do not run it during prototype exploration or audit phases, since those stages have their own workflows. It is only for features confirmed final by stakeholders, ideally with zero P0 audit findings and code merged or ready to merge to the main branch.

How are component and token inventories generated?

Inventories are generated deterministically with grep-based scans of imports, JSX usage, CSS variable references, and utility classes, then counted and sorted into tables. This avoids relying on memory and catches hidden consumption such as components used inside internal functions.

Can the accessibility checklist fully replace manual a11y review?

No. Automated scans only catch visible issues like missing aria-labels, onClick on non-button elements, or Dialogs without titles. Color contrast, keyboard navigation, and screen reader behavior still require manual testing with tools like axe, VoiceOver, or NVDA.