openspec-plus-proposal

Guides interactive discovery to write intent-level OpenSpec change proposals.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing an OpenSpec change proposal often jumps straight into solutions, tech choices, or implementation plans, which pollutes downstream specs and designs. This Skill enforces a disciplined, intent-level proposal process so the Why, What, Scope, Non-Goals, and Impact are captured before any design work begins. ## Core Features & Use Cases - Five-Lens Interactive Discovery: Walks through Problem & Why, Goals, Scope & Capabilities, Non-Goals, and Impact one question at a time (or batched), always with a recommended answer. - Template-Driven Writing: Resolves the official OpenSpec proposal template via openspec instructions proposal --json and maps every discovery answer into the exact required sections. - Automated Compliance Review: Dispatches a reviewer subagent to check for solution language, design leaks, placeholders, missing non-goals, and template violations before user review. - Use Case: When you run /opsx-new to start a change like "add user notifications", the Skill interviews you about the underlying problem and scope boundaries, then produces a clean proposal in openspec/changes/ ready for the spec phase. ## Quick Start Ask the assistant to create a new OpenSpec proposal for your change idea and answer the discovery questions it asks.

Frequently Asked Questions about openspec-plus-proposal

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

FAQPage Schema
How do I create an OpenSpec change proposal?

Start the proposal phase with /opsx-new or openspec-new-change, then answer the five discovery lenses: problem, goals, scope, non-goals, and impact. The Skill resolves the official template with openspec instructions proposal and writes the proposal file for review.

What should an OpenSpec proposal contain?

An OpenSpec proposal contains Why, What Changes, Capabilities, and Impact sections at intent level. It must state explicit non-goals and avoid solution language, technology choices, architecture, tasks, or implementation plans, which belong to later phases.

Can one proposal cover multiple independent features?

No. A proposal must describe a single cohesive change. If a request spans independent subsystems like chat, billing, and analytics, the Skill stops and helps decompose the work into separate proposals, each with its own spec, design, and tasks cycle.

Does the proposal phase read source code?

No. The proposal phase never reads source code because it captures intent, not implementation grounding. It only reads project instruction files like AGENTS.md or CLAUDE.md and existing proposals in openspec/changes/ for terminology and conventions.

Why does the proposal review use a subagent?

A single-shot reviewer subagent checks the written proposal against the template for solution language, design leaks, placeholders, and scope cohesion. Loading it in a separate context keeps the review objective, and findings are fixed inline without re-dispatch.