Core Workflow
Devplan has two workflows: product intelligence (integrations → catalog → signals → insights → daily digest) and feature planning (idea → specs → implementation). Better sources produce better digests, insights, and planning output.
Product intelligence
| Layer | What it is | Where you see it |
|---|---|---|
| Workspace context | Goals, customers, competitors | Workspace, onboarding |
| Integrations | GitHub, Slack, Jira, docs, and more | Integrations |
| Uploads | Files in the knowledge graph | Knowledge > Integrations uploads |
| Feature catalog | Product features from code and docs | Product |
| Signals | Raw evidence items | Signals |
| Insights | Synthesized takeaways | Insights |
| Daily Digest | What changed, with evidence | Today |
1. Set workspace context
Add company details, goals, customers, and competitors during onboarding or on Workspace. Attach strategy docs to workspace sections when helpful.
2. Connect integrations
Open Knowledge > Integrations and connect your tools. Connect alone is usually not enough — also configure scope:
| Provider | Configure |
|---|---|
| GitHub / Bitbucket | Enable Analyze on repos |
| Slack | Invite the Devplan bot to channels in Slack |
| Confluence / Notion / Google Drive | Attach spaces, pages, or folders |
| Jira / Linear | Set allowed projects (Jira) or connect teams (Linear) |
Setup guides: Integrations overview.
Processing time: code repos often need 30+ minutes for first catalog bootstrap; other sources fill in over hours and days. Signals, Insights, and Today start thin and get richer.
3. Upload documents
Upload PDFs, decks, spreadsheets, and images under Knowledge > Integrations uploads (single library, no category picker). Uploads join the knowledge graph and surface in signals, insights, Ask Devplan, and digests.
4. Catalog, signals, insights, digest
- Catalog bootstrap runs after code repos are configured — maps features to code and connected tickets.
- Signals are individual evidence items on Signals.
- Insights synthesize signals into briefs on Insights; roles in Preferences personalize what you see.
- Today delivers workspace and personal digests with evidence pills. Updates shows catalog change history.
Feature planning
Nine steps from idea to implementation, with full product context:
| Step | What happens |
|---|---|
| 1. Input | Text, files, mockups, or ticket links |
| 2. Discovery | Planning Agent asks targeted questions |
| 3. PRD | Generated and self-reviewed PRD |
| 4. User stories | Sized stories with Agentic Scores |
| 5. Technical design | Per-story implementation guidance |
| 6. PM export | Sync → one-way export to Jira or Linear |
| 7. Coding prompts | Context-rich prompts per story |
| 8. CLI | devplan specs start in your terminal |
| 9. Monitoring | Track progress in Runs |
Agentic Score indicates how ready a story is for AI implementation — low scores mean add detail before handing to an agent.
PM export is one-way. Ingestion from Jira/Linear into signals is separate — see Jira Integration.
Typical flow
- Complete Getting Started — context and integrations
- Wait for processing after new connections
- Review Today, Insights, Signals
- Use Ask Devplan for follow-up questions
- Create a project and run the planning workflow
- Keep adding sources and updating workspace context