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
- alphaXiv open-sources OpenResearch to run parallel research agents with any model — alphaXiv · 2026-09-11
- MathModelAgent gains traction: auto-solves math modeling and writes a submission-ready paper — jihe520 · 2026-09-11
- DeskcommCRM: open-source AI sales CRM with native agents and WhatsApp hits 1k stars — melgarafael · 2026-09-11
- hyperresearch: agent-driven knowledge base that turns web research into a searchable wiki — jordan-gibbs · 2026-09-11
- Forter's 13 lessons from its agent sprint: skip custom RAG, lean on mature enterprise search — bibryam · 2026-09-11
- Two real 'company brains' opened up live: Gorgias' in-house Cortex vs Slite — femke_plantinga · 2026-09-11