bmad-project-context

Topics in the source

• Overview
• Resolution rules
• On Activation
• Setup, Adoption, and Refresh Steps
• 1. Assess and report
• 2. Ask what they bring
• 3. Discover and verify
• 4. Interview the gaps

A conversation that produces a repository's agent instructions: a small verified block inside AGENTS.md. The user brings rules they want followed — governance, security, standards — and the repository supplies the rest, verified. Conversational always; the user approves every write. Args: intent (setup | adopt | refresh | record | audit); a target repo or path; extra source paths or URLs. Bare paths and {skill-root} (e.g. references/best-practices.md) resolve from this skill's installed directory. {project-root} → the project working directory. Target → the repository being described, defaulting to {project-root}. If it resolves to more than one working tree, or to one the user cannot commit in, ask before writing. 1. Resolve customization: node {project-root}/bmad/ade-runtime.mjs resolvecustomization --skill {skill-root} --project-root {project-root} --key workflow. Script not found: BMad is not set up here. Offer to run the bmad skill's setup, installing bmad first if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run the command again. Any other failure: read {skill-root}/customize.toml directly and use defaults. Execute {workflow.activationstep

This is an excerpt. Refer to the complete source and its current requirements.