Guide pre-implementation design through requirement clarification, tradeoff analysis, and incremental approval.
npx skills add https://github.com/hicucu/forge --skill brainstorming-hicucu
Please help me install this Agent Skill. Skill: brainstorming Source: https://github.com/hicucu/forge/tree/main/skills/brainstorming Command: npx skills add https://github.com/hicucu/forge --skill brainstorming-hicucu
Jumping straight into implementation without clarifying requirements and finalizing a design leads to wasted work, rework, and building features that don't match user needs. This skill eliminates that risk by enforcing a structured, collaborative process to refine ideas into fully approved, actionable designs before any coding begins.
Use the brainstorming skill to walk through your idea for a new feature, component, or change, present a structured design for your approval, and generate a saved spec document before moving to implementation planning.
High-intent search queries and answers about installing and using this skill.
To prevent rework, feature spec writing requires structured requirement clarification, tradeoff analysis, and incremental design approval to ensure full alignment before implementation begins. This process eliminates ambiguity and saves the finalized design to a workspace file.
The best way to plan new feature designs is through a guided process that asks targeted questions to eliminate ambiguity, presents viable implementation approaches with clear tradeoffs, and breaks design presentation into sections for incremental approval.
Comparing implementation approaches involves evaluating 2-3 viable options with clear tradeoffs and selecting a recommended path to align on the best direction before construction begins. This ensures tradeoff-aware decision making during feature planning.
Pre-build design approval applies to behavior modifications, new feature builds, and component construction. It enforces requirement gathering and spec documentation to ensure full alignment before any implementation planning starts.
Documenting approved designs involves saving the finalized design to a workspace file, running a self-review to catch gaps, and requesting user sign-off. This automated spec documentation ensures actionable designs are ready for implementation planning.
Structured requirement gathering is needed for all pre-implementation creative work, including new feature builds and behavior modifications. Skipping this pre-build design phase leads to wasted work, rework, and building features that don't match user needs.
bacchus-labsTransform raw ideas into validated design specifications through structured questioning.
xtrm-devGuide collaborative brainstorming from vague ideas to approved design specifications.
MarkusonParse epic and story markdown to generate sprint-status.yaml tracking files.
jzallenStructure throwaway prototypes with a three-phase build, learn, and rebuild process.
