langchain-bmad
Use langchain-bmad when the job is combining BMAD phase discipline with the
LangChain ecosystem, not when the user only needs a single framework skill in
isolation. Keep the entrypoint focused on routing: choose the BMAD phase,
choose the framework lane, then load the narrowest downstream skill or support
file that fits.
When to use this skill
- Start a new agent project and choose between LangChain, LangGraph, and Deep
Agents inside a BMAD workflow
- Route a BMAD artifact or phase gate for a LangChain ecosystem project
- Decide which framework-specific skill should be loaded next after a BMAD
planning or architecture step
- Install the BMAD and LangChain skill sets together for one project
- Keep framework choice, persistence, and HITL decisions aligned with BMAD
phase boundaries
Use a narrower skill instead when:
- the user already knows the exact framework problem and does not need BMAD
phase routing: use
langgraph-fundamentals, deep-agents-core, or the specific
LangChain skill directly
- the user mainly needs BMAD phase routing without framework-specific guidance:
use
bmad
- the user is still shaping the idea before structured delivery: use
bmad-idea
Instructions
Step 1: Classify both dimensions before naming commands
Identify:
- BMAD lane: bootstrap, phase-status, artifact-routing, phase-gate, or
implementation handoff
- Framework lane: LangChain, LangGraph, Deep Agents, or framework-selection
Do not dump every BMAD phase and every LangChain skill in one response before
these two lanes are clear.
Step 2: Choose the BMAD phase and the next framework decision together
Use references/phase-map.md to map the current BMAD phase to the narrowest
next skill:
- Analysis:
framework-selection
- Planning:
langchain-dependencies
- Solutioning:
- LangChain ->
langchain-fundamentals
- LangGraph ->
langgraph-fundamentals plus langgraph-persistence
- Deep Agents ->
deep-agents-core
- Implementation:
- LangChain ->
langchain-middleware, optional langchain-rag
- LangGraph ->
langgraph-human-in-the-loop, langgraph-persistence
- Deep Agents ->
deep-agents-memory, deep-agents-orchestration
If the user has not chosen a framework yet, stop at framework-selection
instead of pretending all three lanes should run.
Step 3: Load only the support file that matches the current gap
Use progressive disclosure:
references/phase-map.md for the BMAD-phase to framework-skill routing table
references/setup-and-handoff.md for install commands, package bundles, and
handoff rules between BMAD and framework skills
Keep the main skill compact instead of leaving the entire phase map, setup
guide, and implementation catalog inline.
Step 4: Preserve BMAD gates while delegating framework detail
Use bmad to keep artifact progression and review gates honest:
- use BMAD to decide which artifact is next
- use the framework skill to shape the technical content of that artifact
- use
plannotator or the existing BMAD review gate before advancing major
phase documents
Do not let framework implementation detail bypass the BMAD artifact gate.
Step 5: Verify that the route is specific and minimal
Before claiming success, prove that:
- the chosen BMAD phase matches the user's immediate job
- the chosen framework lane is explicit
- the response names the next skill or command, not the whole catalog
- the answer makes clear when to return to
bmad versus stay inside a
framework-specific skill
Examples
Example 1: Choose a framework before architecture
Input:
We want to use BMAD for an AI support agent, but we still need to decide between LangGraph and Deep Agents.
Expected shape:
- treats this as BMAD analysis or planning plus framework selection
- routes first to
framework-selection
- avoids listing implementation-only skills before the framework decision is
made
Example 2: Route a LangGraph architecture phase
Input:
Our PRD is approved. We need the next BMAD step for a LangGraph workflow with durable execution.
Expected shape:
- recognizes this as BMAD solutioning after a reviewed PRD
- routes to architecture work plus
langgraph-fundamentals and
langgraph-persistence
- keeps BMAD phase gating explicit
Example 3: Keep ideation out of the framework bridge
Input:
Brainstorm three agent product ideas before we choose any framework.
Expected shape:
- routes to
bmad-idea
- avoids forcing a LangChain ecosystem decision too early
- returns to
langchain-bmad only after the idea is ready for structured
delivery
Example 4: Hand off implementation to the right framework skill
Input:
The architecture is done. We need HITL approval and persistence in our LangGraph app.
Expected shape:
- treats this as implementation handoff, not fresh BMAD setup
- routes to
langgraph-human-in-the-loop and langgraph-persistence
- keeps
bmad as the artifact-tracking layer rather than repeating all BMAD
phase detail
Best practices
- Decide the BMAD lane and framework lane before suggesting commands.
- Stop at
framework-selection when the stack choice is still open.
- Keep BMAD responsible for artifact progression and review gates.
- Push phase maps and install detail into references instead of bloating the
entrypoint.
- Prefer one narrow framework skill over a full LangChain catalog dump.
- Add evals before considering a mutation loop for this bridge skill.
- Return to
bmad when the question becomes artifact progression rather than
framework implementation.
References
1---2name: langchain-bmad-23description: >4 Use when the user needs BMAD-style phased delivery for a LangChain,5 LangGraph, or Deep Agents project and wants the right framework skill at the6 right BMAD phase. Triggers on: langchain bmad, bmad langchain, langgraph7 bmad, deep agents bmad, structured agent development, phase-gated langchain8 workflow, framework-aware bmad, and BMAD for agent frameworks.9allowed-tools: Read Write Bash Grep Glob10metadata:11 tags: langchain, langgraph, deep-agents, bmad, workflow, structured-development, framework-selection12 platforms: Claude, Gemini, Codex, OpenCode13 keyword: langchain-bmad14 version: 1.1.015 source: https://skillmd.com/skills/akillness/langchain-bmad-216 upstream: akillness/oh-my-gods17---1819# langchain-bmad2021Use `langchain-bmad` when the job is combining BMAD phase discipline with the22LangChain ecosystem, not when the user only needs a single framework skill in23isolation. Keep the entrypoint focused on routing: choose the BMAD phase,24choose the framework lane, then load the narrowest downstream skill or support25file that fits.2627## When to use this skill2829- Start a new agent project and choose between LangChain, LangGraph, and Deep30 Agents inside a BMAD workflow31- Route a BMAD artifact or phase gate for a LangChain ecosystem project32- Decide which framework-specific skill should be loaded next after a BMAD33 planning or architecture step34- Install the BMAD and LangChain skill sets together for one project35- Keep framework choice, persistence, and HITL decisions aligned with BMAD36 phase boundaries3738Use a narrower skill instead when:3940- the user already knows the exact framework problem and does not need BMAD41 phase routing: use `langgraph-fundamentals`, `deep-agents-core`, or the specific42 LangChain skill directly43- the user mainly needs BMAD phase routing without framework-specific guidance:44 use `bmad`45- the user is still shaping the idea before structured delivery: use46 `bmad-idea`4748## Instructions4950### Step 1: Classify both dimensions before naming commands5152Identify:5354- BMAD lane: bootstrap, phase-status, artifact-routing, phase-gate, or55 implementation handoff56- Framework lane: LangChain, LangGraph, Deep Agents, or framework-selection5758Do not dump every BMAD phase and every LangChain skill in one response before59these two lanes are clear.6061### Step 2: Choose the BMAD phase and the next framework decision together6263Use `references/phase-map.md` to map the current BMAD phase to the narrowest64next skill:6566- Analysis: `framework-selection`67- Planning: `langchain-dependencies`68- Solutioning:69 - LangChain -> `langchain-fundamentals`70 - LangGraph -> `langgraph-fundamentals` plus `langgraph-persistence`71 - Deep Agents -> `deep-agents-core`72- Implementation:73 - LangChain -> `langchain-middleware`, optional `langchain-rag`74 - LangGraph -> `langgraph-human-in-the-loop`, `langgraph-persistence`75 - Deep Agents -> `deep-agents-memory`, `deep-agents-orchestration`7677If the user has not chosen a framework yet, stop at `framework-selection`78instead of pretending all three lanes should run.7980### Step 3: Load only the support file that matches the current gap8182Use progressive disclosure:8384- `references/phase-map.md` for the BMAD-phase to framework-skill routing table85- `references/setup-and-handoff.md` for install commands, package bundles, and86 handoff rules between BMAD and framework skills8788Keep the main skill compact instead of leaving the entire phase map, setup89guide, and implementation catalog inline.9091### Step 4: Preserve BMAD gates while delegating framework detail9293Use `bmad` to keep artifact progression and review gates honest:9495- use BMAD to decide which artifact is next96- use the framework skill to shape the technical content of that artifact97- use `plannotator` or the existing BMAD review gate before advancing major98 phase documents99100Do not let framework implementation detail bypass the BMAD artifact gate.101102### Step 5: Verify that the route is specific and minimal103104Before claiming success, prove that:105106- the chosen BMAD phase matches the user's immediate job107- the chosen framework lane is explicit108- the response names the next skill or command, not the whole catalog109- the answer makes clear when to return to `bmad` versus stay inside a110 framework-specific skill111112## Examples113114### Example 1: Choose a framework before architecture115116Input:117118```text119We want to use BMAD for an AI support agent, but we still need to decide between LangGraph and Deep Agents.120```121122Expected shape:123124- treats this as BMAD analysis or planning plus framework selection125- routes first to `framework-selection`126- avoids listing implementation-only skills before the framework decision is127 made128129### Example 2: Route a LangGraph architecture phase130131Input:132133```text134Our PRD is approved. We need the next BMAD step for a LangGraph workflow with durable execution.135```136137Expected shape:138139- recognizes this as BMAD solutioning after a reviewed PRD140- routes to architecture work plus `langgraph-fundamentals` and141 `langgraph-persistence`142- keeps BMAD phase gating explicit143144### Example 3: Keep ideation out of the framework bridge145146Input:147148```text149Brainstorm three agent product ideas before we choose any framework.150```151152Expected shape:153154- routes to `bmad-idea`155- avoids forcing a LangChain ecosystem decision too early156- returns to `langchain-bmad` only after the idea is ready for structured157 delivery158159### Example 4: Hand off implementation to the right framework skill160161Input:162163```text164The architecture is done. We need HITL approval and persistence in our LangGraph app.165```166167Expected shape:168169- treats this as implementation handoff, not fresh BMAD setup170- routes to `langgraph-human-in-the-loop` and `langgraph-persistence`171- keeps `bmad` as the artifact-tracking layer rather than repeating all BMAD172 phase detail173174## Best practices1751761. Decide the BMAD lane and framework lane before suggesting commands.1772. Stop at `framework-selection` when the stack choice is still open.1783. Keep BMAD responsible for artifact progression and review gates.1794. Push phase maps and install detail into references instead of bloating the180 entrypoint.1815. Prefer one narrow framework skill over a full LangChain catalog dump.1826. Add evals before considering a mutation loop for this bridge skill.1837. Return to `bmad` when the question becomes artifact progression rather than184 framework implementation.185186## References187188- `references/phase-map.md`189- `references/setup-and-handoff.md`190- [LangChain Skills launch](https://www.langchain.com/blog/langchain-skills)191- [Deep Agents skills docs](https://docs.langchain.com/oss/javascript/deepagents/skills)192- [BMAD Method docs](https://docs.bmad-method.org/)193- [Creative Intelligence docs](https://docs.bmad-method.org/explanation/creative-intelligence/)