design

Translate approved research and goals into a validated system architecture and vertical slices.

36|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/dfrysinger/qrspi-plus --skill design-dfrysinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/dfrysinger/qrspi-plus/tree/main/skills/design
Command: npx skills add https://github.com/dfrysinger/qrspi-plus --skill design-dfrysinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate research and approved goals into a concrete architecture and phased implementation plan that proves end-to-end vertical slices, preventing horizontal-only decompositions and unclear phase boundaries.

Core Features & Use Cases

  • Interactive design discussion: Lead a conversational design process that proposes 2-3 approaches, highlights trade-offs, and records key decisions.
  • Vertical slice and phase definition: Define explicit vertical slices, a PoC phase that proves the full stack, and replan gates for multi-phase work.
  • Review orchestration and artifact synthesis: Synthesize design.md via a subagent, run Claude and optional Codex review rounds, write reviews/design-review.md, and gate progression on human approval.
  • Use case: When research/summary.md and goals.md are approved, use this Skill to produce an approved design.md that guides implementation and testing.

Quick Start

Ask the agent to run the design skill to synthesize a draft design.md after goals.md and research/summary.md are approved.

Frequently Asked Questions about design

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

FAQPage Schema
How do I translate approved research and goals into a validated system architecture?

To translate approved research into a validated system architecture, use an interactive design process that proposes approaches, defines vertical slices, and synthesizes a design.md file for review and approval.

What is vertical-slice architecture design and why use it?

Vertical-slice architecture design defines explicit end-to-end functional slices and a PoC phase, preventing horizontal-only decompositions and clarifying phase boundaries by proving the full stack early.

How do I define replan gates and phases for multi-phase implementation?

Define replan gates and phases by establishing a PoC phase that proves the full stack, then setting explicit boundaries for subsequent vertical slices to guide implementation and testing.

Do I need approved goals.md and research/summary.md before architecture design?

Yes, you need approved goals.md and research/summary.md files. The architecture design process requires these approved artifacts to propose approaches and produce a synthesized design.md.

Can I orchestrate Claude and Codex review rounds for design.md synthesis?

Yes, you can orchestrate Claude and optional Codex review rounds. The process synthesizes design.md via a subagent, runs iterative reviews, writes reviews/design-review.md, and gates progression on human approval.

What's the best way to prevent horizontal-only decomposition in system design?

The best way to prevent horizontal-only decomposition is to define explicit vertical slices that prove end-to-end functionality, ensuring clear phase boundaries and a validated PoC phase for the full stack.