I kept running into the same problem: well-written tickets (by human standards) had to be re-explained to claude code. Code. “Update the auth module” - which auth module? Which files? What tests to run? I continue to expand claude bootstrap whenever I come across an issue that I think is faced by others too. So I built a skill for Claude Bootstrap that redefines how tickets are written. The core idea: a ticket is a prompt Traditional tickets assume the developer can ask questions in Slack, infer intent, and draw on institutional knowledge. AI agents can’t do any of that. Every ticket needs to be self-contained. What I added: INVEST+C criteria
- standard INVEST (Independent, Negotiable, Valuable, Estimable, Small, Testable) plus C for Claude-Ready: can an AI agent execute this without asking a single clarifying question? The “Claude Code Context” section - this is the key addition to every ticket template: This section turns a ticket from “something a human interprets” into “something an agent executes.” ### Claude Code Context #### Relevant Files (read these first) - src/services/auth.ts - Existing service to extend - src/models/user.ts - User model definition #### Pattern Reference Follow the pattern in src/services/user.ts for service layer. #### Constraints - Do NOT modify existing middleware - Do NOT add new dependencies #### Verification npm test – --grep “rate-limit” npm run lint npm run typecheck 4 ticket templates optimized for AI execution:
- Feature - user story + Given-When-Then acceptance criteria + Claude Code Context
- Bug - repro steps + test gap analysis + TDD fix workflow
- Tech Debt - problem statement + current vs proposed + risk assessment
- Epic Breakdown - decomposition table + agent team mapping 16-point Claude Code Ready Checklist - validates a ticket before it enters a sprint. If any box is unchecked, the ticket isn’t ready. Okay this is a bit opininated. Story point calibration for AI - agents estimate differently than humans:
- 1pt = single file, ~5 min - 3pt = 2-4 files, ~30 min - 5pt = 4-8 files, ~1 hour - 8+ = split it The anti-patterns we kept seeing Title-only tickets - “Fix login” with empty description Missing file references - “Update the auth module” (which of 20 files?) No verification - no test command, so the agent can’t check its own work Vague acceptance criteria - “should be fast” instead of “response < 200ms” Anthropic’s own docs say verification is the single highest-leverage thing you can give Claude Code. A ticket without a test command is a ticket that will produce untested code. Works with any ticket system Jira, Asana, Linear, GitHub Issues - the templates are markdown. Paste them into whatever you use. Check it out here: github.com/alinaqi/claude-bootstrap submitted by /u/naxmax2019
Originally posted by u/naxmax2019 on r/ClaudeCode
You must log in or # to comment.