docs: onboard to spec-driven workflow (CLAUDE.md Development Workflow block) - #28
Conversation
Onboards this repo to the /spec-driven-workflow flow with only its project-specific deltas: branch from main, gate = make test, OpenSpec via /opsx:*, the two-channel release, and the gotchas (single-source runner, bash-3.2 portability, and the INVERTED commit-attribution rule — this repo's own commits carry trailers, kit-emitted PROMPT artifacts carry none). The generic two-loop flow stays centralized in the skill + ~/.claude/CLAUDE.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BPf3HHoHVTdr8CFki4iRi2
|
@codex review |
![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: b3ec0a0db9
ℹ️ 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".
| For non-trivial changes, follow the two-loop spec-driven flow — invoke `/spec-driven-workflow` | ||
| for the full steps. This project's values: |
There was a problem hiding this comment.
In a fresh checkout of this repo, contributors cannot follow this new required step: I checked the tracked workflow surfaces (.claude/commands, .claude/skills, and skills/) and there is no spec-driven-workflow command or skill, while the repo does ship /opsx:* commands. As written, non-trivial changes now start by invoking a missing command, so the onboarding guidance stalls before the documented OpenSpec flow can begin unless this repo either includes that workflow or points at the shipped commands.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Good catch — fixed forward in #29 (1077b38). You're right that /spec-driven-workflow is the author's personal skill, not shipped here, while /opsx:* IS tracked in .claude/commands/opsx/. Reframed the block so the concrete entry points are /opsx:* + the listed values, with /spec-driven-workflow noted as an optional personal codification the repo doesn't depend on — so a fresh checkout can follow it.
…ted") The global commit-attribution rule is now a per-project soft default (none), not a mandate, so this repo overrides it rather than inverting it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_6a854fe2-5398-45e1-bcbb-bfd3673856f2
docs: workflow block points at shipped /opsx:* (addresses #28 review)
1 participant
What
Adds a
## Development Workflowsection to this repo'sCLAUDE.mdthat defers to the/spec-driven-workflowskill, carrying only this project's deltas:main; PRs tomain.make test(stubs claude/gh → green local predicts CI)./opsx:*.chore(release)commit;/release-ralph-harnessautomates it.base/scripts/only), bash-3.2/Python-3.7 portability, and the inverted commit-attribution rule (this repo's own commits carryCo-Authored-By/Claude-Sessiontrailers; kit-emitted PROMPT artifacts carry none).Docs only — no code, no version bump.
make testgreen.🤖 Generated with Claude Code