Split long projects into one spec and a stack of coding tickets
mattpocockuk · x · 2026-07-22
For big projects, split the plan into a spec and tickets
The post recommends dividing multi-phase work into two documents:
- The spec: where the project is going.
- The tickets: the step-by-step tasks to get there.
Why this helps:
- If the destination changes, you update the spec and discard unfinished tickets.
- Each ticket should fit into one coding session.
- You can clear context between sessions without losing the target, because the spec preserves the destination.
The quote frames this as a practical way to keep long coding projects flexible while avoiding context bloat.
More from coding & agent
- Open-source invoice auditor extracts fields, checks math, and flags anomalies — Arindam_1729 · 2026-07-22
- A 20-part breakdown of what actually powers an AI agent — goyalshaliniuk · 2026-07-22
- New agent-training livestream will teach GRPO with verifiers, reward hacking, and code-alongs — ben_burtenshaw · 2026-07-22
- OpenAI’s Codex beats Claude Code on interface and overall experience, user says — jxnlco · 2026-07-22
- User says t3code is the best browser automation tool they’ve used — tylerbruno05 · 2026-07-22
- Tldraw schedules its first hack night at a new office near Old Street — max__drake · 2026-07-22