openspec-plus-design

Guides phased exploration and generation of OpenSpec design documents with mandatory review gates.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-plus-design-wnddnz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-plus-design
Source: https://github.com/WndDnz/modelo-relatorio-unifei-ict/tree/main/.opencode/skills/openspec-plus-design
Command: npx skills add https://github.com/WndDnz/modelo-relatorio-unifei-ict --skill openspec-plus-design-wnddnz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design documents often converge on the first obvious approach, skip tradeoff analysis, and drift from the approved proposal or spec. This Skill enforces a structured five-phase workflow that explores alternatives, secures user approval per section, and validates the final design.md against the proposal and spec before completion. ## Core Features & Use Cases - Phased Design Workflow: Runs schema resolution, approach exploration, direction selection, incremental section building, and generation in a fixed order with no skipping. - Tradeoff-Driven Exploration: Generates two or three meaningfully different design approaches with advantages, disadvantages, complexity, and a recommendation, then lets the user select the direction. - Mandatory Compliance Review: Dispatches a single-shot reviewer subagent that checks proposal alignment, spec alignment, scope drift, template compliance, YAGNI, and placeholders before the design is finalized. - Use Case: When running /opsx-new or /opsx-continue on an OpenSpec change, the skill walks you through architecture, components, data flow, error handling, and testing concerns one at a time, then writes a design.md that traces back to the approved proposal. ## Quick Start Ask the assistant to start the OpenSpec design phase for your change and follow the phase-by-phase approval prompts until design.md is written.

Frequently Asked Questions about openspec-plus-design

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

FAQPage Schema
How do I create an OpenSpec design document?

Run the design phase via /opsx-new, /opsx-continue, or openspec instructions design. The skill resolves the template, explores two or three approaches, gets your direction selection, builds each design concern with your approval, then writes design.md after a reviewer pass.

What is the difference between OpenSpec proposal, spec, and design phases?

The proposal captures why and which capabilities, the spec captures detailed requirements and scenarios, and the design captures how at architecture level. Design can run before or after spec, but must align with the proposal and any existing spec.

Can the design phase run before the spec exists?

Yes, OpenSpec allows proposal then design then spec ordering. Without a spec, the design works from proposal capabilities only and must not capture detailed requirements, since those belong to the later spec phase.

Why does the skill refuse to write design.md immediately?

The workflow forbids writing before all phases complete through section approvals, preventing premature convergence. It also requires a mandatory reviewer subagent pass to catch scope drift, contradictions, and template violations before finalizing.

What design concerns does the workflow always cover?

It walks through architecture, component structure, data flow, error handling, and testing approach, plus migration when applicable. A mandatory additional-concerns check adds template gaps and change-specific topics like security, performance, or observability.