Core Workflow
Use Devplan to connect product understanding, planning, and delivery. Start with a useful question, inspect its evidence, and carry what you learn into the next decision.
Pipeline
| Layer | What it contributes |
|---|---|
| Workspace context | Your product, customers, priorities, and constraints |
| Connected sources | Selected code, tickets, conversations, meeting notes, and documents |
| Product knowledge | Live Docs, code-change summaries, signals, and decisions |
| Analysis | Insights, answers, proposals, reports, and project assessments |
| Your review | Corrections, decisions, and plans grounded in the available evidence |
1. Set workspace context
Describe your product, customers, and goals in Workspace. Add relevant strategy or research documents and keep important assumptions current.
2. Connect integrations
For a new workspace, connect sources through guided setup and wait for the initial product map to be ready before entering the main app. After onboarding, use Integrations to add or manage sources.
Choose sources that answer your team's questions. For example, code explains what was implemented, while feedback and discussions help explain why it matters. Integration types differ in whether they process selected material in the background or provide tools Weaver uses when needed.
3. Upload documents
Use uploads for research or context that is not available through a connected source. Attach project-specific material to the relevant project so its purpose is clear.
4. Review product knowledge and insights
Browse Live Docs, Changelog, signals, and decisions. Use Radar to catch up on the daily report and relevant work, then ask Weaver to investigate a specific question. For a recurring review, use the weekly report or a dashboard focused on your topic.
5. Evaluate and plan work
Review the proposals Devplan creates from connected evidence, or start a project from a problem you already understand. Refine the desired outcome, scope, requirements, and supporting context before moving into implementation.
6. Follow delivery
Review project progress and risks against the underlying evidence. Bring project context to a coding assistant through MCP or the developer workflow. Keep code and issue trackers current so subsequent analysis reflects the work.
Typical flow
A customer raises a problem in a meeting. Devplan extracts a signal from the connected notes, relates it to product context, and may surface a feature request or proposal. You inspect the original feedback, refine a project, and follow evidence of its implementation as work progresses.