Planning Pipeline
From idea to implementation-ready plan. One command runs brainstorm, research, adversarial review, and locks every bead with file paths, test cases, and acceptance criteria.
Works for non-technical founders too. Describe a feature in plain English -- the pipeline handles planning, research, review, and structuring.
$ /lavra-design "Photo upload for listings"
[brainstorm] 3 approaches, 2 edge cases
[research] 5 agents dispatched
[review] 4 reviewers, 1 revision
[locked] 4 beads created
Interactive dialogue that sharpens scope before any code is planned. Six structured steps force hard questions upfront.
Vision & success criteria
Define what success looks like. Who is this for? What triggered the idea?
One question at a time
Deep questioning: vision, constraints, scope, success criteria. No rushing.
Resolve ambiguity upfront
Sync or async? API layer or client? Decide now, not during implementation.
Scope expansion or reduction?
Find the 10-star product, challenge premises. What's the smallest version that proves this works?
2-3 options, pros & cons
Concrete approaches with trade-offs. Lead with recommendation. Apply YAGNI (You Aren't Gonna Need It).
Filed as child beads
Logical implementation phases with scope, goals, and locked decisions per phase.
Six phases transform an idea into beads so detailed that subagents can implement without asking questions.
5 domain-matched agents dispatched in parallel
Each agent gathers evidence -- docs, prior art, best practices, edge cases -- and logs findings as comments on the relevant beads.
4 adversarial reviewers challenge the plan
Each reviewer runs in parallel, looking for blind spots from a different angle. Findings are categorized as safe-to-auto-apply or requiring user judgment.
Integrate research findings
Research findings are merged into bead descriptions. Conflicts between research and plan assumptions are resolved.
File-scope conflict prevention
No two tasks touch the same file without a dependency. Parallel-safe.
Every bead implementation-ready
File paths, test cases, acceptance criteria, locked decisions. No questions left.
Structure into actionable beads
File paths. Test cases. Dependencies. No questions left.