Understand the territory.
Read the codebase, identify existing patterns, and turn an open question into useful context before implementation begins.
THE PLATFORM
One mission.
Every specialist.
Shared context.
DevPilot connects AI-assisted engineering into a project workflow: clear responsibilities, durable decisions, and evidence you can return to.
ONE SHARED PROJECT RECORD
CONTEXTResearchPlanBuildVerify
DIRECTION IN. REVIEWABLE WORK OUT.
01 / COORDINATED SPECIALISTSGive each agent a job.
Give each agent a job.
Give the work a direction.
A useful team needs more than parallel prompts. Scope, dependencies, and a shared definition of done give each contribution a place.
Make the next step explicit.
Break the objective into bounded tasks. Name the dependencies, assign responsibilities, and define what evidence will close each task.
Build within the brief.
Implementation work focuses on a clear slice of the project. Decisions and changes stay connected to the task that produced them.
Check the actual outcome.
Verification examines the resulting behavior. Keep checks, failures, fixes, and remaining questions visible for the next reviewer.
02 / DURABLE PROJECT MEMORYThe conversation ends.
The conversation ends.
The context stays.
Engineering knowledge is scattered easily: why an API stayed unchanged, which migration was deferred, or what a previous test actually proved. DevPilot’s project records give that knowledge a durable home.
Decisions, documentation, and checkpoints can be read through the gateway. A new session can start from recorded work instead of a retold story.
ILLUSTRATIVE PROJECT RECORD
Payment retries
- Decision
- Preserve the public response contract.
- Constraint
- No production migration in this task.
- Evidence
- Source diff + integration test output.
- Next step
- Review the deployment plan separately.
↳ Saved context, explicit boundaries
Make “done”
mean something.
Implementation
What changed, where it changed, and the intended behavior.
Verification
The checks that ran, their results, and what they do not cover.
Review
The tradeoffs, open questions, and decisions needed from you.
Release
A separate step with an explicit target and authorization.
A code change is evidence of implementation. A passing check is evidence about that check. Neither substitutes for a release decision.
04 / CONNECTED SURFACESWork where
Work where
the work happens.
The CLI, gateway, MCP interface, and native companion provide different ways into the engineering workflow.
The dp CLI
Inspect projects, work with sprints, and run the commands that connect your local development workflow.
Gateway + MCP
Expose project operations and records through structured interfaces for tools and agent clients.
DPXray
Explore the macOS companion and its visual approach to project health, work, and engineering context.
MAKE YOUR NEXT MOVE
Your next idea deserves a team.
Start with the problem. We’ll explore the right path together.