Verified:GitHub

harness:brainstorming

Convert product or engineering ideas into approved design specifications before implementation.

3|1|Updated Apr 5, 2026

Search Tags:#architecture #documentation #brainstorming #implementation planning #requirements #approval workflow #design spec

Ready to run

npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-brainstorming

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness:brainstorming
Source: https://github.com/huangbaixun/harness-engineering/tree/main/skills/brainstorming
Command: npx skills add https://github.com/huangbaixun/harness-engineering --skill harness-brainstorming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted engineering cycles by forcing ideas to be converted into clear, user-approved designs before any implementation begins.

Core Features & Use Cases

Structured brainstorming with hard gates: Enforces a design-before-code workflow that blocks implementation skills until the design is presented and approved.
Incremental design refinement: Guides the workflow through project context exploration, one-at-a-time clarifying questions, and 2–3 approach options with trade-offs.
Spec and documentation production: Creates a validated design spec saved to the agreed path format and commits it, then transitions to an implementation plan.
Optional visual companion for visual questions: Offers an opt-in browser companion for mockups, diagrams, and visual comparisons without forcing it for every step.

Quick Start

Ask for the brainstorming design for your requested change, and include the idea plus any constraints so the skill can produce an approved spec before planning implementation.

Frequently Asked Questions about harness:brainstorming

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

FAQPage Schema

How do I turn product ideas into approved design specifications before implementation?▼

To turn product ideas into approved design specifications, you need a structured brainstorming workflow that enforces hard design gates. This process requires presenting design approaches, obtaining user approval, and creating a validated spec before any implementation planning begins.

What is the best way to refine feature requirements and define component behavior?▼

The best way to refine feature requirements and define component behavior is through incremental design refinement. This involves exploring project context, asking clarifying questions one at a time, and presenting 2-3 approach options with clear trade-offs for user selection.

How does a design approval workflow prevent wasted engineering cycles?▼

A design approval workflow prevents wasted engineering cycles by acting as a safety gate that blocks implementation tasks. It mandates design presentation and explicit user approval, ensuring scope and success criteria are fully clarified and documented before coding starts.

Can I use visual mockups and diagrams during the brainstorming design process?▼

Yes, you can use visual mockups and diagrams during the brainstorming design process via an optional browser companion. This opt-in tool handles visual questions, mockups, and visual comparisons without forcing visual overhead for every single workflow step.

How do I create and save a design spec for implementation planning?▼

To create and save a design spec for implementation planning, you commit a validated design specification to an agreed path format. After completing the spec and review gates, the workflow transitions directly into writing the implementation plan.

Do I need a fully defined scope to start brainstorming a new feature design?▼

No, you do not need a fully defined scope to start brainstorming a new feature design. You can begin with a basic idea and constraints, and the workflow will guide you through clarifying questions and trade-off analysis to clarify scope and success criteria.