chore(openspec): initialize project workflow - #120
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c6e4c050a3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| --- | ||
| name: "OPSX: Apply" | ||
| description: Implement tasks from an OpenSpec change (Experimental) | ||
| allowed-tools: Bash(openspec:*) |
There was a problem hiding this comment.
This adds agent-executed workflow commands with shell access to an external CLI, which is a high-risk command/runtime change under AGENTS.md. The commit message declares Issue ID: N/A, and the supplied review context provides no maintainer/override-intake; per the repository review policy, pause ordinary review and obtain maintainer attention or an explicit override before merging.
Useful? React with 👍 / 👎.
| **Handle states:** | ||
| - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue` |
There was a problem hiding this comment.
When apply is invoked before all required artifacts exist, this directs the user to /opsx:continue, but the added command registry contains only apply, archive, explore, propose, sync, and update; a repo-wide search also finds no opsx:continue or openspec-continue-change skill. That leaves the documented blocked-state recovery path unusable (and the Codex apply skill similarly points to the absent openspec-continue-change), so incomplete changes cannot follow the prescribed workflow.
Useful? React with 👍 / 👎.
| 4. **For each delta spec, apply changes to main specs** | ||
|
|
||
| For each repo-local capability delta spec path returned by the CLI: | ||
|
|
||
| a. **Read the delta spec** to understand the intended changes | ||
|
|
||
| b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet) |
There was a problem hiding this comment.
For a registered standalone store, the preceding store-selection instructions require all spec operations to use that store, but this hard-codes the current checkout’s openspec/specs path rather than deriving the main-spec location from the store/status context. Running sync from a repository with a local openspec/ directory will therefore update that local directory instead of the selected store (or create a new wrong one), leaving the store’s delta specs unsynchronized.
Useful? React with 👍 / 👎.
1 participant
Summary
Issue ID
Test Plan
openspec doctor --json: healthygit diff --check origin/main...HEAD