Guide architectural design brainstorming through understanding, exploration, and validation stages.
npx skills add https://github.com/axivo/claude --skill brainstorming-axivo
Please help me install this Agent Skill. Skill: brainstorming Source: https://github.com/axivo/claude/tree/main/skills/brainstorming Command: npx skills add https://github.com/axivo/claude --skill brainstorming-axivo
This Skill helps users overcome design paralysis and ensures robust architectural decisions by providing a structured, collaborative dialogue process. It adapts to different expertise levels, making complex technical discussions accessible and productive for everyone involved, ultimately saving time on rework and clarifying requirements upfront.
Let's brainstorm ideas for a new user authentication system, considering scalability and security requirements.
High-intent search queries and answers about installing and using this skill.
Structure your design discussion through four stages: understand requirements and constraints, explore 2–3 architectural alternatives with trade-offs documented, validate the chosen approach against functional requirements, and document the rationale. This staged flow ensures comprehensive coverage before implementation.
Use adaptive dialogue that adjusts depth and technical language based on participants' backgrounds. This makes complex design discussions accessible to everyone—from experts to those with limited technical knowledge—ensuring productive collaboration and alignment.
During the exploration stage, generate 2–3 distinct architectural alternatives. For each, document the trade-offs explicitly—covering scalability, security, performance, and other critical concerns. This enables informed comparison and validates which approach best fits your requirements.
Yes. The structured design flow applies to both feature and system design sessions. It guides teams through understanding, exploration, and validation regardless of scope, ensuring architectural decisions are robust and well-reasoned at any scale.
Document alignment checks that confirm all participants agree on requirements and chosen approach, and record the rationale behind architectural decisions. This validation stage clarifies expectations upfront and reduces downstream rework.
stephanjDefine EARS-format feature specifications and testable acceptance criteria from stakeholder interviews.
pradeepmouliConvert feature specifications into structured plan.md technical designs.
ccfDocument architectural decisions with a MADR-style template and lifecycle.
TheGreatLCreate and manage architecture decision records with multiple format templates.
