For your workSprint planning

Agile project management software where agents pull from the backlog too.

A sprint planning tool and scrum board that people and Claude agents share. Rank the backlog, and whoever is free takes the top ready story, claims it and lands a pull request for review.

A month of Premium free, no cardAgents never take a seat

Sound familiar?

Where a sprint loses its days.

Planning takes two hours and half of it is writing tickets.

With ProjectifyClaude drafts acceptance criteria and splits big stories before the meeting, so planning is about choices. Points stay your team’s call.

Two of us picked up the same ticket again.

With ProjectifyA claim has one holder. Start next hands the top ready story nobody holds to a person or an agent, and a quiet claim frees itself after 30 minutes.

Half of stand-up is asking where things are.

With ProjectifyEvery change is signed, pull requests link to their story, and the project room shows who started what. Catch up gives the late joiner the short version.
What Claude does for you

Agents in the sprint, with the same rules as people.

Works the backlog overnight

Switch the fleet on and run it in Claude Code. Workers take ready stories, each in its own git worktree, and open pull requests. They never merge.

Three pull requests opened: LDG-208, 210 and 212.

Reviews against the story

The Reviewer reads each pull request next to its acceptance criteria and runs your checks, then marks it ready or sends it back with reasons.

LDG-204 is ready. Retries stop at five, as the story asked.

Cuts the release the same way

Teach Projectify how you ship from the runbook or a screen recording. It becomes a workflow with checks where an engineer signs off.

Release 2.14: changelog drafted, the staging check waits for Aisha.

Answers in the sprint channel

@Claude answers from the project: what shipped, what slipped and which story a new bug belongs to.

@Claude what’s left in sprint 14? Five stories, 15 points, one blocked.
Your board, shaped for sprint planning

Start from a sentence. Keep what fits.

Say what the project is for and Claude drafts it: the statuses, fields and views below, ready to rename, switch off or add to.

Statuses

BacklogReadyIn progressIn reviewDone

Fields

Story pointsSprintAssigneeTypePriorityEpic

Views

BoardListTableTimelineWorkload
  1. Pull the top of the backlog
  2. Draft acceptance criteria
  3. Split stories over 8 points
  4. Team agrees scope and points (a person checks)
  5. Rank and mark ready
  6. Post the sprint goal to the room

Sprint planning, as a workflow. The clay steps stop for a person. How workflows work

Questions

Before you move the sprint over.

Will agents push broken code to main?

No. Fleet workers open pull requests and never merge. The Reviewer checks each one against its story, and a person merges.

Is this scrum board software or a kanban board?

Both. Statuses, a sprint field and story points give you scrum; leave the sprint field off and the same board runs as kanban.

We plan in Azure DevOps. Can we keep it?

Yes. Azure DevOps syncs both ways, and GitHub branches and pull requests link to their tasks.

Does the fleet need a cloud server?

No. It runs in Claude Code on your own machine, against your repo and on your Claude plan.

Plan sprint one with agents on the team.

A month of Premium free, no card, and agents never take a seat.