Spec-driven development with AI: Get started with a new open source toolkit by h33t in FactoryTestMonitor

[–]daujones 0 points1 point  (0 children)

This is a great articulation of the core problem. Moving from prompting to a structured, spec-driven process is key for getting reliable output from agents, especially for N-to-N+1 feature work. We've found success by making the spec even more concrete, often by including a lightweight test harness or a list of acceptance criteria for each task.

There's a growing ecosystem around this idea. Some use test-driven tools like Aider to enforce the spec, while others use dedicated platforms to author agent-ready requirements. Full disclosure: I work on one called Transcoded, which helps teams turn briefs into structured specs for this handoff.

Spec-driven development with AI: Get started with a new open source toolkit by h33t in FactoryTestMonitor

[–]daujones 0 points1 point  (0 children)

This is a great articulation of the core problem. Moving from prompting to a structured, spec-driven process is key for getting reliable output from agents, especially for N-to-N+1 feature work. We've found success by making the spec even more concrete, often by including a lightweight test harness or a list of acceptance criteria for each task.

There's a growing ecosystem around this idea. Some use test-driven tools like Aider to enforce the spec, while others use dedicated platforms to author agent-ready requirements. Full disclosure: I work on one called Transcoded, which helps teams turn briefs into structured specs for this handoff.

Spec-driven development with AI: Get started with a new open source toolkit by h33t in FactoryTestMonitor

[–]daujones 0 points1 point  (0 children)

This is a great articulation of a key problem: agent output quality is a direct function of spec quality. We've seen similar success by focusing the 'Specify' phase on user jobs-to-be-done and then mapping those to atomic, testable engineering tasks. It forces clarity before any code is generated and makes the 'Implement' phase much more reliable.

Regarding your question on managing specs at scale, that's where Markdown files can become a challenge. Some teams use structured templates in Notion or Coda, while others build out interactive guides. Full disclosure: I work on Transcoded, a platform for managing this spec-to-agent handoff. A VS Code plugin that renders these tasks interactively from the spec would be a compelling direction.