Merge branch 'main' into feat/add_iflow_cli_support
This commit is contained in:
commit
18427b46c6
16
README.md
16
README.md
|
|
@ -243,19 +243,3 @@ BMAD™ and BMAD-METHOD™ are trademarks of BMad Code, LLC. All rights reserved
|
||||||
[](https://github.com/bmadcode/bmad-method/graphs/contributors)
|
[](https://github.com/bmadcode/bmad-method/graphs/contributors)
|
||||||
|
|
||||||
<sub>Built with ❤️ for the AI-assisted development community</sub>
|
<sub>Built with ❤️ for the AI-assisted development community</sub>
|
||||||
|
|
||||||
#### Codex (CLI & Web)
|
|
||||||
|
|
||||||
- Two modes are supported:
|
|
||||||
- Codex (local only): `npx bmad-method install -f -i codex -d .` — keeps `.bmad-core/` ignored via `.gitignore` for local development.
|
|
||||||
- Codex Web Enabled: `npx bmad-method install -f -i codex-web -d .` — ensures `.bmad-core/` is tracked (not ignored) so it can be committed for Codex Web.
|
|
||||||
- For Codex Web, commit both `.bmad-core/` and `AGENTS.md` to the repository.
|
|
||||||
- Codex CLI: run `codex` at your project root; reference agents naturally, e.g., “As dev, implement …”.
|
|
||||||
- Codex Web: open your repo in Codex and prompt the same way — it reads `AGENTS.md` automatically.
|
|
||||||
- Refresh after changes: rerun the appropriate install command (`codex` or `codex-web`) to regenerate the BMAD section inside `AGENTS.md`.
|
|
||||||
|
|
||||||
If a `package.json` exists in your project, the installer will add helpful scripts:
|
|
||||||
|
|
||||||
- `bmad:refresh` → `bmad-method install -f -i codex`
|
|
||||||
- `bmad:list` → `bmad-method list:agents`
|
|
||||||
- `bmad:validate` → `bmad-method validate`
|
|
||||||
|
|
|
||||||
|
|
@ -18,7 +18,7 @@ Each expansion pack provides deep, specialized knowledge without bloating the co
|
||||||
|
|
||||||
Anyone can create and share expansion packs, fostering a ecosystem of AI-powered solutions across all industries and interests.
|
Anyone can create and share expansion packs, fostering a ecosystem of AI-powered solutions across all industries and interests.
|
||||||
|
|
||||||
## Technical Expansion Packs
|
## Technical Expansion Packs (Examples of possible expansions to come)
|
||||||
|
|
||||||
### Game Development Pack
|
### Game Development Pack
|
||||||
|
|
||||||
|
|
@ -191,90 +191,10 @@ Research acceleration tools:
|
||||||
|
|
||||||
## Creating Your Own Expansion Pack
|
## Creating Your Own Expansion Pack
|
||||||
|
|
||||||
### Step 1: Define Your Domain
|
The next major release will include a new agent and expansion pack builder and a new expansion format.
|
||||||
|
|
||||||
What expertise are you capturing? What problems will it solve?
|
|
||||||
|
|
||||||
### Step 2: Design Your Agents
|
|
||||||
|
|
||||||
Each agent should have:
|
|
||||||
|
|
||||||
- Clear expertise area
|
|
||||||
- Specific personality traits
|
|
||||||
- Defined capabilities
|
|
||||||
- Knowledge boundaries
|
|
||||||
|
|
||||||
### Step 3: Create Tasks
|
|
||||||
|
|
||||||
Tasks should be:
|
|
||||||
|
|
||||||
- Step-by-step procedures
|
|
||||||
- Reusable across scenarios
|
|
||||||
- Clear and actionable
|
|
||||||
- Domain-specific
|
|
||||||
|
|
||||||
### Step 4: Build Templates
|
|
||||||
|
|
||||||
Templates need:
|
|
||||||
|
|
||||||
- Structured output format
|
|
||||||
- Embedded LLM instructions
|
|
||||||
- Placeholders for customization
|
|
||||||
- Professional formatting
|
|
||||||
|
|
||||||
### Step 5: Test & Iterate
|
|
||||||
|
|
||||||
- Use with real scenarios
|
|
||||||
- Gather user feedback
|
|
||||||
- Refine agent responses
|
|
||||||
- Improve task clarity
|
|
||||||
|
|
||||||
### Step 6: Package & Share
|
|
||||||
|
|
||||||
- Create clear documentation
|
|
||||||
- Include usage examples
|
|
||||||
- Add to expansion-packs directory
|
|
||||||
- Share with community
|
|
||||||
|
|
||||||
## The Future of Expansion Packs
|
|
||||||
|
|
||||||
### Marketplace Potential
|
|
||||||
|
|
||||||
Imagine a future where:
|
|
||||||
|
|
||||||
- Professional expansion packs are sold
|
|
||||||
- Certified packs for regulated industries
|
|
||||||
- Community ratings and reviews
|
|
||||||
- Automatic updates and improvements
|
|
||||||
|
|
||||||
### AI Agent Ecosystems
|
|
||||||
|
|
||||||
Expansion packs could enable:
|
|
||||||
|
|
||||||
- Cross-pack agent collaboration
|
|
||||||
- Industry-standard agent protocols
|
|
||||||
- Interoperable AI workflows
|
|
||||||
- Universal agent languages
|
|
||||||
|
|
||||||
### Democratizing Expertise
|
|
||||||
|
|
||||||
Every expansion pack:
|
|
||||||
|
|
||||||
- Makes expert knowledge accessible
|
|
||||||
- Reduces barriers to entry
|
|
||||||
- Enables solo entrepreneurs
|
|
||||||
- Empowers small teams
|
|
||||||
|
|
||||||
## Getting Started
|
|
||||||
|
|
||||||
1. **Browse existing packs**: Check `expansion-packs/` directory
|
|
||||||
2. **Install what you need**: Use the installer's expansion pack option
|
|
||||||
3. **Create your own**: Use the expansion-creator pack
|
|
||||||
4. **Share with others**: Submit PRs with new packs
|
|
||||||
5. **Build the future**: Help shape AI-assisted work
|
|
||||||
|
|
||||||
## Remember
|
## Remember
|
||||||
|
|
||||||
The BMad Method is more than a development framework - it's a platform for structuring human expertise into AI-accessible formats. Every expansion pack you create makes specialized knowledge more accessible to everyone.
|
The BMad Method is more than a Software Development Agile Framework! Every expansion pack makes specialized knowledge and workflows more accessible to everyone.
|
||||||
|
|
||||||
**What expertise will you share with the world?**
|
**What expertise will you share with the world?**
|
||||||
|
|
|
||||||
|
|
@ -1,12 +1,12 @@
|
||||||
{
|
{
|
||||||
"name": "bmad-method",
|
"name": "bmad-method",
|
||||||
"version": "4.40.1",
|
"version": "4.42.1",
|
||||||
"lockfileVersion": 3,
|
"lockfileVersion": 3,
|
||||||
"requires": true,
|
"requires": true,
|
||||||
"packages": {
|
"packages": {
|
||||||
"": {
|
"": {
|
||||||
"name": "bmad-method",
|
"name": "bmad-method",
|
||||||
"version": "4.40.1",
|
"version": "4.42.1",
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"@kayvan/markdown-tree-parser": "^1.6.1",
|
"@kayvan/markdown-tree-parser": "^1.6.1",
|
||||||
|
|
|
||||||
|
|
@ -1,7 +1,7 @@
|
||||||
{
|
{
|
||||||
"$schema": "https://json.schemastore.org/package.json",
|
"$schema": "https://json.schemastore.org/package.json",
|
||||||
"name": "bmad-method",
|
"name": "bmad-method",
|
||||||
"version": "4.40.1",
|
"version": "4.42.1",
|
||||||
"description": "Breakthrough Method of Agile AI-driven Development",
|
"description": "Breakthrough Method of Agile AI-driven Development",
|
||||||
"keywords": [
|
"keywords": [
|
||||||
"agile",
|
"agile",
|
||||||
|
|
|
||||||
|
|
@ -1,12 +1,12 @@
|
||||||
{
|
{
|
||||||
"name": "bmad-method",
|
"name": "bmad-method",
|
||||||
"version": "4.37.0-beta.4",
|
"version": "4.42.1",
|
||||||
"lockfileVersion": 3,
|
"lockfileVersion": 3,
|
||||||
"requires": true,
|
"requires": true,
|
||||||
"packages": {
|
"packages": {
|
||||||
"": {
|
"": {
|
||||||
"name": "bmad-method",
|
"name": "bmad-method",
|
||||||
"version": "4.37.0-beta.4",
|
"version": "4.42.1",
|
||||||
"license": "MIT",
|
"license": "MIT",
|
||||||
"dependencies": {
|
"dependencies": {
|
||||||
"chalk": "^4.1.2",
|
"chalk": "^4.1.2",
|
||||||
|
|
|
||||||
|
|
@ -1,6 +1,6 @@
|
||||||
{
|
{
|
||||||
"name": "bmad-method",
|
"name": "bmad-method",
|
||||||
"version": "4.39.1",
|
"version": "4.42.1",
|
||||||
"description": "BMad Method installer - AI-powered Agile development framework",
|
"description": "BMad Method installer - AI-powered Agile development framework",
|
||||||
"keywords": [
|
"keywords": [
|
||||||
"bmad",
|
"bmad",
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue