Compare commits
8 Commits
ac56bdec7f
...
5c5e1f0e68
| Author | SHA1 | Date |
|---|---|---|
|
|
5c5e1f0e68 | |
|
|
3a24d8ffc9 | |
|
|
15f49b8bd4 | |
|
|
d51e2159e5 | |
|
|
e9a6bfa95c | |
|
|
adb2506b7f | |
|
|
3be49a5c09 | |
|
|
e6986fe867 |
|
|
@ -3,7 +3,7 @@ title: '{title}'
|
|||
type: 'feature' # feature | bugfix | refactor | chore
|
||||
created: '{date}'
|
||||
status: 'draft' # draft | ready-for-dev | in-progress | in-review | done
|
||||
context: [] # optional: max 3 project-wide standards/docs. NO source code files.
|
||||
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: 900–1300 tokens. Above 1600 = high risk of context rot.
|
||||
|
|
|
|||
|
|
@ -42,6 +42,13 @@ Never ask extra questions if you already understand what the user intends.
|
|||
1. Load context.
|
||||
- List files in `{planning_artifacts}` and `{implementation_artifacts}`.
|
||||
- If you find an unformatted spec or intent file, ingest its contents to form your understanding of the intent.
|
||||
- Planning artifacts are the output of BMAD phases 1-3. Typical files include:
|
||||
- **PRD** (`*prd*`) — product requirements and success criteria
|
||||
- **Architecture** (`*architecture*`) — technical design decisions and constraints
|
||||
- **UX/Design** (`*ux*`) — user experience and interaction design
|
||||
- **Epics** (`*epic*`) — feature breakdown into implementable stories
|
||||
- **Product Brief** (`*brief*`) — project vision and scope
|
||||
- Scan the listing for files matching these patterns. If any look relevant to the current intent, load them selectively — you don't need all of them, but you need the right constraints and requirements rather than guessing from code alone.
|
||||
2. Clarify intent. Do not fantasize, do not leave open questions. If you must ask questions, ask them as a numbered list. When the human replies, verify that every single numbered question was answered. If any were ignored, HALT and re-ask only the missing questions before proceeding. Keep looping until intent is clear enough to implement.
|
||||
3. Version control sanity check. Is the working tree clean? Does the current branch make sense for this intent — considering its name and recent history? If the tree is dirty or the branch is an obvious mismatch, HALT and ask the human before proceeding. If version control is unavailable, skip this check.
|
||||
4. Multi-goal check (see SCOPE STANDARD). If the intent fails the single-goal criteria:
|
||||
|
|
|
|||
|
|
@ -24,6 +24,8 @@ Capture `baseline_commit` (current HEAD, or `NO_VCS` if version control is unava
|
|||
|
||||
Change `{spec_file}` status to `in-progress` in the frontmatter before starting implementation.
|
||||
|
||||
If `{spec_file}` has a non-empty `context:` list in its frontmatter, load those files before implementation begins. When handing to a sub-agent, include them in the sub-agent prompt so it has access to the referenced context.
|
||||
|
||||
Hand `{spec_file}` to a sub-agent/task and let it implement. If no sub-agents are available, implement directly.
|
||||
|
||||
**Path formatting rule:** Any markdown links written into `{spec_file}` must use paths relative to `{spec_file}`'s directory so they are clickable in VS Code. Any file paths displayed in terminal/conversation output must use CWD-relative format with `:line` notation (e.g., `src/path/file.ts:42`) for terminal clickability. No leading `/` in either case.
|
||||
|
|
|
|||
|
|
@ -0,0 +1,65 @@
|
|||
---
|
||||
name: bmad-install-agentvibes
|
||||
description: 'Install AgentVibes TTS voice system for BMAD agents. Gives each agent a unique voice, personality, and audio effects. Use when user wants to add voice/TTS to their BMAD setup, or when bmad-party-mode is active and agents are silent.'
|
||||
---
|
||||
|
||||
# Install AgentVibes
|
||||
|
||||
AgentVibes is an open-source Text-to-Speech system that gives BMAD agents unique voices, personalities, and audio effects. Once installed, party mode agents speak aloud — each with their own voice.
|
||||
|
||||
## What AgentVibes Provides
|
||||
|
||||
- **Per-agent voices** — each BMAD agent gets a distinct voice via `bmad-voice-map.json`
|
||||
- **Cross-platform** — Windows (SAPI + Piper), macOS, Linux, WSL
|
||||
- **Personalities & effects** — reverb, background music, speed, sentiment
|
||||
- **Party mode integration** — agents introduce themselves and speak sequentially
|
||||
|
||||
## Installation
|
||||
|
||||
Run the installer in the terminal:
|
||||
|
||||
```bash
|
||||
npx agentvibes install
|
||||
```
|
||||
|
||||
Or if you prefer a global install first:
|
||||
|
||||
```bash
|
||||
npm install -g agentvibes
|
||||
agentvibes install
|
||||
```
|
||||
|
||||
**The installer will:**
|
||||
1. Detect your platform (Windows/Mac/Linux/WSL)
|
||||
2. Install the appropriate TTS provider (Piper recommended for best quality, SAPI as zero-dependency fallback on Windows)
|
||||
3. Configure Claude Code hooks so agents speak automatically
|
||||
4. Set up `bmad-speak.sh` / `bmad-speak.ps1` integration for party mode
|
||||
|
||||
## Post-Install: Configure Agent Voices
|
||||
|
||||
After installing, configure per-agent voices for party mode:
|
||||
|
||||
```
|
||||
/agent-vibes:bmad
|
||||
```
|
||||
|
||||
This opens the BMAD voice configuration where you can assign each agent a distinct voice, personality, and effects profile.
|
||||
|
||||
## Verify Installation
|
||||
|
||||
```bash
|
||||
agentvibes whoami
|
||||
```
|
||||
|
||||
Should display the active voice and provider. If party mode is active, agents will now speak when you run `/bmad-party-mode`.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
- **Agents still silent after install**: Run `agentvibes install` again — it is idempotent
|
||||
- **Windows users**: Ensure PowerShell execution policy allows scripts: `Set-ExecutionPolicy -Scope CurrentUser RemoteSigned`
|
||||
- **Voice quality**: Install Piper for neural TTS — `agentvibes install` will prompt you
|
||||
|
||||
## More Info
|
||||
|
||||
- GitHub: https://github.com/paulpreibisch/AgentVibes
|
||||
- Docs: `agentvibes --help`
|
||||
|
|
@ -1,6 +1,7 @@
|
|||
module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
|
||||
Core,bmad-brainstorming,Brainstorming,BSP,Use early in ideation or when stuck generating ideas.,,anytime,,,false,{output_folder}/brainstorming,brainstorming session
|
||||
Core,bmad-party-mode,Party Mode,PM,Orchestrate multi-agent discussions when you need multiple perspectives or want agents to collaborate.,,anytime,,,false,,
|
||||
Core,bmad-install-agentvibes,Install AgentVibes,AV,Install AgentVibes TTS so party mode agents speak with unique voices. Run once after BMAD setup.,,anytime,,,false,,
|
||||
Core,bmad-help,BMad Help,BH,,,anytime,,,false,,
|
||||
Core,bmad-index-docs,Index Docs,ID,Use when LLM needs to understand available docs without loading everything.,,anytime,,,false,,
|
||||
Core,bmad-shard-doc,Shard Document,SD,Use when doc becomes too large (>500 lines) to manage effectively.,[path],anytime,,,false,,
|
||||
|
|
|
|||
|
Can't render this file because it has a wrong number of fields in line 2.
|
|
|
@ -1121,7 +1121,58 @@ class Installer {
|
|||
lines.push(` Invoke the ${color.cyan('bmad-help')} skill in your IDE Agent to get started`);
|
||||
}
|
||||
|
||||
// AgentVibes TTS suggestion
|
||||
lines.push(
|
||||
'',
|
||||
` ${color.cyan('🎙 Want your BMAD agents to speak?')}`,
|
||||
` Install AgentVibes TTS: ${color.dim('npx agentvibes install')}`,
|
||||
` Gives each agent a unique voice in party mode and beyond.`,
|
||||
);
|
||||
|
||||
await prompts.note(lines.join('\n'), 'BMAD is ready to use!');
|
||||
|
||||
// Optional AgentVibes install prompt
|
||||
if (!this._silentConfig) {
|
||||
try {
|
||||
const agentVibesChoice = await prompts.select({
|
||||
message: '🎙 Give your BMAD agents a voice? (AgentVibes TTS)',
|
||||
choices: [
|
||||
{
|
||||
name: 'Yes — install AgentVibes now',
|
||||
value: 'install',
|
||||
hint: 'runs npx agentvibes install',
|
||||
},
|
||||
{
|
||||
name: 'No — I\'ll do it later',
|
||||
value: 'skip',
|
||||
hint: 'npx agentvibes install',
|
||||
},
|
||||
{
|
||||
name: 'Tell me more',
|
||||
value: 'info',
|
||||
hint: 'github.com/paulpreibisch/AgentVibes',
|
||||
},
|
||||
],
|
||||
default: 'skip',
|
||||
});
|
||||
|
||||
if (agentVibesChoice === 'install') {
|
||||
const { execSync } = require('node:child_process');
|
||||
await prompts.log.step('Running npx agentvibes install...');
|
||||
execSync('npx agentvibes install', { stdio: 'inherit' });
|
||||
} else if (agentVibesChoice === 'info') {
|
||||
await prompts.log.info(
|
||||
'AgentVibes gives each BMAD agent a unique TTS voice, personality, and audio effects.\n' +
|
||||
' Works on Windows (SAPI + Piper), macOS, Linux, and WSL.\n' +
|
||||
' Party mode agents speak with their own voice — no more silent roundtables.\n\n' +
|
||||
' GitHub: https://github.com/paulpreibisch/AgentVibes\n' +
|
||||
' Install: npx agentvibes install'
|
||||
);
|
||||
}
|
||||
} catch {
|
||||
// Prompt cancelled or AgentVibes install failed — non-fatal
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
|
|
|
|||
|
|
@ -119,6 +119,20 @@ export default defineConfig({
|
|||
autogenerate: { directory: 'reference' },
|
||||
},
|
||||
// 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
|
||||
|
|
|
|||
Loading…
Reference in New Issue