spec-first-brainstorming

Frames ambiguous feature requests into scoped problem statements with assumptions, questions, and readiness decisions.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/GonkaGate/opencode-setup --skill spec-first-brainstorming-gonkagate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-first-brainstorming
Source: https://github.com/GonkaGate/opencode-setup/tree/main/.agents/skills/spec-first-brainstorming
Command: npx skills add https://github.com/GonkaGate/opencode-setup --skill spec-first-brainstorming-gonkagate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump from a vague feature idea straight into design or code, carrying hidden assumptions and unresolved scope conflicts into implementation. This Skill turns raw feature, refactor, or behavior-change requests into a concrete, challenge-ready problem frame before any design work begins. ## Core Features & Use Cases - Problem Framing: Rewrites ambiguous requests into a precise problem statement with behavior delta, affected actors, and system boundaries. - Scope & Assumption Tracking: Defines scope, non-goals, constraints, and marks every critical unknown as an explicit assumption with risk and validation path. - Challenge Routing: Produces prioritized open questions with owners and unblock conditions, plus a required/recommended/skippable pre-spec challenge recommendation. - Use Case: A product manager says "let's add team billing." The Skill normalizes the request, flags that it touches money and identity, lists blocking questions about seat models and proration, and marks the readiness decision as fail until those are answered. ## Quick Start Ask the AI to use spec-first brainstorming to frame your raw feature request into a problem statement, scope, assumptions, open questions, and a readiness decision before any design work starts.

Frequently Asked Questions about spec-first-brainstorming

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

FAQPage Schema
How do I turn a vague feature request into a clear problem statement?

Use spec-first brainstorming to rewrite the request into one concise problem statement identifying current behavior, desired behavior, and affected actors. It separates the requested outcome from any proposed implementation and surfaces the smallest behavior delta downstream design must preserve.

What should a problem frame include before starting design work?

A challenge-ready frame includes the normalized problem, behavior delta, scope and non-goals, constraints, explicit assumptions with validation paths, prioritized open questions with owners, and a challenge recommendation. The Skill outputs these sections in a fixed deliverable order.

When is a request ready to move from brainstorming into design?

A request is ready when the problem and behavior change are unambiguous, scope and non-goals do not conflict, critical unknowns are tracked, and open questions have owners and unblock conditions. The Skill returns an explicit pass or fail readiness decision.

When should brainstorming escalate instead of producing a frame?

Escalation happens when goals or actors remain ambiguous after clarification, when the request touches money, identity, privacy, or destructive actions, or when critical constraints are missing. The Skill states the minimum additional data needed to unblock framing.

Does spec-first brainstorming make architecture or API decisions?

No. The Skill explicitly avoids final architecture, API, data, security, or rollout decisions, which belong to downstream specialists. It only frames the problem and recommends whether a pre-spec challenge pass is required, recommended, or skippable.