Turn dictated specs into tickets and code with LLM agents

A developer dictates a spec, has LLMs densify it, then plan and scaffold the project, and an agent files implementation tickets per module. · Oct 31, 2026

What They Did: The developer dictates a rambling spec, Whisper transcribes it, and an LLM condenses it into a structured markdown spec filed as issue 1. After human edits and another LLM densifying pass, an LLM writes a plan and scaffolding. An agent files per-module tickets, parallel agents write commit-level tasks and implement them as PRs, and an adversarial reviewer plus rework agents iterate.
How It Went: The author reports quite good results, with most PRs landing as-is and occasional corrections when the agent took the wrong approach. No numbers are given; the author says it is far cheaper than human developers despite many parallel agents and CI runs.
Worth Knowing: Works best when code is highly modular so agents rarely cross modules; the author keeps shared workflow, style, and lint policies in one repo vendored into each project.

Try it yourself with custom-built or unnamed agent

I'm going to paste a rough, dictated spec for [project idea]. First rewrite it into a tight, complete spec and list any open questions for me. Then propose a module-by-module plan, scaffold the project in [language/framework], and write one implementation ticket per module as a markdown file in a tickets folder, each with scope, acceptance criteria, and dependencies. Stop when the scaffold runs and every module has a ticket, then show me the list before doing any more work.

Read the original ↗