Discovery Sessions
Guided project planning through structured conversation.
Discovery sessions are Lisa's structured approach to project planning. Instead of a blank chat, Lisa guides you through a four-phase process that turns ideas into actionable work.
Starting a discovery
Use the /discover command or ask Lisa to "start a discovery session." You'll be guided through:
Phase 1: Product Context
Lisa asks about:
- What problem are you solving?
- Who are the users?
- What does success look like?
- Are there existing solutions to build on?
Phase 2: Planning
Based on product context, Lisa helps you define:
- Technical approach and architecture decisions
- Scope boundaries (what's in, what's out)
- Risk assessment and mitigation
- Timeline estimates
Phase 3: Breakdown
Lisa breaks the plan into:
- Milestones with due dates
- Issues grouped by milestone
- Dependencies between issues
- Acceptance criteria for each issue
Phase 4: Tasks
The final phase creates concrete, developer-ready tasks:
- Each task has clear scope and acceptance criteria
- Dependencies are mapped
- Verification hints tell developers how to validate their work
- Everything is linked to the parent project and milestones
Output
At the end of a discovery session, Lisa has created:
- A project with description and custom AI instructions
- Milestones with due dates
- Issues with hierarchies, dependencies, and acceptance criteria
- Artifacts (PRDs, specs) linked to the project
Tips
- Be honest about unknowns — Lisa adapts her questions based on what you don't know
- Reference existing repositories for code-aware planning
- You can pause and resume discoveries — context is preserved
- Discovery output can be edited after generation