Files
BMAD-METHOD/docs/explanation/philosophy/facilitation-over-generation.md
forcetrainer 12d3492e0c Add link auditor, reorganize documentation, and README update (#1277)
* 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>
2026-01-10 02:55:33 +08:00

3.0 KiB

title, description
title description
Facilitation Over Generation Understanding CIS's facilitation-first approach to creative work

The Creative Intelligence Suite (CIS) takes a fundamentally different approach from typical AI tools. Instead of generating solutions directly, CIS agents act as master facilitators who guide you to discover insights yourself.


The Problem with Generation

Traditional AI approaches to creative work:

User: "Give me marketing ideas"
AI: "Here are 10 marketing ideas..."

This approach:

  • Produces generic, predictable outputs
  • Removes human ownership of ideas
  • Misses context and nuance
  • Limits creative exploration

The Facilitation Approach

CIS agents use strategic questioning:

User: "I need marketing ideas"
CIS: "What makes your customers choose you over alternatives?
      What's the one thing they always mention?"
User: "They say our support is exceptional"
CIS: "Interesting! How might you make that exceptional
      support visible before they become customers?"

This approach:

  • Draws out insights already within you
  • Maintains human ownership of ideas
  • Captures context and nuance
  • Enables deeper creative exploration

Key Principles

1. Questions Over Answers

CIS agents ask strategic questions rather than providing direct answers. This:

  • Activates your own creative thinking
  • Uncovers assumptions
  • Reveals blind spots
  • Builds on your domain knowledge

2. Energy-Aware Sessions

CIS monitors engagement and adapts:

  • Adjusts pace when energy flags
  • Suggests breaks when needed
  • Changes techniques to maintain momentum
  • Recognizes productive vs. unproductive struggle

3. Process Trust

CIS uses proven methodologies:

  • Design Thinking's 5 phases
  • Structured brainstorming techniques
  • Root cause analysis frameworks
  • Innovation strategy patterns

You're not just having a conversation—you're following time-tested creative processes.

4. Persona-Driven Engagement

Each CIS agent has a distinct personality:

  • Carson - Energetic, encouraging
  • Maya - Jazz-like, improvisational
  • Dr. Quinn - Analytical, methodical
  • Victor - Bold, strategic
  • Sophia - Narrative, imaginative

These personas create engaging experiences that maintain creative flow.


When Generation is Appropriate

CIS does generate when appropriate:

  • Synthesizing session outputs
  • Documenting decisions
  • Creating structured artifacts
  • Providing technique examples

But the core creative work happens through facilitated discovery.


Benefits

For Individuals

  • Deeper insights than pure generation
  • Ownership of creative outputs
  • Skill development in creative thinking
  • More memorable and actionable ideas

For Teams

  • Shared creative experience
  • Aligned understanding
  • Documented rationale
  • Stronger buy-in to outcomes