Generate categorized questions to explore project requirements, constraints, and assumptions.
npx skills add https://github.com/B4san/Calix-Pass --skill brainstorming-b4san
Please help me install this Agent Skill. Skill: brainstorming Source: https://github.com/B4san/Calix-Pass/tree/main/.gemini/skills/brainstorming Command: npx skills add https://github.com/B4san/Calix-Pass --skill brainstorming-b4san
This Skill helps you identify all potential questions, assumptions, and risks associated with a new project or feature before you start implementation, preventing costly rework and missed requirements.
Use the brainstorming skill to generate questions for building a new user authentication system.
High-intent search queries and answers about installing and using this skill.
To identify project requirements and unknowns before development, generate categorized questions covering constraints, user experience, and technical architecture. This process surfaces hidden assumptions and risks early, preventing costly rework and missed requirements during implementation.
The best way to gather requirements for a new software feature is to systematically probe areas like edge cases, success criteria, dependencies, and alternatives. Generating comprehensive questions helps uncover constraints and technical architecture needs before coding begins.
Uncovering hidden technical assumptions and risks in project planning requires explicitly questioning potential failure modes and blockers. By categorizing questions into requirements, dependencies, and alternatives, teams can surface unknowns and mitigate risks early.
Risk assessment and assumption surfacing are needed before implementing any new project or feature, such as a user authentication system. Performing this early prevents costly rework by ensuring security, scalability, and integration points are evaluated beforehand.
Question-based brainstorming works for technical architecture and edge cases by generating an organized prompt that explores success criteria and constraints. It ensures all angles are considered, bringing unknowns into the open for discussion before development.
syahrilTGRGuide structured brainstorming to define software designs and specifications.
leifericfAnalyze planning documents to surface risks and generate mitigation strategies.
CygnusfearDocument engineering decisions as ADRs with rationale and decision logs.
viktorbezdekIdentify missing edge cases and boundary conditions for software components.
