Compare commits

...

4 Commits

Author SHA1 Message Date
Hisyam d2cb27aa5a
Merge 84a3aa57de into 15f49b8bd4 2026-04-04 08:28:00 +03:00
Brian 15f49b8bd4
docs: add BMad Ecosystem cross-links to sidebar (#2203) 2026-04-04 00:27:47 -05:00
Alex Verkhovsky d51e2159e5
fix(quick-dev): specify {project-root}/ anchor for context: list paths (#2200)
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-03 11:42:31 -07:00
Hisyam 84a3aa57de
docs: add pencil usage guidelines to core-tools #2162
Addresses issue #2162 by adding recommendations for introducing Pencil early in the BMad workflow.
2026-03-30 12:14:20 +07:00
3 changed files with 26 additions and 1 deletions

View File

@ -291,3 +291,14 @@ Run both `bmad-review-adversarial-general` and `bmad-review-edge-case-hunter` to
**Input:** Target folder path **Input:** Target folder path
**Output:** `index.md` with organized file listings, relative links, and brief descriptions **Output:** `index.md` with organized file listings, relative links, and brief descriptions
## 3rd Party Tools Integration: Pencil
If you are using **Pencil** within BMAD workflows for creating mockups or UI designs, it is critical that the LLM is fully aware of its existence early in the process rather than treating it merely as a nice-to-have MCP (Model Context Protocol).
**Important Guidelines for Pencil:**
- **Introduce Early:** The sooner you bring Pencil into your planning process, the better. You must specify Pencil in your tooling **before** generating the `_bmad-output/planning-artifacts/architecture.md` document.
- **Enforce Context:** Explicitly enforce the inclusion of your `.pen` (Pencil) files in the `_bmad-output/project-context.md` file.
- **Why this matters:** If you bring Pencil in after the PRD, UX, and Architecture docs are already drafted without establishing these guardrails, the AI will not integrate it smoothly and will cause avoidable course corrections during sprints.

View File

@ -3,7 +3,7 @@ title: '{title}'
type: 'feature' # feature | bugfix | refactor | chore type: 'feature' # feature | bugfix | refactor | chore
created: '{date}' created: '{date}'
status: 'draft' # draft | ready-for-dev | in-progress | in-review | done status: 'draft' # draft | ready-for-dev | in-progress | in-review | done
context: [] # optional: project-wide standards/docs the implementation agent should load. Keep short — only what isn't already distilled into the spec body. context: [] # optional: `{project-root}/`-prefixed paths to project-wide standards/docs the implementation agent should load. Keep short — only what isn't already distilled into the spec body.
--- ---
<!-- Target: 9001300 tokens. Above 1600 = high risk of context rot. <!-- Target: 9001300 tokens. Above 1600 = high risk of context rot.

View File

@ -119,6 +119,20 @@ export default defineConfig({
autogenerate: { directory: 'reference' }, autogenerate: { directory: 'reference' },
}, },
// TEA docs moved to standalone module site; keep BMM sidebar focused. // TEA docs moved to standalone module site; keep BMM sidebar focused.
{
label: 'BMad Ecosystem',
collapsed: false,
items: [
{ label: 'BMad Builder', link: 'https://bmad-builder-docs.bmad-method.org/', attrs: { target: '_blank' } },
{ label: 'Creative Intelligence Suite', link: 'https://cis-docs.bmad-method.org/', attrs: { target: '_blank' } },
{ label: 'Game Dev Studio', link: 'https://game-dev-studio-docs.bmad-method.org/', attrs: { target: '_blank' } },
{
label: 'Test Architect (TEA)',
link: 'https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/',
attrs: { target: '_blank' },
},
],
},
], ],
// Credits in footer // Credits in footer