Guide structured brainstorming from vague ideas to validated design specs.
npx skills add https://github.com/HexSleeves/skills --skill staff-brainstorming
Please help me install this Agent Skill. Skill: staff-brainstorming Source: https://github.com/HexSleeves/skills/tree/main/skills/staff-brainstorming Command: npx skills add https://github.com/HexSleeves/skills --skill staff-brainstorming
This Skill prevents rushed implementation by forcing a clear design discussion first. It helps turn vague ideas into validated requirements, constraints, and a shared plan before any code or scaffolding is created.
Use the staff-brainstorming skill to examine the project context and guide me through a design conversation for the change I want to make.
High-intent search queries and answers about installing and using this skill.
To turn vague ideas into validated design specs, use a structured brainstorming process that enforces sequential discovery, tradeoff analysis, and design presentation before any implementation begins. This prevents rushed coding by clarifying requirements and constraints first.
The best way to control scope for architecture changes is through design validation, where you present architecture, data flow, error handling, and testing plans for explicit approval before proceeding to implementation planning.
Brainstorming technical alternatives involves proposing 2-3 approaches and recommending one with clear reasoning. This tradeoff analysis happens after narrowing scope through focused, one-question-at-a-time discovery.
Yes, you can use this structured design process for component design, behavior changes, and feature planning. It applies to any creative or technical changes requiring scope control and approval.
Writing a design specification involves producing the spec document, self-reviewing it for gaps, and then handing it off to implementation planning. This documentation workflow ensures all requirements and constraints are captured before development starts.
You should not skip design discovery when a feature or behavior change requires scope control and approval. Rushing implementation without context exploration and sequential discovery risks building the wrong solution.
chuan-khunaGather design context and persist it to .impeccable.md.
haposoftAutomate implementation of approved software specification tasks with design context.
yasarremreMap and analyze codebases to reveal architecture and dependencies.
jzallenStructure throwaway prototypes with a three-phase build, learn, and rebuild process.
