mother-brain 0.0.4

package/.github/skills/mother-brain/examples/input-01.md

@@ -0,0 +1,51 @@
+# Example Input: Music Marketing SaaS Platform
+
+**User Statement**: "I want to build a music marketing SaaS platform"
+
+## Vision Discovery Wizard Interaction
+
+**Question 1**: What pain point or opportunity are you addressing?
+> User: "Independent artists struggle to market their music effectively. They don't have the budget for marketing agencies, and existing tools are either too expensive or too complicated. I want to make professional music marketing accessible to everyone."
+
+**Question 2**: Imagine this project succeeds—what does that look like in 3-12 months?
+> User: "In 12 months, 1,000 independent artists are using the platform monthly to run their marketing campaigns. They're seeing measurable increases in streams and followers. The platform handles Spotify playlist pitching, social media scheduling, and email campaigns all in one place."
+
+**Question 3**: Who will benefit from this? Describe them.
+> User: "Independent artists and small labels. Ages 18-35, tech-savvy but not developers. They're releasing music regularly but don't have time or knowledge for marketing."
+
+**Question 4**: Why is this important? What changes if you DON'T build this?
+> User: "Great music goes unheard. Artists give up because they can't get traction. The music industry stays dominated by those who can afford expensive marketing."
+
+**Question 5**: How will you know this project succeeded?
+> User: "User metrics: 1,000 active users, 50% retention rate. Business metrics: Artists see 20%+ increase in streams. Personal metric: Artists telling me this changed their career."
+
+**Question 6**: What's your timeline?
+> User: "6 months to MVP, 12 months to 1,000 users, ongoing after that"
+
+**Question 7**: What limitations exist?
+> User: "Budget: $5k for initial hosting/APIs. Skills: I can code backend/frontend but need to learn Spotify API. Time: 20 hours/week."
+
+**Question 8**: What's the minimum that proves this works?
+> User: "MVP: Connect Spotify account, submit track to 5 curated playlists, see submission status. If 10 artists use it and get one playlist placement, that proves it works."
+
+## Mother Brain's Analysis
+
+**Strategic Themes Identified:**
+1. Artist Empowerment
+2. Marketing Simplification
+3. Platform Integration
+4. Data-Driven Insights
+
+**Repetitive Patterns Detected:**
+- Spotify API calls (authentication, track lookup, playlist data)
+- Image uploads (album art, artist photos)
+- Email campaigns (welcome, updates, results)
+- User authentication (signup, login, sessions)
+- Payment processing (subscription management)
+
+**Skills to Create:**
+- spotify-api-integrator
+- image-upload-handler
+- email-campaign-builder
+- auth-manager
+- subscription-manager (future)

package/.github/skills/mother-brain/examples/menu-examples.md

@@ -0,0 +1,119 @@
+# Mother Brain - Welcome Menu Example
+
+## Scenario: Returning to Existing Project
+
+### User invokes mother-brain
+
+**Mother Brain displays:**
+
+```
+    ___________________
+   /                   \
+  /  ╔═══════════════╗  \
+ |   ║  M O T H E R  ║   |
+ |   ║   B R A I N   ║   |
+  \  ╚═══════════════╝  /
+   \___________________/
+       ||         ||
+      //\\       //\\
+     //  \\     //  \\
+    //====\\   //====\\
+   
+   👽 Vision-Driven Development 👽
+
+🧠 Welcome back to Gaming Backlog Manager!
+
+📍 Where You Left Off:
+• Phase: Phase 1 - Core PWA Foundation
+• Last Task: 003-localstorage-data-layer (DONE)
+• Progress: 3 of 9 tasks completed in this phase
+• Skills Created: 1 skill available (pwa-builder)
+• Last Session: 2026-02-03 at 20:31
+
+What would you like to do?
+```
+
+**Options presented (selectable with numbers or arrow keys):**
+1. Continue where I left off
+2. Start next task
+3. Review/update roadmap
+4. Realign with vision
+5. View all skills
+6. Create new skill
+
+*Freeform input also available*
+
+---
+
+## Scenario: New Project
+
+### User invokes mother-brain for first time
+
+**Mother Brain displays:**
+
+```
+    ___________________
+   /                   \
+  /  ╔═══════════════╗  \
+ |   ║  M O T H E R  ║   |
+ |   ║   B R A I N   ║   |
+  \  ╚═══════════════╝  /
+   \___________________/
+       ||         ||
+      //\\       //\\
+     //  \\     //  \\
+    //====\\   //====\\
+   
+   👽 Vision-Driven Development 👽
+
+🧠 Welcome to Mother Brain!
+
+I'll help you transform your vision into reality by:
+• Discovering your project vision
+• Creating a phased roadmap
+• Identifying needed skills
+• Breaking down tasks
+• Tracking your progress
+
+Ready to begin?
+```
+
+**Options presented:**
+1. Yes, start vision discovery
+2. I have a vision document already (import it)
+3. Show me an example first
+
+*Freeform input also available*
+
+---
+
+## Scenario: After Completing Task
+
+**Mother Brain displays:**
+
+```
+✅ Task 003: localStorage Data Layer - COMPLETE!
+
+What's next?
+```
+
+**Options presented:**
+1. Start next task automatically
+2. Review roadmap and choose task
+3. Take a break (save progress)
+4. Update/refine the roadmap
+
+*Freeform input also available*
+
+---
+
+## User Experience Flow
+
+1. **ASCII art appears** (establishes branding)
+2. **Progress displayed** (user sees where they are)
+3. **Menu with numbered choices** (easy selection)
+4. **User can type number OR use arrow keys OR type custom text**
+5. **Mother Brain executes selected action**
+6. **Cycle repeats after each action**
+
+This creates a consistent, intuitive interface that mirrors skill-creator's UX.

package/.github/skills/mother-brain/examples/output-01.md

@@ -0,0 +1,185 @@
+# Example Output: Music Marketing SaaS Project Structure
+
+## What Mother Brain Created
+
+### Vision Document (`docs/vision.md`)
+```markdown
+# MusicMarketingSaaS - Vision
+
+## The Problem
+Independent artists struggle to market their music effectively without the budget for agencies or access to affordable, simple tools.
+
+## The Vision
+In 12 months: 1,000 independent artists using the platform monthly to run professional marketing campaigns, seeing 20%+ increases in streams and followers.
+
+## Target Users
+Independent artists and small labels (ages 18-35), tech-savvy but not developers, releasing music regularly.
+
+## Why This Matters
+Great music goes unheard. Artists give up due to lack of traction. This democratizes music marketing.
+
+## Success Looks Like
+- User Metrics: 1,000 active users, 50% retention
+- Business Metrics: Artists see 20%+ stream increases
+- Impact: Artists report career-changing results
+
+## Timeline & Constraints
+- 6 months to MVP
+- Budget: $5k for hosting/APIs
+- Time: 20 hours/week
+
+## MVP Definition
+Connect Spotify, submit track to 5 playlists, track status. Success = 10 artists get 1 placement.
+
+## Strategic Themes
+1. Artist Empowerment - Give artists professional tools
+2. Marketing Simplification - One platform, not five
+3. Platform Integration - Spotify, social media, email
+4. Data-Driven Insights - Show what's working
+```
+
+### Roadmap (`docs/roadmap.md`)
+```markdown
+# MusicMarketingSaaS - Roadmap
+
+## Phase 1: Foundation (Weeks 1-3)
+**Goal**: Prove core concept with Spotify playlist submission
+**Strategic Theme**: Platform Integration
+
+**Deliverables**:
+- [ ] Task 001: User authentication system
+- [ ] Task 002: Spotify OAuth integration
+- [ ] Task 003: Playlist database setup
+- [ ] Task 004: Submission form UI
+
+**Skills Available**: auth-manager, spotify-api-integrator
+
+## Phase 2: MVP Features (Weeks 4-8)
+**Goal**: Complete playlist submission workflow
+**Strategic Theme**: Marketing Simplification
+
+**Deliverables**:
+- [ ] Task 005: Curator matching algorithm
+- [ ] Task 006: Submission tracking dashboard
+- [ ] Task 007: Email notifications
+- [ ] Task 008: Artist profile page
+
+**Skills Available**: email-campaign-builder, image-upload-handler
+
+## Phase 3: Beta Launch (Weeks 9-12)
+**Goal**: Get first 10 artists using the platform
+**Strategic Theme**: Artist Empowerment
+
+**Deliverables**:
+- [ ] Task 009: Onboarding flow
+- [ ] Task 010: Analytics dashboard
+- [ ] Task 011: Landing page
+- [ ] Task 012: Beta user feedback system
+
+## MVP Checkpoint (Week 12)
+✅ 10 artists signed up
+✅ At least 50 playlist submissions made
+✅ At least 1 artist got a playlist placement
+✅ System stable and bug-free
+
+## Future Phases (Post-MVP)
+- Social media scheduling
+- Email campaign automation
+- Advanced analytics
+- Subscription tiers
+```
+
+### Skills Created
+
+1. **auth-manager** - User authentication with sessions
+2. **spotify-api-integrator** - OAuth, track lookup, playlist API
+3. **email-campaign-builder** - Welcome emails, notifications
+4. **image-upload-handler** - Album art, profile photos
+
+### First Task Document (`docs/tasks/001-user-authentication.md`)
+```markdown
+# Task 001: User Authentication System
+
+**Status**: 🟡 In Progress
+**Phase**: Phase 1 - Foundation
+**Strategic Theme**: Platform Integration
+**Assigned**: 2026-02-03
+
+## Objective
+Create secure user registration and login system so artists can create accounts and access the platform.
+
+## Success Criteria
+- [ ] Users can sign up with email/password
+- [ ] Users can log in and stay authenticated
+- [ ] Passwords are securely hashed
+- [ ] Session management works correctly
+- [ ] Basic profile page exists
+
+## Approach
+Use auth-manager skill to scaffold authentication system with Express.js and JWT tokens.
+
+## Dependencies
+- None (first task)
+
+## Skills to Use
+- auth-manager (will be created and used)
+
+## Deliverables
+- `/src/auth/` directory with auth routes
+- User model with bcrypt password hashing
+- JWT token generation/validation
+- Login and signup API endpoints
+- Basic profile endpoint
+
+## Notes & Decisions
+[To be filled during execution]
+
+## Validation
+[ ] Auth endpoints built and tested
+[ ] Can create account and log in
+[ ] User confirmed functionality works
+```
+
+### Project Structure
+```
+MusicMarketingSaaS/
+├── docs/
+│   ├── vision.md
+│   ├── roadmap.md
+│   └── tasks/
+│       └── 001-user-authentication.md
+├── .github/
+│   └── skills/
+│       ├── auth-manager/
+│       ├── spotify-api-integrator/
+│       ├── email-campaign-builder/
+│       └── image-upload-handler/
+├── src/
+│   ├── auth/
+│   ├── api/
+│   ├── models/
+│   └── utils/
+├── README.md
+└── package.json
+```
+
+## User Experience Flow
+
+1. **User starts Mother Brain** → Vision discovery wizard (8 questions)
+2. **Mother Brain analyzes** → Identifies 4 core skills needed
+3. **Creates skills** → Invokes skill-creator 4 times
+4. **Generates roadmap** → 3 phases, 12 tasks total
+5. **Starts Task 001** → Uses auth-manager skill
+6. **Validates with user** → "Does this work properly?"
+7. **User confirms** → Task marked complete
+8. **Moves to Task 002** → Continues building...
+
+## Key Features Demonstrated
+
+✅ Vision-driven planning (WHY before HOW)
+✅ Skill identification from patterns
+✅ Phased execution roadmap
+✅ Task documentation with validation
+✅ Best-practice project structure
+✅ Session continuity (can pause/resume)
+✅ User validation at each step

package/.github/skills/mother-brain/references/resources.md

@@ -0,0 +1,147 @@
+# Resources for Mother Brain
+
+## Project Vision & Strategy
+
+### Vision Documents
+- [Strategic Vision Guide - Strategy Institute](https://www.thestrategyinstitute.org/insights/strategic-vision-a-guide-for-developing-a-clear-roadmap-for-your-organization)
+- [Project Vision Best Practices - Leiga](https://www.leiga.com/post/strategic-project-roadmap-planning-for-2026-a-guide-for-leaders)
+
+### Strategic Themes & Outcomes
+- [Outcome-Focused Planning - monday.com](https://monday.com/blog/project-management/project-roadmap/)
+- [Strategic Theme Definition - ProjectManager](https://www.projectmanager.com/blog/tips-for-project-roadmap)
+
+## Roadmap Creation
+
+### Best Practices
+- [How to Create a Project Roadmap - ProjectManager](https://www.projectmanager.com/blog/tips-for-project-roadmap)
+- [Project Roadmap Guide - Office Timeline](https://www.officetimeline.com/roadmaps)
+- [10 Steps to Build a Roadmap - KooperHQ](https://kooperhq.com/blog/project-roadmap)
+
+### Templates & Examples
+- [Roadmap Templates for 2026 - SnackNation](https://snacknation.com/blog/project-roadmap-templates/)
+- [Visual Roadmap Examples - monday.com](https://monday.com/blog/project-management/project-roadmap/)
+
+## Task Management
+
+### Task Documentation
+- [Project Management Plan Guide - Productive](https://productive.io/blog/project-management-plan/)
+- [Task Breakdown Structures - Celoxis](https://www.celoxis.com/article/project-management-guide)
+
+### Prioritization Methods
+- [MoSCoW Method - Digital Project Manager](https://thedigitalprojectmanager.com/project-management/project-roadmap/)
+- [Weighted Scoring for Tasks - Leiga](https://www.leiga.com/post/strategic-project-roadmap-planning-for-2026-a-guide-for-leaders)
+
+## Skill Identification Patterns
+
+### Common Repetitive Patterns
+- **Authentication**: User login, sessions, OAuth
+- **File Uploads**: Images, documents, assets
+- **API Integration**: Third-party services (Spotify, Stripe, etc.)
+- **Email**: Welcome, notifications, campaigns
+- **Payments**: Subscriptions, transactions
+- **Analytics**: Tracking, dashboards, reports
+- **Search**: Full-text, filtering, autocomplete
+- **Real-time**: WebSockets, live updates
+- **Scheduling**: Cron jobs, queues, background tasks
+
+### When to Create a Skill
+- Pattern appears 3+ times in project
+- Has configurable parameters/context
+- Could apply to future projects
+- Requires wizard for context gathering
+- Automates complex setup
+
+## Product Discovery
+
+### Customer Development Questions
+- [The Mom Test - Rob Fitzpatrick](http://momtestbook.com/)
+- [Product Discovery Framework - Teresa Torres](https://www.producttalk.org/)
+- [Jobs to Be Done - Clayton Christensen](https://hbr.org/2016/09/know-your-customers-jobs-to-be-done)
+
+### Problem Validation
+- [Y Combinator Startup School - Problem Validation](https://www.startupschool.org/)
+- [Lean Startup Methodology - Eric Ries](http://theleanstartup.com/)
+
+## MVP Definition
+
+### MVP Best Practices
+- [What is an MVP? - Martin Fowler](https://martinfowler.com/bliki/MinimumViableProduct.html)
+- [MVP vs MMP - ProductPlan](https://www.productplan.com/glossary/minimum-viable-product/)
+- [MVP Anti-Patterns - Mind the Product](https://www.mindtheproduct.com/)
+
+## Agile & Iterative Development
+
+### Methodologies
+- [Agile Manifesto](https://agilemanifesto.org/)
+- [Scrum Guide](https://scrumguides.org/)
+- [Kanban Principles](https://kanbanize.com/kanban-resources/getting-started/what-is-kanban)
+
+### Continuous Delivery
+- [Continuous Integration - Martin Fowler](https://martinfowler.com/articles/continuousIntegration.html)
+- [DevOps Culture - DevOps Handbook](https://www.devopshandbook.com/)
+
+## Project Structure Best Practices
+
+### Standard Conventions
+- [12-Factor App Methodology](https://12factor.net/)
+- [Clean Architecture - Robert C. Martin](https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html)
+- [Monorepo vs Polyrepo - Google Engineering](https://research.google/pubs/why-google-stores-billions-of-lines-of-code-in-a-single-repository/)
+
+### Documentation Standards
+- [Documentation Best Practices - Write the Docs](https://www.writethedocs.org/guide/)
+- [README Templates - GitHub](https://github.com/matiassingers/awesome-readme)
+
+## Feedback & Learning Systems
+
+### Retrospectives
+- [Agile Retrospectives - Esther Derby](https://www.estherderby.com/)
+- [Continuous Improvement - Kaizen Institute](https://www.kaizen.com/)
+
+### User Feedback
+- [Collecting User Feedback - Intercom](https://www.intercom.com/blog/)
+- [User Testing Methods - Nielsen Norman Group](https://www.nngroup.com/)
+
+## Technology Stack Decisions
+
+### Choosing Technologies
+- [Technology Radar - ThoughtWorks](https://www.thoughtworks.com/radar)
+- [State of JavaScript - js.org](https://stateofjs.com/)
+- [Stack Overflow Developer Survey](https://insights.stackoverflow.com/survey)
+
+### Best Practices by Domain
+- **Web Apps**: [web.dev by Google](https://web.dev/)
+- **APIs**: [API Design Best Practices - Microsoft](https://learn.microsoft.com/en-us/azure/architecture/best-practices/api-design)
+- **Databases**: [Database Design - PostgreSQL Wiki](https://wiki.postgresql.org/)
+- **Authentication**: [OAuth 2.0 Best Practices](https://oauth.net/2/)
+
+## Session State Management
+
+### Persistence Patterns
+- [State Management Patterns - Martin Fowler](https://martinfowler.com/)
+- [Stateless vs Stateful - AWS](https://aws.amazon.com/compare/the-difference-between-stateful-and-stateless/)
+
+## Tools & Integrations
+
+### Project Management Tools
+- [Linear](https://linear.app/) - Issue tracking
+- [Notion](https://notion.so/) - Documentation
+- [Miro](https://miro.com/) - Visual planning
+
+### Roadmap Tools
+- [ProductBoard](https://www.productboard.com/)
+- [Aha!](https://www.aha.io/)
+- [Roadmap.sh](https://roadmap.sh/) - Developer roadmaps
+
+## Related Concepts
+
+### Meta-Programming
+- [Domain-Specific Languages - Martin Fowler](https://martinfowler.com/dsl.html)
+- [Code Generation Best Practices](https://www.yegor256.com/2016/11/08/recursion.html)
+
+### AI-Assisted Development
+- [GitHub Copilot Best Practices](https://github.blog/2023-06-20-how-to-write-better-prompts-for-github-copilot/)
+- [AI Pair Programming - OpenAI](https://openai.com/blog/chatgpt-for-programming)
+
+### System Design
+- [System Design Primer - GitHub](https://github.com/donnemartin/system-design-primer)
+- [Designing Data-Intensive Applications - Martin Kleppmann](https://dataintensive.net/)

package/.github/skills/mother-brain/references/tech-stack-guide.md

@@ -0,0 +1,161 @@
+# Technology Stack Decision Guide
+
+## Quick Reference for Common Project Types
+
+### Web Application (Full Stack)
+**Best for**: SaaS products, dashboards, collaborative tools
+
+**Recommended Stack**:
+- Frontend: React + TypeScript + Tailwind CSS
+- Backend: Node.js (Express/Fastify) or Python (FastAPI)
+- Database: PostgreSQL or MongoDB
+- Auth: Auth0, Supabase, or Firebase Auth
+- Hosting: Vercel (frontend) + Railway/Render (backend)
+
+**Why**: Modern, widely supported, strong ecosystem, fast development
+
+---
+
+### Mobile Application
+**Best for**: Consumer apps, on-the-go tools
+
+**Recommended Stack**:
+- Framework: React Native or Flutter
+- Backend: Firebase or Supabase (BaaS)
+- State Management: Redux Toolkit or Riverpod
+- Analytics: Firebase Analytics or Amplitude
+
+**Why**: Write once, deploy iOS + Android, native performance
+
+---
+
+### Desktop Application
+**Best for**: Professional tools, productivity apps, offline-first
+
+**Recommended Stack**:
+- Cross-platform: Electron + React
+- Windows-specific: WinUI 3 + .NET
+- Mac-specific: SwiftUI
+- Linux: Qt or GTK
+
+**Why**: Native feel, full system access, offline capabilities
+
+---
+
+### API / Backend Service
+**Best for**: Microservices, data processing, integrations
+
+**Recommended Stack**:
+- Python: FastAPI (modern, fast, auto-docs)
+- Node.js: Express or Fastify (JavaScript ecosystem)
+- .NET: ASP.NET Core (enterprise, high performance)
+- Go: Gin or Echo (extreme performance)
+
+**Database**:
+- Relational: PostgreSQL
+- Document: MongoDB
+- Key-Value: Redis
+- Time-series: InfluxDB
+
+**Why**: Optimized for specific use case, scales well
+
+---
+
+### Data Science / ML Project
+**Best for**: Analytics, predictions, insights
+
+**Recommended Stack**:
+- Language: Python 3.11+
+- Notebooks: Jupyter Lab
+- Data: Pandas, Polars (faster alternative)
+- Visualization: Plotly, Matplotlib
+- ML: scikit-learn, PyTorch, TensorFlow
+- Deployment: FastAPI + Docker
+
+**Why**: Rich ecosystem, community support, proven tools
+
+---
+
+### Static Website / Blog
+**Best for**: Marketing sites, documentation, blogs
+
+**Recommended Stack**:
+- Framework: Next.js, Gatsby, or Astro
+- CMS: Contentful, Sanity, or MDX
+- Hosting: Vercel, Netlify, or Cloudflare Pages
+- Styling: Tailwind CSS
+
+**Why**: Lightning fast, SEO-friendly, free hosting
+
+---
+
+### E-Commerce
+**Best for**: Online stores, marketplaces
+
+**Recommended Stack**:
+- Platform: Shopify (hosted) or WooCommerce
+- Custom: Next.js + Stripe + Sanity CMS
+- Cart: Snipcart or Commerce.js
+- Payments: Stripe or PayPal
+
+**Why**: Secure payments, inventory management, shipping integrations
+
+---
+
+### Real-Time Application
+**Best for**: Chat apps, collaborative editors, live dashboards
+
+**Recommended Stack**:
+- Frontend: React + Socket.io or WebSockets
+- Backend: Node.js + Socket.io
+- Database: Redis (pub/sub) + PostgreSQL
+- Infrastructure: Heroku or AWS
+
+**Why**: Low latency, bidirectional communication
+
+---
+
+## Decision Matrix
+
+| Priority | Choose... |
+|----------|-----------|
+| Speed to market | No-code (Bubble, Webflow) or BaaS (Firebase, Supabase) |
+| Scalability | Cloud-native (AWS, GCP, Azure) + containerization |
+| Cost-effective | Open source stack + free tiers (Vercel, Render, Supabase) |
+| Enterprise ready | .NET, Java Spring Boot, PostgreSQL |
+| Developer productivity | TypeScript + modern framework + Copilot |
+| Performance critical | Go, Rust, or C++ |
+
+## Technology Evaluation Checklist
+
+When selecting technologies, consider:
+
+✅ **Community Size**: Active community = more resources, packages, help
+✅ **Documentation Quality**: Good docs save days of debugging
+✅ **Long-term Viability**: Is the tech actively maintained?
+✅ **Hiring Pool**: Can you find developers who know it?
+✅ **Learning Curve**: How quickly can team become productive?
+✅ **Ecosystem**: Are there good libraries, tools, integrations?
+✅ **Performance**: Does it meet your scale requirements?
+✅ **Cost**: Licensing, hosting, third-party services
+
+## Red Flags (Avoid These)
+
+❌ **Dead Projects**: Last commit > 2 years ago
+❌ **Single Maintainer**: Bus factor of 1
+❌ **Overly Complex**: Requires PhD to understand
+❌ **Hyped but Immature**: Trendy but production-untested
+❌ **Vendor Lock-in**: Impossible to migrate away
+❌ **Poor Security**: History of vulnerabilities
+
+## When in Doubt...
+
+**For Prototypes**: Use whatever you know best + fastest
+**For MVPs**: Modern, popular stack with good docs
+**For Scale**: Battle-tested, boring technology
+**For Unique Needs**: Research thoroughly, POC first
+
+---
+
+**Last Updated**: 2026-02-03
+**Source**: Aggregate best practices from Stack Overflow Survey, GitHub, ThoughtWorks Radar