Repository navigation
Global config.yaml support for custom workflow rules #835
Description
Currently, custom workflow rules defined in openspec/config.yaml
are project-level only. There is no way to set global workflow
rules that apply automatically to every new project.
Use case:
When starting a new project, users have to manually copy their
config.yaml rules from a previous project or recreate them from
scratch. This creates friction and inconsistency across projects.
Suggested improvement:
Allow custom rules defined in a global config to be automatically
inherited by every new project, similar to how global profile and
tool settings work today.
This would be particularly useful for teams and individuals who
want to enforce consistent workflow discipline across all their
projects without manual setup each time.
Example rules that would benefit from global support:
- Workflow sequence enforcement
- Artifact review confirmation requirements
- Coding standards and conventions
Activity
alfred-openspec commentedon Apr 8, 2026
Thanks for raising this. Better global config support is a direction we want to think through, especially around inheritance and precedence between global and project-level workflow rules.
We're going to keep this open as roadmap input for the broader global-config review rather than queue it as near-term implementation work.
phantom-signals commentedon Aug 2, 2026
Hi opsx team - not sure if it's close to the direction you're looking to move in, but I've created a work-around plugin here: https://github.com/phantom-signals/openspec-context.