mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-01-30 04:32:02 +00:00
* feat: add link auditor tools and fix broken docs links - Add audit-doc-links.js to scan docs for broken links with auto-resolution - Add fix-doc-links.js to apply suggested fixes (dry-run by default) - Remove stale "Back to Core Concepts" breadcrumb links - Update BMad acronym to "Breakthrough Method of Agile AI Driven Development" - Update README links to docs.bmad-method.org - Simplify upgrade callout in getting-started tutorial Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: reorganize docs structure and archive v4 tutorial - Remove unused section index files (tutorials, how-to, explanation, reference) - Move getting-started-bmadv4.md to _archive - Update quick-start-bmgd.md to remove archived file reference - Update upgrade-to-v6.md - Update astro.config.mjs for new structure Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: ignore underscore directories in link checker Update check-doc-links.js to skip _archive, _planning, and other underscore-prefixed directories when validating links. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: add v4 users section to README Add links to v4 documentation archive and upgrade guide for users migrating from previous versions. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: convert docs to site-relative links and add validation tools - Convert all relative links (./ ../) to site-relative paths (/path/) - Strip .md extensions and use trailing slashes for Astro/Starlight - Add fix-doc-links.js to convert relative links to site-relative - Add validate-doc-links.js to check links point to existing files - Remove old audit-doc-links.js and check-doc-links.js - Update build-docs.js to use new validation script - Add npm scripts: docs:fix-links, docs:validate-links - Update style guide with validation steps Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: standardize acronym to BMad across documentation Replace incorrect "BMAD" with correct "BMad" in text and frontmatter while preserving "BMAD-METHOD" in GitHub URLs. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: fix BMad acronym and remove draft README - Correct acronym to "Breakthrough Method of Agile AI Driven Development" - Remove unused README-draft.md Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: standardize BMad acronym in README Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: standardize FAQ format across all FAQ pages - Add TOC with jump links under "## Questions" - Use ### headers for questions (no Q: prefix) - Direct answers without **A:** prefix - Remove horizontal rules and "Related Documentation" sections - End each FAQ with issue/Discord CTA - Update style guide with new FAQ guidelines - Delete redundant faq/index.md (sidebar handles navigation) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: use repo-relative links with .md for GitHub compatibility Convert all documentation links to repo-relative format (/docs/path/file.md) so they work when browsing on GitHub. The rehype plugin strips /docs/ prefix and converts .md to trailing slash at build time for Astro/Starlight. - Update rehype-markdown-links.js to strip /docs/ prefix from absolute paths - Update fix-doc-links.js to generate /docs/ prefixed paths with .md extension - Convert 217 links across 64 files to new format Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: handle /docs/ prefix in link validator Update resolveLink to strip /docs/ prefix from repo-relative links before checking if files exist. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: restore FAQ index page Re-add the FAQ index page that was accidentally deleted, with updated repo-relative link format. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com> Co-authored-by: Alex Verkhovsky <alexey.verkhovsky@gmail.com>
2.7 KiB
2.7 KiB
title, description
| title | description |
|---|---|
| Creative Intelligence Suite (CIS) | AI-powered creative facilitation with the Creative Intelligence Suite |
AI-powered creative facilitation transforming strategic thinking through expert coaching across five specialized domains.
Core Capabilities
CIS provides structured creative methodologies through distinctive agent personas who act as master facilitators, drawing out insights through strategic questioning rather than generating solutions directly.
Specialized Agents
- Carson - Brainstorming Specialist (energetic facilitator)
- Maya - Design Thinking Maestro (jazz-like improviser)
- Dr. Quinn - Problem Solver (detective-scientist hybrid)
- Victor - Innovation Oracle (bold strategic precision)
- Sophia - Master Storyteller (whimsical narrator)
Interactive Workflows
5 Workflows with 150+ Creative Techniques:
Brainstorming
36 techniques across 7 categories for ideation:
- Divergent/convergent thinking
- Lateral connections
- Forced associations
Design Thinking
Complete 5-phase human-centered process:
- Empathize → Define → Ideate → Prototype → Test
- User journey mapping
- Rapid iteration
Problem Solving
Systematic root cause analysis:
- 5 Whys, Fishbone diagrams
- Solution generation
- Impact assessment
Innovation Strategy
Business model disruption:
- Blue Ocean Strategy
- Jobs-to-be-Done
- Disruptive innovation patterns
Storytelling
25 narrative frameworks:
- Hero's Journey
- Story circles
- Compelling pitch structures
Quick Start
Direct Workflow
workflow brainstorming
workflow design-thinking --data /path/to/context.md
Agent-Facilitated
agent cis/brainstorming-coach
> *brainstorm
Key Differentiators
- Facilitation Over Generation - Guides discovery through questions
- Energy-Aware Sessions - Adapts to engagement levels
- Context Integration - Domain-specific guidance support
- Persona-Driven - Unique communication styles
- Rich Method Libraries - 150+ proven techniques
Integration Points
CIS workflows integrate with:
- BMM - Powers project brainstorming
- BMB - Creative module design
- Custom Modules - Shared creative resource
Best Practices
- Set clear objectives before starting sessions
- Provide context documents for domain relevance
- Trust the process - Let facilitation guide you
- Take breaks when energy flags
- Document insights as they emerge
Related
- Facilitation Over Generation - Core philosophy
- Brainstorming Techniques - Technique reference