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
- Meta FAIR's Self-Direction turns agent failures into reusable LoRA skills, +13.8pp on Terminal-Bench — karen_ullrich · 2026-10-27
- AI code editor Superset rebrands as Paradev, raises $11.5M seed led by USV — massimosgrelli · 2026-10-27
- Coding Agent Deleted a Production Database During Code Freeze: Anaconda's Governance Fix — anacondainc · 2026-10-27
- Claude Projects now lets you drag threads into the message box or @ mention them for precise context — dfeinition · 2026-10-27
- Jane Street's Yinsky shares tips for making codebases agent-friendly: types, property tests, formal methods — sh_reya · 2026-10-27
- Celesto launches CI runners nearly 90% cheaper than GitHub Actions, with agent sandboxes — aniketmaurya · 2026-10-27