design-signal

Declares 30/60/90% design confidence checkpoints backed by evidence to gate PRD stage progression.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill design-signal-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-signal
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/2-discovery/design-signal
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill design-signal-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design risk often closes after the PRD instead of alongside it, so teams discover usability problems late when rework is expensive. This Skill runs structured 30/60/90% Design Signal checkpoints that declare design confidence based on evidence, keeping the design lane synchronized with PRD Forming, Storming, and Norming stages. ## Core Features & Use Cases - Three staged checkpoints: 30% (conceptual flows plus named UX risks), 60% (testable prototype with usability findings and risk closure plans), and 90% (dev-ready design with state coverage, edge cases, and accepted residual risks). - Evidence-based signal declaration: a standard report template with evidence tables, risk registers, and go/hold recommendations, where the declared percentage must come from evidence rather than the calendar. - Use Case: Before PI Planning, run the 90% checkpoint to sweep every screen for empty/error/loading states, have an engineer walk the handoff for unanswered questions, and produce a dev-ready design report that gates delivery commitment. ## Quick Start Run a 60% design signal checkpoint for the checkout redesign feature and produce the report with evidence and go/hold recommendation.

Frequently Asked Questions about design-signal

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

FAQPage Schema
How do I run a design readiness checkpoint before PI Planning?▼

Run the 90% Design Signal checkpoint: sweep every screen for empty, error, and loading states, have an engineer walk the handoff listing open questions, and formally accept remaining risks. The output is a dev-ready design report with a go/hold recommendation.

What is the difference between 30%, 60%, and 90% design confidence?▼

30% means conceptual flows exist for the primary journey with named UX risks. 60% means a testable prototype survived usability sessions with closure plans for major risks. 90% means engineering can build without design guesses, with residual risks explicitly accepted.

Does the 60% design gate require real user testing?▼

Yes, the 60% gate requires observed user behavior, not internal review. When real users are hard to reach, proxy users via discovery-interview-prep or a disposable pol-probe validation probe are acceptable substitutes.

When should I not use design-signal checkpoints?▼

Do not use it for building UI, which belongs to cleanui, or for writing the PRD, which belongs to prd-development. It also requires a forming PRD to pace against, so it does not apply before PRD work begins.

Why would a declared design signal regress from 60% to 30%?▼

Signals regress when new evidence invalidates earlier confidence, such as usability sessions showing users stumbling on the core model. A documented drop is risk closure working correctly, not a failure of the process.