project-brainstorming
Installation
SKILL.md
When To Use
- Starting a new project without clear requirements
- Exploring problem space before specification
- Need to compare multiple approaches systematically
- Validating project feasibility and scope
- Documenting decision rationale for stakeholders
- Need to clarify the core problem being solved
When NOT To Use
- Requirements and specification already exist (use
Skill(attune:project-planning)instead) - Refining existing specs (use
Skill(attune:project-specification)instead) - Project scope is well-defined (jump to
/attune:project-init) - Mid-project pivots (use
Skill(attune:war-room)for strategic decisions)
Integration
With superpowers:
- Delegates to
Skill(superpowers:brainstorming)for Socratic method
Related skills
More from athola/claude-night-market
project-planning
Turn a specification into a phased implementation plan with dependency ordering.
126code-quality-principles
KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity and preventing over-engineering.
94doc-generator
Generate or remediate documentation with human-quality writing and style.
81rigorous-reasoning
Anti-sycophancy reasoning checklist.
79project-specification
Transform project briefs into testable specifications with user stories, acceptance criteria, and measurable outcomes.
78bloat-detector
Detect codebase bloat via progressive analysis: dead code, duplication, complexity, and doc bloat.
71