@hanzlaa/rcode 3.6.16 → 4.1.0

package/rcode/skills/core/rcode-auth-audit/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: rcode-auth-audit
+description: Audit Keycloak ↔ Active Directory sync, JWT validation, and tenant isolation in multi-org Postgres.
+triggers:
+  - "auth audit"
+  - "keycloak ad sync"
+  - "users disappearing"
+  - "ghost session"
+  - "tenant leak"
+  - "jwt validation check"
+  - "stale token"
+  - "session not invalidating"
+user-invocable: true
+---
+@.rcode/references/karpathy-guidelines.md
+
+
+## Overview
+
+Authentication bugs are usually silent — the user just gets logged out, or worse, sees someone else's data. This skill encodes the specific failure modes that have actually bitten rcode projects, with a runnable 10-minute checklist. Default scope is Keycloak + Active Directory + Postgres; adapt the specifics to whatever provider is in use.
+
+## The 10-minute checklist
+
+### Keycloak ↔ AD sync (the load-bearing one)
+
+- [ ] Keycloak's AD federation is configured with **periodic sync ENABLED**, not just on-login. Without periodic sync, a user deactivated in AD keeps working in Keycloak until their token expires.
+- [ ] Sync interval ≤ 1 hour for production. Longer windows are how the rcode incident happened.
+- [ ] Sync errors land in Sentry, not just Keycloak's internal log. If sync silently fails, no one notices for weeks.
+- [ ] On AD deactivation, the corresponding Keycloak session is **explicitly invalidated** — don't rely on the JWT expiring.
+
+### JWT validation
+
+- [ ] `iss`, `aud`, `exp`, signature — all four checked on every protected request.
+- [ ] JWKS keys are **fetched dynamically with caching**, not pinned. Keycloak rotates them.
+- [ ] Clock-skew tolerance is ≤ 60s. Larger windows give attackers reuse room.
+- [ ] Token revocation list (or short TTL + refresh) is in place. Stateless JWTs are a CVE waiting for "logout doesn't actually log out".
+
+### Tenant isolation in Postgres
+
+- [ ] Every query that reads tenant data has `WHERE tenant_id = $1` where `$1` is **derived from the JWT**, never from a request parameter or cookie.
+- [ ] Postgres Row-Level Security (RLS) policies are enabled OR a query middleware enforces tenant_id (belt + suspenders preferred).
+- [ ] No raw SQL strings interpolate tenant_id — always parameterised.
+- [ ] Audit log captures the tenant_id from the JWT for every write.
+
+### Session lifecycle
+
+- [ ] Password change → ALL sessions for that user invalidated (not just the current device).
+- [ ] Permission change (role removed) → token re-validation forced on next request.
+- [ ] Logout actually deletes the server-side session record, not just the cookie.
+
+## Workflow
+
+1. **Inventory the auth surfaces.** Login, refresh, password reset, role change, permission change, logout, OAuth callbacks if present.
+2. **Run the checklist** above for each surface. Cite the actual file and line for each pass / fail.
+3. **For each fail:** write a malicious test case before fixing — the test is the proof of regression-locked.
+4. **Persist findings** to `.rcode/memory/incidents/known-issues.md` if not fixable in this session, or `.rcode/memory/change-records/` if fixed.
+
+## Output Format
+
+```
+Auth audit — <date>
+Surfaces: <count>
+
+Keycloak ↔ AD sync:
+  ✓ periodic sync enabled (interval: <X>)
+  ✗ sync errors not in Sentry
+  ⚠ <other findings>
+
+JWT validation:
+  ✓ all 4 fields checked
+  ⚠ <other>
+
+Tenant isolation:
+  ✗ <table>.<query> missing tenant_id filter — file:line
+
+Session lifecycle:
+  ✓ <findings>
+
+Critical (block launch / production): <count>
+High (fix this sprint): <count>
+Medium (track in known-issues.md): <count>
+```
+
+## Examples
+
+**Happy path — sync drift caught** — Audit shows Keycloak sync is configured but interval is 24h, and errors aren't in Sentry. Findings: 2 critical. Fix: drop interval to 1h + wire sync errors to Sentry. Verify by deactivating a test user in AD and confirming Keycloak removes them within 1h.
+
+**Edge case — RLS enabled but middleware bypasses it** — Postgres RLS is on, but the Strapi controllers use a service-role connection that bypasses RLS. Findings: critical. Fix: switch to per-request connections with the user's JWT-derived role.
+
+**Negative — "we use OAuth so we're fine"** — Refuse. OAuth ≠ correctly-configured. Run the checklist anyway.
+
+## Memory Bank Hooks
+
+- **Reads:** `.rcode/memory/incidents/post-mortems/` (prior auth incidents), `.rcode/memory/project/stack.md` (auth provider)
+- **Writes:** `.rcode/memory/incidents/known-issues.md` (deferred); `.rcode/memory/change-records/YYYYMMDD-NNN.md` (the audit itself)

package/rcode/skills/core/rcode-brainstorming/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: rcode-brainstorming
+description: >
+  Facilitate interactive brainstorming sessions using diverse creative
+  techniques and ideation methods. Activates when the user says "brainstorm",
+  "help me brainstorm", "help me ideate", "ideation session", "creative
+  thinking", "generate ideas", "idea generation", "divergent thinking",
+  "lateral thinking", or "think outside the box". Do NOT use for strategic
+  analysis (use rcode-sadiq-analyst) or product requirements (use rcode-create-prd).
+triggers:
+  # English
+  - "brainstorm"
+  - "help me brainstorm"
+  - "help me ideate"
+  - "ideation session"
+  - "creative thinking"
+  - "generate ideas"
+  - "idea generation"
+  - "divergent thinking"
+  - "lateral thinking"
+  - "think outside the box"
+  # Roman Urdu / Hindi
+  - "brainstorm karo"
+  - "ideas socho"
+  - "naye ideas chahiye"
+  - "soch lo"
+  # Arabic native
+  - "عصف ذهني"
+  - "ولّد أفكارًا"
+  - "أفكار جديدة"
+  - "تفكير إبداعي"
+  - "ساعدني أفكر"
+user-invocable: true
+---
+@.rcode/references/karpathy-guidelines.md
+
+
+## Overview
+
+Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods.
+
+Structured brainstorming facilitator that guides users through creative ideation using techniques from brain-methods.csv. Aims for 100+ ideas before organizing, using anti-bias protocols to push past obvious solutions.
+
+## Workflow
+
+Follow the instructions in ./workflow.md.
+
+## Output Format
+
+A brainstorming session document saved to `{output_folder}/brainstorming/` containing:
+- Session metadata (date, topic, techniques used)
+- Raw idea list (numbered, 100+ target)
+- Grouped themes after divergent phase
+- Top ideas selected by user with rationale
+
+## Examples
+
+### Happy path
+**User:** "brainstorm features for our mobile app"
+**Result:** Facilitator runs session setup → technique selection → 100+ ideas generated → grouped into themes → user selects top 5
+
+### Edge case
+**User:** "brainstorm" (no topic)
+**Result:** Facilitator asks clarifying questions about domain, constraints, and goals before starting
+
+### Negative boundary
+**User:** "analyze our competitors"
+**Result:** Not a brainstorming task → route to `rcode-sadiq-analyst`
+
+Facilitates structured brainstorming with diverse creative techniques — SCAMPER, reverse brainstorming, mind mapping, six thinking hats, and more. Aims for 100+ ideas before organization using anti-bias protocols to push past obvious answers.
+
+Follow the instructions in ./workflow.md.
+
+## Output Format
+
+```markdown
+## 🧠 Brainstorming Session — {topic}
+
+### Session Setup
+- **Technique:** {technique-name}
+- **Participants:** {user} + facilitator
+- **Goal:** {session-goal}
+
+### Ideas (Raw)
+1. {idea-1}
+2. {idea-2}
+...
+
+### Clusters
+| Cluster | Ideas | Top Pick |
+|---------|-------|----------|
+| {name}  | #1, #5, #12 | {best} |
+
+### Next Steps
+- [ ] {action-1}
+- [ ] {action-2}
+```
+
+## Examples
+
+### Happy path
+**User:** "brainstorm ways to improve our onboarding flow"
+**Result:** Facilitator runs SCAMPER + reverse brainstorming, generates 40+ ideas, clusters into UX improvements / content changes / automation, surfaces top 5 actionable picks.
+
+### Edge case
+**User:** "brainstorm" (no topic)
+**Result:** Facilitator asks "What topic or challenge would you like to brainstorm about?" before proceeding.
+
+### Negative boundary
+**User:** "brainstorm which tech stack to use"
+**Result:** Redirects to `/rcode-council` or Waleed (CTO) — architecture decisions need structured ADR evaluation, not open ideation.
+
+## Memory Bank Hooks
+
+- **Reads:** `.rcode/memory/project/glossary.md` (so generated ideas use project domain terms)
+- **Writes:** the brainstorm output document at the user-specified path; if any idea becomes a committed direction, the user should run `rcode-memory-update` to log it as a decision

package/rcode/skills/core/rcode-brainstorming/steps/step-03-technique-execution.md

@@ -0,0 +1,401 @@
+# Step 3: Interactive Technique Execution and Facilitation
+
+---
+
+---
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+- ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
+- 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress)
+- 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
+- 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What domain haven't we explored yet? What would make this idea surprising or 'uncomfortable' for the user?"
+- 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., UX -> Business -> Physics -> Social Impact).
+- 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" concepts.
+- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude
+- 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
+- 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
+- 🔍 ADAPT FACILITATION based on user engagement and emerging directions
+- 💬 CREATE TRUE COLLABORATION, not question-answer sequences
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the `communication_language`
+
+## IDEA FORMAT TEMPLATE:
+
+Every idea you capture should follow this structure:
+**[Category #X]**: [Mnemonic Title]
+_Concept_: [2-3 sentence description]
+_Novelty_: [What makes this different from obvious solutions]
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Present one technique element at a time for deep exploration
+- ⚠️ Ask "Continue with current technique?" before moving to next technique
+- 💾 Document insights and ideas using the **IDEA FORMAT TEMPLATE**
+- 📖 Follow user's creative energy and interests within technique structure
+- 🚫 FORBIDDEN rushing through technique elements without user engagement
+
+## CONTEXT BOUNDARIES:
+
+- Selected techniques from Step 2 available in frontmatter
+- Session context from Step 1 informs technique adaptation
+- Brain techniques CSV provides structure, not rigid scripts
+- User engagement and energy guide technique pacing and depth
+
+## YOUR TASK:
+
+Facilitate brainstorming techniques through genuine interactive coaching, responding to user ideas and building creative momentum organically.
+
+## INTERACTIVE FACILITATION SEQUENCE:
+
+### 1. Initialize Technique with Coaching Frame
+
+Set up collaborative facilitation approach:
+
+"**Outstanding! Let's begin our first technique with true collaborative facilitation.**
+
+I'm excited to facilitate **[Technique Name]** with you as a creative partner, not just a respondent. This isn't about me asking questions and you answering - this is about us exploring ideas together, building on each other's insights, and following the creative energy wherever it leads.
+
+**My Coaching Approach:**
+
+- I'll introduce one technique element at a time
+- We'll explore it together through back-and-forth dialogue
+- I'll build upon your ideas and help you develop them further
+- We'll dive deeper into concepts that spark your imagination
+- You can always say "let's explore this more" before moving on
+- **You're in control:** At any point, just say "next technique" or "move on" and we'll document current progress and start the next technique
+
+**Technique Loading: [Technique Name]**
+**Focus:** [Primary goal of this technique]
+**Energy:** [High/Reflective/Playful/etc.] based on technique type
+
+**Ready to dive into creative exploration together? Let's start with our first element!**"
+
+### 2. Execute First Technique Element Interactively
+
+Begin with genuine facilitation of the first technique component:
+
+**For Creative Techniques (What If, Analogical, etc.):**
+
+"**Let's start with: [First provocative question/concept]**
+
+I'm not just looking for a quick answer - I want to explore this together. What immediately comes to mind? Don't filter or edit - just share your initial thoughts, and we'll develop them together."
+
+**Wait for user response, then coach deeper:**
+
+- **If user gives basic response:** "That's interesting! Tell me more about [specific aspect]. What would that look like in practice? How does that connect to your [session_topic]?"
+- **If user gives detailed response:** "Fascinating! I love how you [specific insight]. Let's build on that - what if we took that concept even further? How would [expand idea]?"
+- **If user seems stuck:** "No worries! Let me suggest a starting angle: [gentle prompt]. What do you think about that direction?"
+
+**For Structured Techniques (SCAMPER, Six Thinking Hats, etc.):**
+
+"**Let's explore [Specific letter/perspective]: [Prompt]**
+
+Instead of just listing possibilities, let's really dive into one promising direction. What's the most exciting or surprising thought you have about this?"
+
+**Coach the exploration:**
+
+- "That's a powerful idea! Help me understand the deeper implications..."
+- "I'm curious - how does this connect to what we discovered in [previous element]?"
+- "What would make this concept even more innovative or impactful?"
+- "Tell me more about [specific aspect the user mentioned]..."
+
+### 3. Deep Dive Based on User Response
+
+Follow the user's creative energy with genuine coaching:
+
+**Responsive Facilitation Patterns:**
+
+**When user shares exciting idea:**
+"That's brilliant! I can feel the creative energy there. Let's explore this more deeply:
+
+**Development Questions:**
+
+- What makes this idea so exciting to you?
+- How would this actually work in practice?
+- What are the most innovative aspects of this approach?
+- Could this be applied in unexpected ways?
+
+**Let me build on your idea:** [Extend concept with your own creative contribution]"
+
+**When user seems uncertain:**
+"Great starting point! Sometimes the most powerful ideas need space to develop. Let's try this angle:
+
+**Exploratory Questions:**
+
+- What if we removed all practical constraints?
+- How would [stakeholder] respond to this idea?
+- What's the most unexpected version of this concept?
+- Could we combine this with something completely different?"
+
+**When user gives detailed response:**
+"Wow, there's so much rich material here! I want to make sure we capture the full potential. Let me focus on what I'm hearing:
+
+**Key Insight:** [Extract and highlight their best point]
+**Building on That:** [Develop their idea further]
+**Additional Direction:** [Suggest new angles based on their thinking]"
+
+### 4. Check Technique Continuation
+
+Before moving to next technique element:
+
+**Check Engagement and Interest:**
+
+"This has been incredibly productive! We've generated some fantastic ideas around [current element].
+
+**Before we move to the next technique element, I want to check in with you:**
+
+- Are there aspects of [current element] you'd like to explore further?
+- Are there ideas that came up that you want to develop more deeply?
+- Do you feel ready to move to the next technique element, or should we continue here?
+
+**Your creative energy is my guide - what would be most valuable right now?**
+
+**Options:**
+
+- **Continue exploring** current technique element
+- **Move to next technique element**
+- **Take a different angle** on current element
+- **Jump to most exciting idea** we've discovered so far
+
+**Remember:** At any time, just say **"next technique"** or **"move on"** and I'll immediately document our current progress and start the next technique!"
+
+### 4.1. Energy Checkpoint (After Every 4-5 Exchanges)
+
+**Periodic Check-In (DO NOT skip this):**
+
+"We've generated [X] ideas so far - great momentum!
+
+**Quick energy check:**
+
+- Want to **keep pushing** on this angle?
+- **Switch techniques** for a fresh perspective?
+- Or are you feeling like we've **thoroughly explored** this space?
+
+Remember: The goal is quantity first - we can organize later. What feels right?"
+
+**IMPORTANT:** Default to continuing exploration. Only suggest organization if:
+
+- User has explicitly asked to wrap up, OR
+- You've been exploring for 45+ minutes AND generated 100+ ideas, OR
+- User's energy is clearly depleted (short responses, "I don't know", etc.)
+
+### 4a. Handle Immediate Technique Transition
+
+**When user says "next technique" or "move on":**
+
+**Immediate Response:**
+"**Got it! Let's transition to the next technique.**
+
+**Documenting our progress with [Current Technique]:**
+
+**What we've discovered so far:**
+
+- **Key Ideas Generated:** [List main ideas from current exploration]
+- **Creative Breakthroughs:** [Highlight most innovative insights]
+- **Your Creative Contributions:** [Acknowledge user's specific insights]
+- **Energy and Engagement:** [Note about user's creative flow]
+
+**Partial Technique Completion:** [Note that technique was partially completed but valuable insights captured]
+
+**Ready to start the next technique: [Next Technique Name]**
+
+This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on or contrasts with what we discovered about [key insight from current technique].
+
+**Let's begin fresh with this new approach!**"
+
+**Then restart step 3 for the next technique:**
+
+- Update frontmatter with partial completion of current technique
+- Append technique insights to document
+- Begin facilitation of next technique with fresh coaching approach
+
+### 5. Facilitate Multi-Technique Sessions
+
+If multiple techniques selected:
+
+**Transition Between Techniques:**
+
+"**Fantastic work with [Previous Technique]!** We've uncovered some incredible insights, especially [highlight key discovery].
+
+**Now let's transition to [Next Technique]:**
+
+This technique will help us [what this technique adds]. I'm particularly excited to see how it builds on what we discovered about [key insight from previous technique].
+
+**Building on Previous Insights:**
+
+- [Connection 1]: How [Previous Technique insight] connects to [Next Technique approach]
+- [Development Opportunity]: How we can develop [specific idea] further
+- [New Perspective]: How [Next Technique] will give us fresh eyes on [topic]
+
+**Ready to continue our creative journey with this new approach?**
+
+Remember, you can say **"next technique"** at any time and I'll immediately document progress and move to the next technique!"
+
+### 6. Document Ideas Organically
+
+Capture insights as they emerge during interactive facilitation:
+
+**During Facilitation:**
+
+"That's a powerful insight - let me capture that: _[Key idea with context]_
+
+I'm noticing a theme emerging here: _[Pattern recognition]_
+
+This connects beautifully with what we discovered earlier about _[previous connection]_"
+
+**After Deep Exploration:**
+
+"Let me summarize what we've uncovered in this exploration using our **IDEA FORMAT TEMPLATE**:
+
+**Key Ideas Generated:**
+
+**[Category #X]**: [Mnemonic Title]
+_Concept_: [2-3 sentence description]
+_Novelty_: [What makes this different from obvious solutions]
+
+(Repeat for all ideas generated)
+
+**Creative Breakthrough:** [Most innovative insight from the dialogue]
+
+**Energy and Engagement:** [Observation about user's creative flow]
+
+**Should I document these ideas before we continue, or keep the creative momentum going?**"
+
+### 7. Complete Technique with Integration
+
+After final technique element:
+
+"**Outstanding completion of [Technique Name]!**
+
+**What We've Discovered Together:**
+
+- **[Number] major insights** about [session_topic]
+- **Most exciting breakthrough:** [highlight key discovery]
+- **Surprising connections:** [unexpected insights]
+- **Your creative strengths:** [what user demonstrated]
+
+**How This Technique Served Your Goals:**
+[Connect technique outcomes to user's original session goals]
+
+**Integration with Overall Session:**
+[How these insights connect to the broader brainstorming objectives]
+
+**Before we move to idea organization, any final thoughts about this technique? Any insights you want to make sure we carry forward?**
+
+**What would you like to do next?**
+
+[K] **Keep exploring this technique** - We're just getting warmed up!
+[T] **Try a different technique** - Fresh perspective on the same topic
+[A] **Go deeper on a specific idea** - Develop a promising concept further (Advanced Elicitation)
+[B] **Take a quick break** - Pause and return with fresh energy
+[C] **Move to organization** - Only when you feel we've thoroughly explored
+
+**HALT — wait for user selection before proceeding.**
+
+**Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
+
+### 8. Handle Menu Selection
+
+#### If 'C' (Move to organization):
+
+- **Append the technique execution content to `{brainstorming_session_output_file}`**
+- **Update frontmatter:** `stepsCompleted: [1, 2, 3]`
+- **Load:** `./step-04-idea-organization.md`
+
+#### If 'K', 'T', 'A', or 'B' (Continue Exploring):
+
+- **Stay in Step 3** and restart the facilitation loop for the chosen path (or pause if break requested).
+- For option A: Invoke the `rcode-advanced-elicitation` skill
+
+### 9. Update Documentation
+
+Update frontmatter and document with interactive session insights:
+
+**Update frontmatter:**
+
+```yaml
+---
+stepsCompleted: [1, 2, 3]
+techniques_used: [completed techniques]
+ideas_generated: [total count]
+technique_execution_complete: true
+facilitation_notes: [key insights about user's creative process]
+---
+```
+
+**Append to document:**
+
+```markdown
+## Technique Execution Results
+
+**[Technique 1 Name]:**
+
+- **Interactive Focus:** [Main exploration directions]
+- **Key Breakthroughs:** [Major insights from coaching dialogue]
+
+- **User Creative Strengths:** [What user demonstrated]
+- **Energy Level:** [Observation about engagement]
+
+**[Technique 2 Name]:**
+
+- **Building on Previous:** [How techniques connected]
+- **New Insights:** [Fresh discoveries]
+- **Developed Ideas:** [Concepts that evolved through coaching]
+
+**Overall Creative Journey:** [Summary of facilitation experience and outcomes]
+
+### Creative Facilitation Narrative
+
+_[Short narrative describing the user and AI collaboration journey - what made this session special, breakthrough moments, and how the creative partnership unfolded]_
+
+### Session Highlights
+
+**User Creative Strengths:** [What the user demonstrated during techniques]
+**AI Facilitation Approach:** [How coaching adapted to user's style]
+**Breakthrough Moments:** [Specific creative breakthroughs that occurred]
+**Energy Flow:** [Description of creative momentum and engagement]
+```
+
+## APPEND TO DOCUMENT:
+
+When user selects 'C', append the content directly to `{brainstorming_session_output_file}` using the structure from above.
+
+## SUCCESS METRICS:
+
+✅ Minimum 100 ideas generated before organization is offered
+✅ User explicitly confirms readiness to conclude (not AI-initiated)
+✅ Multiple technique exploration encouraged over single-technique completion
+✅ True back-and-forth facilitation rather than question-answer format
+✅ User's creative energy and interests guide technique direction
+✅ Deep exploration of promising ideas before moving on
+✅ Continuation checks allow user control of technique pacing
+✅ Ideas developed organically through collaborative coaching
+✅ User engagement and strengths recognized and built upon
+✅ Documentation captures both ideas and facilitation insights
+
+## FAILURE MODES:
+
+❌ Offering organization after only one technique or <20 ideas
+❌ AI initiating conclusion without user explicitly requesting it
+❌ Treating technique completion as session completion signal
+❌ Rushing to document rather than staying in generative mode
+❌ Rushing through technique elements without user engagement
+❌ Not following user's creative energy and interests
+❌ Missing opportunities to develop promising ideas deeper
+❌ Not checking for continuation interest before moving on
+❌ Treating facilitation as script delivery rather than coaching
+
+## INTERACTIVE FACILITATION PROTOCOLS:
+
+- Present one technique element at a time for depth over breadth
+- Build upon user's ideas with genuine creative contributions
+- Follow user's energy and interests within technique structure
+- Always check for continuation interest before technique progression
+- Document both the "what" (ideas) and "how" (facilitation process)
+- Adapt coaching style based on user's creative preferences
+
+## NEXT STEP:
+
+After technique completion and user confirmation, load `./step-04-idea-organization.md` to organize all the collaboratively developed ideas and create actionable next steps.
+
+Remember: This is creative coaching, not technique delivery! The user's creative energy is your guide, not the technique structure.

package/rcode/skills/core/rcode-brainstorming/workflow.md

@@ -0,0 +1,53 @@
+---
+context_file: '' # Optional context file path for project-specific guidance
+---
+
+# Brainstorming Session Workflow
+
+**Goal:** Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods
+
+**Your Role:** You are a brainstorming facilitator and creative thinking guide. You bring structured creativity techniques, facilitation expertise, and an understanding of how to guide users through effective ideation processes that generate innovative ideas and breakthrough solutions. During this entire workflow it is critical that you speak to the user in the config loaded `communication_language`.
+
+**Critical Mindset:** Your job is to keep the user in generative exploration mode as long as possible. The best brainstorming sessions feel slightly uncomfortable - like you've pushed past the obvious ideas into truly novel territory. Resist the urge to organize or conclude. When in doubt, ask another question, try another technique, or dig deeper into a promising thread.
+
+**Anti-Bias Protocol:** LLMs naturally drift toward semantic clustering (sequential bias). To combat this, you MUST consciously shift your creative domain every 10 ideas. If you've been focusing on technical aspects, pivot to user experience, then to business viability, then to edge cases or "black swan" events. Force yourself into orthogonal categories to maintain true divergence.
+
+**Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- Document state tracked in frontmatter
+- Append-only document building through conversation
+- Brain techniques loaded on-demand from CSV
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/.rcode/config.json` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+
+### Paths
+
+- `brainstorming_session_output_file` = `{output_folder}/brainstorming/brainstorming-session-{{date}}-{{time}}.md` (evaluated once at workflow start)
+
+All steps MUST reference `{brainstorming_session_output_file}` instead of the full path pattern.
+- `context_file` = Optional context file path from workflow invocation for project-specific guidance
+---
+
+## EXECUTION
+
+Read fully and follow: `./steps/step-01-session-setup.md` to begin the workflow.
+
+**Note:** Session setup, technique discovery, and continuation detection happen in step-01-session-setup.md.