skills.rest
haposoft
haposoftOFFICIAL
Explore all skills by this author →
WebsiteGitHub

hapo:brainstorm

Transforms raw ideas into validated, spec-ready designs for software architecture.

54|Updated Jan 21, 2026
Search Tags:#design#brainstorming#software development#specification#architecture planning
One-click install
npx skills add https://github.com/haposoft/cafekit --skill hapo-brainstorm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hapo:brainstorm
Source: https://github.com/haposoft/cafekit/tree/main/packages/spec/src/claude/skills/brainstorm
Command: npx skills add https://github.com/haposoft/cafekit --skill hapo-brainstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of turning raw ideas and unclear concepts into detailed, spec-ready designs without jumping into implementation.

Core Features & Use Cases

  • Scout-first Ideation: Offers a structured approach to brainstorming by first gathering information from the codebase.
  • Requirement Capture: Ensures that all necessary requirements are captured before architecture is proposed.
  • Incremental Design Approval: Allows design approval in sections to ensure clarity and buy-in from stakeholders.
  • Collaboration Tools: Provides tools and sub-agents for effective collaboration in complex design workflows.
  • Decision Register: Maintains a record of all decisions made during the brainstorming process.
  • Final Design Presentation: Presents the design in sections for user approval before moving to implementation.
  • Visual & UI Protocols: Offers guidance on how to include visual elements in the brainstorming process for better validation.
  • 4-Point Spec Review: Ensures the design document is complete and ready for the specification phase.
  • Final Handoff & Documentation: Generates a comprehensive report and moves the design to the next phase.

Quick Start

To initiate brainstorming for a new feature, use the command: /hapo:brainstorm "Define the architecture for the upcoming feature X."

Frequently Asked Questions about hapo:brainstorm

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

FAQPage Schema
How do I transform a raw software idea into a spec-ready architecture?▼

Structured brainstorming transforms raw ideas into spec-ready designs by capturing exact requirements and validating architectural planning before implementation. It performs detailed codebase inspection to ensure proposed designs align with existing software development constraints.

What is the best way to capture software requirements before proposing an architecture?▼

The best way to capture software requirements before proposing an architecture is using a scout-first ideation approach. This method gathers information directly from the codebase to ensure all necessary specifications are documented before any architectural design is proposed or validated.

How do I get stakeholder buy-in during the software design and brainstorming process?▼

You get stakeholder buy-in during software design through incremental design approval. This process presents the architecture in distinct sections for review, maintains a decision register of all choices, and ensures clarity before moving to the final specification phase.

Can I use structured brainstorming for complex architectural planning in software development?▼

Yes, you can use structured brainstorming for complex architectural planning in software development. It utilizes internal collaboration tools and sub-agents to manage design workflows, ensuring detailed requirement capture and incremental validation for complex software architectures.

Does the brainstorming workflow include visual and UI protocols for design validation?▼

Yes, the brainstorming workflow includes visual and UI protocols for design validation. It offers specific guidance on incorporating visual elements into the architectural planning process, ensuring that user interface designs are thoroughly reviewed before the final handoff.

When should I not jump directly into software implementation from a raw idea?▼

You should not jump directly into software implementation from a raw idea when architectural clarity is required. Skipping structured brainstorming and specification validation risks misaligned designs, missing requirements, and缺乏 stakeholder buy-in for complex software development projects.

Related Skills

Explore More Software Engineering Skills→
securityreviewaisecurityreviewai

project-overview-analysis

Analyzes Git repositories to produce summaries of their structure, risks, and key components.

Official
Intermediate
mortenbroesbymortenbroesby
1

writing-plans

Generate implementation plans with task steps and file changes from a spec.

Community
Advanced
damianpapadopoulosdamianpapadopoulos
6

design-debate

Facilitate a multi-agent design debate among architect, critic, and pragmatist roles.

Community
Advanced
Bbeierle12Bbeierle12
8

component-library

Generate production-ready React components for a shadcn/ui component library.

Community
Advanced