design-proposer

Draft a bounded sprint contract from design.md and expose an awaiting_human approval gate.

28|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/labs21-dev/agents-stack --skill design-proposer-labs21-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-proposer
Source: https://github.com/labs21-dev/agents-stack/tree/main/templates/.agents/skills/frontend-design/design-proposer
Command: npx skills add https://github.com/labs21-dev/agents-stack --skill design-proposer-labs21-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a design.md exists with a design_spec phase, this skill ensures a clearly scoped sprint contract is produced and a human approval gate is enforced before any build begins. It prevents scope creep and misaligned expectations by converting intent into a concrete, testable design contract that guides downstream work.

Core Features & Use Cases

  • Drafts a bounded sprint contract anchored to the design spec and vocabulary reference, ensuring explicit acceptance criteria and success metrics.
  • Reads and cross-references AGENTS.md, design.md, and tracked-work.json to align stakeholders, constraints, and priorities, and to surface gaps for human review.
  • Supports a structured handoff into the build phase with an approval gate and a clear contract artifact stored under .agents-stack/<sprint-id>/design.md.

Quick Start

Provide the human brief and let design-proposer draft the bounded sprint contract in design.md and pause for human approval.

Frequently Asked Questions about design-proposer

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

FAQPage Schema
How do I turn a design brief into a bounded sprint contract with human approval?▼

A sprint contract prevents scope creep by converting design intent into a concrete, testable specification with explicit acceptance criteria and success metrics, ensuring alignment before any build phase begins.

What is the best way to enforce a human approval gate before starting a build phase?▼

Enforce a human approval gate by generating a design proposal artifact that pauses execution, exposing an awaiting_human state to review outputs, variation axes, and acceptance criteria before any construction starts.

How do I generate design specifications and acceptance criteria from existing project files?▼

Supporting inputs include AGENTS.md, design.md, and tracked-work.json, which are cross-referenced to align stakeholders, surface gaps for review, and produce the precise sprint specification.

Where should the design proposal artifact be stored for sprint tracking?▼

The design proposal artifact should be stored at .agents-stack/<sprint-id>/design.md, containing the proposal, outputs, variation axes, and acceptance criteria to guide downstream work.

When do I need a design_spec phase to produce a sprint contract?▼

You need a design_spec phase when a design.md exists and you must articulate a bounded sprint contract, preventing misaligned expectations by converting intent into a testable design contract.