How it works

From a sentence to shipped, without rewriting tickets twice.

TackPile is built around one loop: humans pile up intent, the system refines it into work an AI agent can execute, and the agent ships it autonomously while your board stays honest.

STEP 01

Set the rules once.

Give TackPile your product vision, glossary, tech stack, and the guardrails your agent should follow. This context is automatically injected into every story refinement and every MCP read.

▸Product vision & non-goals
▸Stack, frameworks, conventions
▸Agent rules: where to push, what to avoid, when to ask
▸Glossary so the agent uses your team's words

VISION.MD

# Product TackPile is a backlog for tiny AI-native teams. # Stack - Next.js 15 / React 19 - Postgres + Drizzle - Resend for email # Agent rules - Open a PR, never push to main - Ask before adding new dependencies - Use Tailwind utilities, no CSS modules

STEP 02

Pile up the work.

Drop in raw ideas. A sentence is enough; a sentence with a screenshot is plenty. Tag the page or feature, mark severity, link related items. The whole point is to keep capture friction near zero.

▸One-line ideas → captured in seconds
▸Page / feature / area tagging
▸Optional screenshots and links
▸Bulk paste for triage sessions

NEW ITEM

idea: login button looks weird on mobile, padding off page: /sign-in severity: low

STEP 03

AI rewrites it for the agent.

TackPile uses your vision and rules to convert each idea into a user story with acceptance criteria, written so an AI agent can execute it without a second round of clarification. You review, edit if needed, approve.

▸User story with explicit AC
▸Constraints lifted from your rules
▸Out-of-scope notes so the agent stops where it should
▸One-click approve to mark Ready for AI

TP-127 · READY FOR AI

As a signed-out user on /sign-in, I want the login button padded correctly on screens < 640px so it doesn't crowd the email input. AC: - Button has min-h-44px on mobile - 12px gap between input and button - No regression on >= 640px Out of scope: - Visual redesign of the form - OAuth provider buttons

STEP 04

Prioritize. The agent picks up the top.

Drag to reorder. The agent (Claude Code, Cursor, anything MCP-aware) pulls the top Ready-for-AI item, transitions it to In Progress, ships it, and walks it through your custom states.

▸MCP: list, read, transition, comment
▸Customizable states beyond To Do / Done
▸Live webhooks on every change
▸Talk to the agent on the item itself

AGENT TIMELINE

09:14 TP-127 → In Progress 09:18 TP-127 ✓ Tests passing 09:19 TP-127 → In Dev (PR #234) 09:42 TP-127 → Done

The agent loop

Live, while your team watches.

Every state transition, comment, or PR link the agent makes fires a webhook and updates the board in real time. No polling, no stale standups, no "wait, what's the agent on right now?" The truth is on the board.

See the MCP surface →

claude-code · tackpile mcp

$ claude code --next-from tackpile

› Connecting to TackPile via MCP…

› Found 4 items in "Ready for AI". Pulling priority #1.

[tackpile]TP-127 · Add OAuth loginIn Progress

› Reading product vision + agent rules…

› Drafting implementation across 7 files…

✓ Tests passing · 18/18

[tackpile]TP-127In Progress→In Dev

› PR #234 opened · linked to TP-127

[tackpile]TP-127In Dev→Done

Try it with your team.

Early access is rolling out to small teams first. Get on the list and we'll reach out with onboarding.