A skill that turns a statement of work into a schedule and tickets.
A colleague’s text-only prototype, taken to production: it reads a project’s statement of work and produces the schedule and the tickets, following the agency’s standard structure. It is in daily use.
What needed
solving.
Every new project starts from a statement of work, and someone has to turn its deliverables into a schedule and a set of epics and tickets that follow the agency’s standard structure. A colleague had built a text-only prototype of a Claude skill for it.
What I decided,
and why.
- 01
Start from the colleague’s prototype. The idea and the first version are theirs.
- 02
Connect it to the issue tracker through MCP and make it interactive, so the output is tickets in the tracker rather than text to copy across.
- 03
Keep tuning its judgment on exceptions and on the rules for creating tickets.
What shipped,
and what isn’t proven.
In daily use: a project’s statement of work goes in, and a full schedule and its tickets come out. Not proven: how much time it saves, and where it breaks. Neither has been measured.