Facilitate structured brainstorming and design validation for OpenSpec changes.
npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-brainstorm
Please help me install this Agent Skill. Skill: openspec-brainstorm Source: https://github.com/mrclrchtr/SuPi/tree/main/skills/openspec-brainstorm Command: npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-brainstorm
Many feature ideas or small changes are implemented before their assumptions, constraints, and success criteria are clarified, leading to rework and misaligned implementations. This Skill guides collaborative exploration of intent, constraints, and trade-offs so a clear, approved design is produced before any OpenSpec or implementation steps are taken.
Ask it to brainstorm an OpenSpec change for <brief idea>, explore project context, ask clarifying questions one at a time, propose approaches with trade-offs, and produce a short handoff brief recommending the next OpenSpec step.
High-intent search queries and answers about installing and using this skill.
Structured brainstorming validates product design ideas by guiding context exploration, enforcing incremental one-question-at-a-time clarifications, and comparing approaches with trade-offs to produce an approved design before implementation begins.
The best way to explore project features is to analyze existing project files and OpenSpec context, then propose 2–3 approaches with explicit trade-offs and a preferred recommendation scaled to the feature's complexity.
Creating a design handoff brief involves producing a concise, reviewed summary of the approved design that recommends the next OpenSpec command, without directly editing or modifying existing OpenSpec artifacts.
Yes, you can use an optional browser-based visual companion tool for mockups and diagrams during requirements elicitation, provided explicit consent is given before launching the visual support.
Yes, effective brainstorming for OpenSpec changes requires reading project files, docs, recent commits, and existing OpenSpec artifacts to ensure informed questioning and context-aware design validation.
You should avoid structured brainstorming for spec changes when implementation assumptions, constraints, and success criteria are already fully clarified, as the process is designed to prevent rework on misaligned or unexamined feature ideas.
LayerDynamicsFacilitate structured brainstorming to define feature intent and requirements.
billh93Plan UX and UI by running a structured discovery interview and producing a design brief.
ArtemioPadillaRender architecture diagrams, UI mockups, and data flows in a browser.
darkmatterStructure ambiguous ideas into an approved design before implementation.
