Monorepo change/spec naming rules

[dhndmn]

I use OpenSpec in the root of a small monorepo. I want my changes and specs to be prefixed with the project's name for organization (project-name-change-name instead of just change-name). What is the most reliable way to do this? Should I:

1. Provide the desired name in the proposal prompt: "/opsx-propose project-name-change-name Build this new feature..."
2. Define a rule in config.yaml (specs: -Prefix specs with the project name (project-name-feature-name)
3. Manually change the directory/file names after archiving (or with another prompt)

My preference would be 2 but this prompt hasn't been working for me at all. Has anyone else found a way to reliably control the naming of changes and specs? Thank you!

[dhndmn]

I've had some success with some models (GPT-5.4 and Opus 4.6) using the name I provide after opsx:propose for the change but neither have then used the same name on the archived spec. At the moment it seems renaming the change and spec at the end is the way to go.

[JayceZhang9602]

Since both changes and specs are generated under the projectRoot/openspec directory, I created an AGENTS.md file directly in projectRoot/openspec/ to manage naming conventions.
The key insight is that whenever an agent creates or modifies files in this directory, it will naturally read AGENTS.md first

projectRoot/openspec/AGENTS.md example:

# OpenSpec Instructions

Instructions for AI coding assistants using OpenSpec in this monorepo.

## Naming Conventions

OpenSpec CLI requires flat directories under `openspec/specs/` and `openspec/changes/`. To keep things organized in a large monorepo, we use **structured naming conventions** instead of nested folders.

### Spec Naming

`{scope}-{module}[-{feature}]`

> **Note:** The OpenSpec CLI does not support underscores (`_`) as separators — always use hyphens (`-`).

- **scope**: identifies which project or domain owns this spec (see [Allowed Scopes](#allowed-scopes))
- **module**: the functional area within that scope
- **feature** (optional): a specific feature within the module

### Change Naming

`{verb}-{scope}-{module}[-{feature}]`

- **verb**: what kind of change this is (see [Allowed Verbs](#allowed-verbs))
- Remaining segments follow the same pattern as spec naming

[dhndmn]

Great suggestion - thanks!