User Problem

When using Rovo Dev, there is not an explicit configuration for specification toolkits that support the practice of spec-driven development (SDD).

Relevant toolkits:
https://github.com/github/spec-kit
https://openspec.dev/
https://github.com/buildermethods/agent-os
https://github.com/bmad-code-org/BMAD-METHOD

Suggested Solutions

Rovo Dev should support spec-driven development toolkits with a "Spec Mode", which would allow:

1. Support workflow execution for spec creation, validation, and implementation, including frontmatter metadata (description + argument injection).
2. Detect structured spec repository layouts and/or allow configuration of the spec directory.
3. Support common locations without enforcing one

• {{ {project-root}/.claude/ }}
• {{ {project-root}/_bmad/ }}
• (optionally) shared locations like ~/.bmad

1. Work seamlessly with both git-controlled and git-ignored workflow assets.
2. Generate structured pull requests aligned with toolkit conventions.
3. Provide validation between specification and implementation.
4. Avoid conflicts with toolkit-defined role/persona redefinitions.
5. Prefer compatibility with existing “skills/workflow” patterns used by other agentic tools, rather than introducing a proprietary mechanism.

A rather simplistic solution would be to provide configuration options for memory, prompts, and subagents.

Current Workarounds

Rovo Dev CLI docs cover similar but proprietary features for memory,  prompts and subagents . These are the fundamental building blocks for the SDD frameworks; however, the proprietary nature of Rovo Dev's file structure & priorities means that such frameworks are difficult to package & install for Rovo Dev; they would need to be "shoehorned" into Rovo Dev's specific files and would be difficult to manage over time with respect to framework evolution.