spec-gen-brainstorm

Transform feature ideas into testable annotated stories with greenfield or brownfield detection.

270|34|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/clay-good/spec-gen --skill spec-gen-brainstorm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-gen-brainstorm
Source: https://github.com/clay-good/spec-gen/tree/main/examples/mistral-vibe/skills/spec-gen-brainstorm
Command: npx skills add https://github.com/clay-good/spec-gen --skill spec-gen-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts a high-level feature idea into a structured, testable, and annotated story while automatically detecting whether the work is greenfield or brownfield so design stays aligned with the existing codebase and risk profile.

Core Features & Use Cases

  • Automatic mode detection: Probes the spec-gen structural index to choose greenfield (Domain Sketch) or brownfield (Constrained Option Tree) workflows.
  • Architecture-aware options and gating: Generates change proposals, assesses risk scores, recommends approaches, and blocks high-risk changes until a refactor is agreed.
  • Story generation and annotation: Writes story files from templates, enforces verifiable acceptance criteria, and annotates risk context via spec-gen MCP tools when available.
  • Use case: A product manager or engineer exploring "payment-retry-flow" receives 2–3 constrained options, a recommended approach, devil's-advocate failure modes, and a ready-to-run story file.

Quick Start

Brainstorm a new payment-retry-flow feature by describing the goal and constraints and ask to "create an annotated story with risk context and verifiable acceptance criteria".

Frequently Asked Questions about spec-gen-brainstorm

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

FAQPage Schema
How do I turn a feature idea into testable stories for a brownfield codebase?

To turn a feature idea into testable stories for a brownfield codebase, this skill probes the structural index to detect existing code, then generates constrained option trees, assesses risk scores, and writes annotated story files with verifiable acceptance criteria.

What is the best way to brainstorm greenfield feature design and generate a ready-to-run story?

The best way to brainstorm greenfield feature design is applying a Domain Sketch workflow, which generates 2-3 constrained options, a recommended approach, devil's-advocate failure modes, and a ready-to-run story file with verifiable acceptance criteria.

How does risk assessment work when generating change proposals for new features?

Risk assessment for change proposals works by scoring architectural impact and blocking high-risk changes until a refactor is agreed, annotating the story file with explicit risk context via structural analysis tools.

Can I use spec-gen tools to impose risk gates on high-risk feature changes?

Yes, you can use spec-gen tools to impose risk gates by probing the structural index, generating change proposals, and automatically blocking high-risk changes until an agreed refactor occurs.

Do I need existing code for the structural index to choose between greenfield and brownfield workflows?

You do not need existing code for greenfield workflows, but detecting existing code via the structural index triggers the brownfield Constrained Option Tree workflow to align design with the current codebase and risk profile.