Detailed Prototypes

Use when a human-approved design system exists and the in-scope screens need high-fidelity prototypes: one prototype per screen, each tracing to a functional requirement, user story, or acceptance criterion, with mock/API-gap annotations for anything designed ahead of its backend contract. This is the detailed_prototypes action of the design stretch — one Agent-tool dispatch with subagent_type ui-ux-developer — UI-bearing targets only, and it hard-requires the recorded human approval visual-design stopped for.

BhangeeF16 c390724 1.6 KB Updated

File contents

Detailed Prototypes

Produce high-fidelity prototypes for the approved design system. The precondition is not that visual-design passed — it is that a human approved its output.

Dispatch

One synchronous Agent-tool call, subagent_type: ui-ux-developer. Do not dispatch this action at all while visual-design's manual approval is missing — dispatching it anyway is a process defect, not initiative.

Required inputs

  • The human-approved design-system.md from visual-design.
  • The target's functional-requirement catalog.
  • Relevant user-story documents for in-scope actors.
  • Relevant business rules referenced by in-scope screens.

Required outputs (all mandatory)

  • High-fidelity prototypes per in-scope screen, each tracing to a functional requirement, user story, or acceptance criterion.
  • Mock/API-gap annotations for any screen designed ahead of its backend contract.

Result

Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).

BhangeeF16/kaizen/tree/main/skills/detailed-prototypes commit c39072460c

Frequently asked questions

npx skillmds@latest add bhangeef16/detailed-prototypes