For your workWeb development

Web development project management with Claude on the code.

Designs become tasks, tasks become branches, and every pull request lands on the card it came from. While you sleep, a fleet of Claude Code workers clears the ready backlog and leaves the merging to you.

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

Sound familiar?

Where a build loses its days.

The designs change in Figma and the tickets never catch up.

With ProjectifyClaude reads the Figma file and files what it finds as tasks, once each, so a new frame becomes a card and not a surprise at QA.

Two of us fixed the same bug on the same afternoon.

With ProjectifyA claim has one holder at a time, person or agent, and frees itself after 30 quiet minutes. Start next hands out only free, unblocked work.

The small tickets wait months behind the big features.

With ProjectifyLeave them ready on the board. Fleet workers take them overnight, each in its own git worktree, and open a pull request for the morning.
What Claude does for web development

More hands on the backlog, fewer meetings about it.

Works the backlog overnight

Run projectify fleet before you log off. Workers on your machine take the ready tasks, each in its own worktree, and open pull requests. They never merge.

Three pull requests opened overnight, all in Review.

Reviews each pull request

A Reviewer checks every fleet pull request against its task’s done-when and runs your checks, so you read the ones that are ready first.

LRK-36: changes asked, alt text missing on two images.

Runs your go-live list

Redirects, forms, analytics, meta tags and a last look on staging. Record a launch once and every site goes live the same way, with checks for a person.

Larkspur go-live: 6 of 8 steps done, redirects wait for Sana.

Turns QA notes into tasks

Paste a round of QA notes or a client’s email into chat. Each issue becomes a task on the right page, with the words it came from.

Seven issues from Thursday’s QA are on the board.
Your board, shaped for web development

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 progressCode reviewQAShipped

Fields

Page or screenTypeEstimatePull requestSprintOwner

Views

BoardListTimelineWorkloadDashboard
  1. Content freeze
  2. Redirect map from the old sitemap
  3. Lead checks the redirects (a person checks)
  4. Forms and analytics tested
  5. Performance and accessibility pass
  6. Sign-off on staging (a person checks)

Go-live checklist, as a workflow. The clay steps stop for a person. How workflows work

Questions

Before you connect the repo.

Does the fleet merge code on its own?

No. Each worker opens a pull request from its own git worktree, a Reviewer checks it against the task, and a person on your team merges.

Does it work for app development project management too?

Yes. The same board runs web and mobile app builds: screens instead of pages, a field for platform, and the same claims, queue and pull requests.

Where does the fleet run?

On your own machine, in Claude Code, on your Claude plan. It needs a code repo and runs only when you start it.

We already plan sprints in Azure DevOps.

Azure DevOps syncs both ways, as do Trello and Monday. GitHub branches and pull requests show on the tasks they belong to.

Put the backlog to work tonight.

A month of Premium free, no card, and your first repo connected before you log off.