Work Pipeline — Ryan’s Real Operating Flow
This is the actual workflow in practice:
- Ryan starts with an idea.
- Ryan chooses BMAD or Pulp/Compound lane.
- BMAD is used mainly for planning + wiki documentation.
- Execution work is handed to Hank/Max using Compound Engineering.
High-Level Flow
Lane Definitions
BMAD Lane (Planning + Wiki)
Use this when the goal is:
- brainstorming,
- strategy shaping,
- writing docs,
- preserving decisions in the wiki.
BMAD output is primarily artifacts and clarity, not direct shipping.
Execution Lane (Compound Engineering)
Use this when the goal is shipping:
- concrete implementation,
- PR creation and review,
- deployment and iteration.
Execution is run through the Compound cycle:
- Plan → Work → Review → Compound
Typical handoff pattern:
- Ryan brainstorms in Claude,
- then passes the plan to Hank (and Max when product/design input is needed),
- then execution proceeds through PR and deploy.
Practical Rule of Thumb
- Need to think? Use BMAD.
- Need to ship? Use Compound Engineering with Hank/Max.
- Need both? BMAD first for planning context, then Compound for execution.