Compare solution options with trade-offs and recommend one path.
npx skills add https://github.com/linenoize/topia --skill brainstorm-linenoize
Please help me install this Agent Skill. Skill: brainstorm Source: https://github.com/linenoize/topia/tree/main/skills/brainstorm Command: npx skills add https://github.com/linenoize/topia --skill brainstorm-linenoize
This Skill helps you avoid jumping straight into implementation by generating and comparing multiple solution approaches, especially when the right path is unclear or the first attempt failed.
Use the brainstorm skill to explore a problem, compare a few viable approaches, and recommend the best one with trade-offs.
High-intent search queries and answers about installing and using this skill.
Architecture trade-off analysis requires generating distinct solution options with explicit constraints, evaluating pros, cons, effort, and risk for each. You compare these viable approaches against hard design gates to recommend a single path before planning begins.
Solution exploration uses mode-based thinking workflows like discovery, vision, rescue, and design-it-twice to evaluate multiple approaches. This structured ideation produces clear comparative trade-offs so you can confidently choose the best implementation strategy.
Reframing a broken approach uses rescue workflows to analyze the failed implementation and generate alternative design options. By applying explicit constraints and comparative trade-off analysis, you identify a new recommended path to replace the failed architecture.
Yes, structured ideation supports evaluating alternative module interfaces through design-it-twice workflows. It forces explicit constraints and hard design gates, providing comparative trade-offs and a single recommended interface path before you commit to coding.
Brainstorming without explicit constraints fails to produce guardrailed decisions, risking unstructured ideation. Without forcing comparative trade-off analysis and hard design gates, you cannot confidently recommend a single viable path before handing off to implementation planning.
Design review workflows are needed when multiple viable approaches exist for product or coding decisions, or when an initial approach has failed. They enforce comparative trade-off analysis and constraint evaluation to yield a single recommended path.
maestria-coFrame design problems and document architecture decisions as ADRs.
dxc-dannyIdentify project goals, constraints, and success criteria, then propose design options with trade-offs.
14790897Create and evaluate Architecture Decision Records documenting technical trade-offs.
nikhilvallishayeePrototype minimal viable outputs through rapid build-test cycles.
