Planning
Action Items, Goals & Insights
The conversation is your project management. You don't update a board afterwards, you don't summarise in Slack, you don't open GitHub separately. Work is tracked and the plan is live as the conversation happens — one subscription, one source of truth, no separate tracker to keep in sync.
Exponential backoff for Stripe webhook retries
from session 23 · 3 acceptance criteria
Auth fixes — token refresh, session expiry, logout race
rolled up from 3 commits this morning
Migrate billing page to new pricing constants
verified on video · closed yesterday
— the board, keeping itself. One item came from commits alone.
Nobody wants to write the ticket
Process tools assume someone will stop and document: write the ticket, groom the backlog, update the status, summarise it for standup. On a small team, that someone is you — and it's hours a week. So the board drifts from reality, and the tool you pay for becomes a chore you avoid.
You spend the morning fixing auth bugs across three commits. You never open your project board. By lunchtime, your product owner sees a single, clear ticket summarising everything you did — and why.
How it works
DevSpec keeps the project record as a side effect of the work, not a separate job.
Action items fall out of conversation
Discuss a bug, sketch a feature, agree on a fix — the AI captures it as an action item with a description, acceptance criteria, priority, and type. Bigger pieces become briefs that break down into child items.
An action item created from a session, complete with acceptance criteriaThe ticket wrote itself while you were still talking.
Commits write their own tickets
Shipping fast without documenting? DevSpec watches your pushes, reads what actually changed, and creates items retroactively. Five pushes on the same feature roll up into one coherent record.
Retroactive items generated from a morning of commitsThree commits in, one coherent record out.
Goals measure themselves
Set the end goal. DevSpec assesses progress toward it with evidence from your actual work — sessions, commits, deployments. Not ticket counts: real clarity on whether you're moving toward the thing that matters.
A goal with AI-assessed progress and linked evidenceProgress with evidence attached, not a percentage someone guessed.
Reports written for you, not by you
DevSpec uses the full project narrative to generate reports tailored to each person's role. A salesperson sees feature highlights. A product owner sees what shipped and what's blocked. An engineering lead sees velocity and risk.
A narrative report generated for a non-technical stakeholderThe status update nobody had to write.
A project record that matches reality
A lifecycle, not columns
Items move open → implementing → deployed → verified, driven by what actually happened. Blocked or failing work surfaces in a needs-attention bucket instead of rotting in a column.
Acceptance criteria built in
Every item carries criteria the team agreed on in conversation — and AI verification uses those same criteria to test the deployed result later.
Real relationships
Blocks, caused-by, supersedes, related-to. Dependencies are facts the queue respects, not labels nobody reads.
Assignment that includes agents
Route items to a teammate — or stage them and let Autopilot pick them up. Everyone knows who (or what) owns each piece.
Insights you would otherwise miss
DevSpec synthesises changelogs, open items, and goal progress to surface what the team might overlook — an environment variable change gets flagged before the production deploy breaks.
Changelog without ceremony
A deployment-aware changelog assembles itself from the work as it ships. The daily digest keeps everyone current without a standup.
Convinced?
Set up your first project in under five minutes. Connect your repo, start a session, and see what your duck can do.
Start Your Project14-day free trial · 1,500 credits included