RCP-001-001-014-CRAFT-BRAINSTORMER – CRAFT Framework Innovation Brainstormer


How To Start
- After hundreds (perhaps thousands) of hours of using these recipes, I rarely need to use any of the CORE Cookbook recipes aside from Recipes RCP-001-001-002-HANDOFF-SNAPSHOT and RCP-001-001-002-HANDOFF-SNAPSHOT, but when I do, they are essential to the functioning of CRAFT. Also, the A.I. reads all of these recipes at the start of each session. This happens quietly in the background. Even though you may never need to call the recipe, the A.I. will know all of them and it helps the A.I. to understand what CRAFT is and how it works. Even if you rarely need to use these recipes, they are still working for you and are essential to the CRAFT Framework.
- Set constraint mode based on parameter: BLUE SKY MODE No implementation limits Focus on vision and possibility Dream big without technical barriers PRACTICAL MODE Consider current technical constraints Balance innovation with feasibility Ideas should be achievable with effort IMMEDIATE MODE Only ideas implementable now Use existing framework capabilities Quick wins with current tools
- Narrow ideation based on focus_area parameter: GENERAL Consider all aspects of CRAFT RECIPES Focus on recipe creation, discovery, execution, and composition PERSISTENCE Explore state management, variable storage, and cross-session memory COLLABORATION Enhance multi-user, multi-AI, or team workflows SECURITY Strengthen safety, validation, and protection mechanisms USABILITY Improve user experience and reduce learning curve PERFORMANCE Optimize token usage, speed, and efficiency
- For each of the num_ideas ideas, structure as: IDEA NUMBER: DESCRIPTIVE NAME WHAT IS IT Concise description of the functionality in 2-3 sentences. WHICH CRAFT COMPONENTS ARE INVOLVED Website – How it uses or enhances the site Handoff File – Impact on session continuity Cookbook File – Recipes or modifications Specification – Framework changes required Project File – Project implementations WHAT PRINCIPLES DOES IT IMPROVE Core Purpose Improvements: Specific challenge addressed Philosophical Principles Enhanced: 1-3 principles from framework Fundamental Guiding Principles Advanced: 1-2 fundamental principles HOW WOULD IT WORK Based on depth_level, provide: Key mechanism – Primary way it works User experience – How users interact Integration points – CRAFT connections
- For each main idea, provide 2-5 extensions: Natural extension or enhancement Complementary feature Advanced capability building on this Integration with other CRAFT components Future evolution possibility
- Apply consistent scoring 1-10 for each: INNOVATION SCORE How novel is this idea? Does it solve problems in new ways? FEASIBILITY SCORE How practical is implementation? What resources are required? IMPACT SCORE How much value does it provide? How many users would benefit?
- Prioritize ideas that demonstrate: SOLVING REAL PROBLEMS Addresses actual pain points Users immediately understand value PHILOSOPHICAL ALIGNMENT Embodies CRAFT core principles Enhances rather than complicates TECHNICAL ELEGANCE Can be implemented cleanly Integrates naturally with existing TOKEN EFFICIENCY Reduces repetition Saves tokens in practice SCALABILITY Works for simple and complex cases Grows with user needs
- Stimulate additional ideation with: What if CRAFT could…? How might we eliminate the need for…? What would make users say WOW? How can we make complex feel simple? What patterns could we standardize?
When to Use This Recipe
Recipe FAQ
A: Use blue_sky for vision sessions, practical for
roadmap planning, and immediate for quick wins. Q: What if generated ideas seem unrealistic?
A: Adjust constraint_mode to practical or immediate
for more feasible suggestions. Q: Can I combine ideas from multiple focus areas?
A: Run the recipe multiple times with different
focus areas, then synthesize the results. Q: How do I act on high-scoring ideas?
A: Create implementation plans for ideas scoring
high across all three dimensions. Low feasibility
with high impact may warrant long-term roadmap. Q: Should I save brainstorming outputs?
A: Yes, capture outputs in handoff notes or project
documentation for future reference.
