spec-brainstorm

Analyze software problems and document architectural tradeoffs in a draft directory.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/eavichay/mycli --skill spec-brainstorm-eavichay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-brainstorm
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/spec-brainstorm
Command: npx skills add https://github.com/eavichay/mycli --skill spec-brainstorm-eavichay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the ambiguity and lack of structure often present in the early stages of software development by forcing a rigorous exploration of problem spaces, tradeoffs, and architectural constraints before any code is written.

Core Features & Use Cases

  • Structured Exploration: Guides the user through problem understanding, approach identification, and risk assessment using predefined lenses.
  • Architectural Context: Synthesizes findings into a formal brainstorm document that serves as the foundation for subsequent specification creation.
  • Use Case: Before building a new complex feature, use this skill to evaluate multiple technical approaches and document potential risks to ensure the final specification is robust and well-considered.

Quick Start

Run the spec-brainstorm skill to explore the architectural requirements for the new task management module.

Frequently Asked Questions about spec-brainstorm

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

FAQPage Schema
How do I evaluate technical approaches for software architecture before writing a specification?

Structured architectural exploration helps evaluate technical approaches by guiding you through problem understanding, risk assessment, and tradeoff documentation within a dedicated draft directory before creating formal specifications.

When should I do architectural exploration and problem space analysis for a new software feature?

You need architectural exploration before building complex software features to rigorously evaluate problem spaces, tradeoffs, and constraints. This synthesizes findings into a formal brainstorm document that serves as the foundation for specification creation.

Do I need a spec-kit compatible project structure to run architectural brainstorming?

Yes, a spec-kit compatible project structure is required to execute lifecycle hooks and generate context documents during architectural brainstorming. Without this structure, the skill cannot properly synthesize findings into formal brainstorm documents.

What's the best way to document architectural constraints and technical debt during software design?

The best way to document architectural constraints and technical debt is through predefined lenses that guide problem understanding and approach identification. This process evaluates multiple technical approaches and documents potential risks within a dedicated draft directory.

How does structured architectural exploration work for software development projects?

Structured architectural exploration works by identifying core problems, evaluating multiple technical approaches, and documenting tradeoffs using predefined lenses. It operates within a dedicated draft directory to synthesize findings into a formal brainstorm document.