spec-to-code: from pipeline to plugin, and the bug I almost ignored
This post was translated from Italian with the help of Claude.
For a few months now I’ve been using a pipeline of four Claude Code agents to take a feature from idea to implemented code: stories-init creates the workspace, spec-builder expands a rough idea into a complete spec, story-creator slices it into INVEST user stories, laravel-feature-builder implements a story in Laravel. It’s not a weekend experiment: I built Chimera Forge with it, a playful kobold-generating API (kaas.procionegobbo.it) and a Discord bot (kichand.procionegobbo.it). It’s tested, it works, and right now it fully fits my way of doing agentic coding.
Universe Generator: Thirty Years of Code Reborn
Universe Generator
1996: Access Basic and Virtual Dice
There’s a piece of code I’ve been carrying around for thirty years. Yes, thirty years. Since 1996. It was part of a personal project related to role-playing games, built on Microsoft Access 2.0, prehistoric stuff. In Access Basic, the scripting language that preceded VBA. For its time, it was incredibly advanced.
The system was a simple generator of space sectors based on probability tables. I found the tables on the internet, designed as aids for space-themed role-playing games. Using d6 and d100 dice, it could create star systems, their stars, and their planets. It was very simple, without many details (stellar class, planet type, diameter, and number of moons) and no pretense of realism. It was enough for me to let my imagination soar through outer space.