ReadyHandoff

Design done means client ready.

An Agent Skill that audits, packages, cold-tests, and delivers complete client-facing design handoffs.

Most handoff tools stop at measurements or a shared link. ReadyHandoff creates the durable package a client can understand and use after the project is over: complete flows, final screens, annotations, brand assets, design-system context, prototype access, implementation guidance, accessibility and QA evidence, and licensing.

It refuses to call the work complete until the package passes an audit. The portable packager then extracts the ZIP into a clean temporary directory and audits the received archive again.

Quick start

Requirements: Node.js 18+ and Python 3.10+.

npx skills add demobdev/readyhandoff@ready-handoff -g -y

Then ask your agent:

Use $ready-handoff to package this responsive web and mobile redesign for my client.
Include onboarding, billing, and settings flows, annotated screens, the logo kit,
prototype access, accessibility evidence, and implementation notes.

New to Agent Skills? You can also copy skills/ready-handoff into the skills directory supported by your coding agent.

What the client receives

client-delivery/
  client-project-design-handoff/
    00-START-HERE/       package guide, manifest, delivery scope
    01-DIRECTION/        brief, chosen direction, decision history
    02-BRAND/            logos, colors, typography, usage
    03-FLOWS/            ordered journeys and important states
    04-SCREENS/          clean web, iOS, and Android exports
    05-ANNOTATED/        numbered callouts plus written explanations
    06-SYSTEM/           tokens, components, variants, states
    07-ASSETS/           implementation-ready media
    08-PROTOTYPE/        links, access, walkthroughs, fallback
    09-IMPLEMENTATION/   behavior, content, accessibility, QA
    10-LICENSES/         rights, sources, attribution

Internal research, competitor screenshots, rejected explorations, credentials, private data, and unlicensed assets are explicitly excluded.

How it works

1. Scaffold early once scope and design direction are stable.
2. Build continuously as flows, screens, assets, and decisions become final.
3. Declare evidence for every contracted platform, viewport, flow, state, accessibility target, and QA target.
4. Audit required files, placeholders, unsafe filenames, screenshots, annotations, brand formats, and client-safety rules.
5. Package and cold-test by extracting the ZIP and auditing what the client will actually receive.

node skills/ready-handoff/scripts/scaffold.mjs \
  --project . \
  --client "Northstar Labs" \
  --name "Product Redesign" \
  --platform both \
  --brand

node skills/ready-handoff/scripts/audit.mjs \
  --pack client-delivery/northstar-labs-product-redesign-design-handoff

python skills/ready-handoff/scripts/package.py \
  --pack client-delivery/northstar-labs-product-redesign-design-handoff

PowerShell packaging is also included for Windows.

Designed for real work

• Responsive websites and web applications
• Native iOS and Android products
• SaaS and internal software
• Brand identities and logo systems
• Figma, Penpot, Sketch, Framer, coded prototypes, or exported-image workflows
• Freelancers, studios, agencies, product designers, and design engineers

ReadyHandoff is intentionally tool-agnostic and has no telemetry.

Help shape it

The fastest ways to help are:

• Try it on a real, safely redacted project
• Report where the audit is too weak or too strict
• Share an anonymized package tree or missing-deliverable story
• Improve Windows, macOS, or Linux compatibility
• Propose adapters for the design tools you actually use

Start with CONTRIBUTING.md. Beginner-friendly issues will be labeled good first issue and should include a reproduction, expected outcome, and a suggested starting point.

Project status

ReadyHandoff is in Phase One: prove the open delivery contract with real designers. See the measurable roadmap and Phase Two gate.

License

MIT. Contributions are licensed under the same terms. See LICENSE.