Using AI to Generate Project Tickets Before Coding Reduces Scope Drift
Structured AI Workflow for Better Code Management
A developer on r/ClaudeAI shared a specific workflow change that reduced scope drift when working with AI coding agents. Instead of letting AI touch code immediately after planning, they now have the AI generate detailed project tickets first.
Key Workflow Details
The process involves these specific steps:
- After planning but before writing any code, ask the AI to generate actual project tickets from the plan
- Break the plan into tasks and add sub-tasks
- Define scope and acceptance criteria for each task
- The ticket format can be Linear, Jira, or just a markdown board
Each AI agent or run only receives:
- The high-level task
- The specific sub-task it owns
- Not the entire plan and not every other ticket
Results and Benefits
This approach reduced:
- Huge diffs
- Scope creep
- "Why did it do that?" moments
The developer maintains a "Canceled" column in their board where they move tasks that don't work instead of deleting them. They write why each task was canceled, creating a decision history that prevents repeating old mistakes in new AI sessions.
📖 Read the full source: r/ClaudeAI
👀 See Also
Check Claude's project summaries into your repo — they're better than human docs
A developer suggests committing Claude-generated project summaries to your repo. They're good enough, take seconds to generate, and can help future readers.
AI Assistant Extracts Apple Watch Sleep Data for Clinic: 5 Gotchas
An AI assistant pulled Apple Watch sleep data into a clinic diary CSV. Key issues: in-bed vs asleep, timezone bugs, date offsets, missing zero-sleep nights, and invented HR values.
Stop Copy-Pasting Errors Into Claude Code — Give It Access Instead
Don't copy-paste errors into Claude Code. Instead, give it the API keys or tools it needs to self-diagnose and fix. The author shares practical patterns for staging databases, headless browsers, and eval environments.
OpenClaw Drift Fix: Four Operator Skills to Harden Agent Workflows
A developer shares four operator skills — Outcome Guard, Direction Clarifier, Routing Enforcer, Completion Verifier — to stop agents from drifting and calling tasks done prematurely.