design

Enforce design-first approval gates before code generation in agentic development.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/SeaBrad72/sparkwright --skill design-seabrad72
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/SeaBrad72/sparkwright/tree/main/skills/design
Command: npx skills add https://github.com/SeaBrad72/sparkwright --skill design-seabrad72

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents wasted engineering effort by enforcing a rigorous design-first process, ensuring that every feature or change is scoped, reviewed, and approved by an owner before any implementation begins.

Core Features & Use Cases

  • Design-First Guardrails: Implements a hard gate that blocks code generation until a design spec is authored and approved.
  • Provenance Tracking: Supports multiple design sources, from original authorship to confirming existing backlog items or architectural decisions.
  • Use Case: Before building a new authentication module, use this skill to document the architecture, trade-offs, and security requirements, ensuring the owner signs off on the approach before a single line of code is written.

Quick Start

Initiate the design process for your current feature by asking the agent to walk you through the design flow and help you draft the initial specification.

Frequently Asked Questions about design

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

FAQPage Schema
How do I enforce a design-first workflow before code generation starts?

To enforce a design-first workflow, you need a formal approval gate that blocks code generation until a technical specification is authored and signed off by the project owner. This prevents wasted engineering effort on unscoped features.

What is the best way to validate architecture and security requirements before implementation?

Validating architecture and security requirements before implementation requires documenting design trade-offs and control-plane security constraints in a specification. An owner must then review and approve this design before any coding begins.

Can I use this design spec workflow for existing backlog items and architectural decisions?

Yes, this design spec workflow supports multiple provenance sources, allowing you to confirm existing backlog items or prior architectural decisions. It tracks the origin of your designs while enforcing the same mandatory owner approval gates.

How do I document design provenance for agentic software development?

Documenting design provenance for agentic software development involves tracking the source of your specifications, whether from original authorship or confirming existing decisions. This ensures architectural rigor is maintained across all project phases.

Why should I require owner-approved technical specifications before building a new module?

Requiring owner-approved technical specifications before building a new module ensures the approach is rigorously reviewed for architectural and security impacts. This design-first gate prevents wasted effort by forcing alignment before implementation begins.

How do I draft an initial specification for a new software feature?

To draft an initial specification for a new software feature, initiate the design process by asking the agent to walk you through the design flow. This helps you document the architecture, trade-offs, and security requirements for owner review.