design-gate-orchestration

Coordinates Gate 3 UX+Design orchestration enforcing local-only execution and checkpointing until Design QA closure.

Updated Jan 30, 2019
One-click install
npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill design-gate-orchestration
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-gate-orchestration
Source: https://github.com/nishantnaagnihotri/tark-vitark/tree/main/.github/skills/design-gate-orchestration
Command: npx skills add https://github.com/nishantnaagnihotri/tark-vitark --skill design-gate-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design gate orchestration workflow: coordinates Gate 3 UX+Design single-pass and Design QA substeps, enforces local-only execution and validation checks, runs revision loops, and requires Product Owner approval before gate closure. Use when Gate 3 is active, for readiness validation, or for decisioning progression.

Core Features & Use Cases

  • Orchestrates Gate 3A UX+Design single-pass and Gate 3B Design QA handoffs with built-in validation and checkpointing.
  • Enforces local execution, revision loops, and persistence of design decisions via 03-ux.md and related artifacts.
  • Supports delta triage, AC writeback, and OQ resolution to keep the PRD aligned with UX outcomes.

Quick Start

Initiate Gate 3A UX+Design execution for the active slice and generate the initial 03-ux.md checkpoint.

Frequently Asked Questions about design-gate-orchestration

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

FAQPage Schema
How do I orchestrate UX design checkpoints for a Gate 3 review process?▼

Gate 3 UX design orchestration coordinates the single-pass handoff and Design QA substeps using validation checkpoints. It enforces local execution and persists design decisions within the 03-ux.md artifact before progressing.

What is the best way to ensure PRD alignment during a design QA closure?▼

PRD alignment during design QA closure is maintained through delta triage, acceptance criteria writeback, and open question resolution. These steps keep product requirements synchronized with the final UX outcomes.

Can I use local execution to enforce revision loops for UX handoffs?▼

Yes, local execution is enforced to run revision loops and validation checks for UX handoffs. This ensures all design artifacts meet Gate 3 readiness standards before Product Owner review.

When do I need an Orchestrator Resume Packet for design gate progression?▼

An Orchestrator Resume Packet is required when validating Gate 3 readiness and determining progression to Gate 4. It works alongside 03-ux.md checkpoints and Design Review access for Product Owner approval.

Does Gate 3 orchestration require Product Owner approval before gate closure?▼

Yes, Product Owner approval is explicitly required before Gate 3 closure. The orchestration workflow manages the complete validation sequence from initial UX handoff through Design QA to secure this final sign-off.

Why does a Gate 3 design review require validation checks and checkpointing?▼

Gate 3 design reviews require validation checks and checkpointing to ensure local execution standards are met and to manage revision loops effectively. This prevents unreviewed design decisions from advancing to Gate 4.