How We’re Embracing Spec-Driven Development at OpsMill

OpsMill describes two experiments for incorporating AI into software development while retaining human oversight and code-quality controls. Its first approach adapts GitHub’s Spec Kit into a spec-driven workflow in which engineers create and review Markdown specifications before an LLM proposes a code-change plan and then implements approved work; the company reports nearly 115 pull requests since February and cites earlier edge-case detection and easier onboarding as benefits. However, it notes that changing requirements can make specifications stale, and updating internal knowledge from completed work remains partly manual. Its second approach uses agents to analyze GitHub bug reports, identify likely root causes, reproduce issues, recommend fixes, generate failing tests, and assist with implementation, with engineers reviewing each stage; approximately 15 fixes have been merged so far. OpsMill ultimately aims to unify feature development, bug fixing, and other engineering tasks into an agent-supported, test-driven process with specifications, planning, implementation standards, and continued engineer involvement, while also exploring how the approach could support technical-debt reduction.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.