devplaninc/devplan
Product intelligence for software teams, powered by your Devplan workspace. Four dashboards refreshed twice every weekday: a Daily Radar tailored to you, Execution Monitoring with slipped work and a searchable changelog, a Demand Report with customer promises, market moves and suggested projects, and Engineering Analytics. Plan cycles from your team's real pace, and write specs that are tracked in Devplan automatically. Requires a Devplan account; setup walks you through creating one.
Build a personal Daily Radar ("Your daily radar") dashboard of what shipped, what's moving, what's stuck, and what needs the user's attention, tailored to their role, team, and projects. Use for "daily radar", "what happened yesterday", "team status", "standup prep", "what's blocked", "what needs my attention", or "catch me up".
Foundational context for product, customer, roadmap, project, launch, risk, planning, product-writing, coding, or review work that depends on what the company has built, decided, shipped, or heard from customers. Invoke even when the user doesn't mention Devplan, whenever local context may be insufficient, and whenever another Devplan skill asks for product context. Skip generic tasks answerable from local evidence.
Set up Devplan - connect or create a Devplan workspace, confirm company context, build every dashboard, and schedule twice-daily weekday refreshes. Use right after install, when the user says "set up Devplan", "get started", "what does Devplan do", says "refresh my Devplan dashboards", wants to change their dashboards, schedule, or company context, or another Devplan skill finds Devplan isn't connected.
Build an Engineering Analytics dashboard of PR throughput, cycle time, review load, and work in progress, daily or weekly, by person and repo. Use for "engineering metrics", "cycle time", "how fast are we shipping", "throughput", "review bottlenecks", "team productivity", or "DORA".
Turn an idea, request, or suggested or inferred project into a spec with scope, technical approach, and estimate, after a few discovery questions, and track it in Devplan. Use for "write a spec", "write a Devplan spec", "plan this feature", "new project", "technical plan", "how should we build", "how long will this take", "estimate this", "PRD", "scope this project", or "update the spec".