docs(openspec): adopt spec-driven development policy#323
Merged
Conversation
Integrate OpenSpec spec-driven development as the contributor workflow, adapted from ergane's policy to dots' Go quality gate. - AGENTS.md: add "Spec-Driven Development (OpenSpec)" section — route behavioral changes through openspec/ (proposal + deltas + tasks), validate, get approval, archive into base specs within the same PR. Specs stay local docs only; never wired into CI. The gate stays the Pre-Completion Checklist (go install, revive, go test, skill tests, skill linter, qlty). - openspec/project.md: add matching "OpenSpec note". - README.md: add Spec-Driven Development subsection under Development. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
The escaped quotes (\") in the back-reference code example tripped agnix's "Windows path separator" check, failing CI (5 errors). Inside markdown backticks the backslashes were also wrong — they'd render literally. Use plain quotes; agnix is clean (0 errors). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
drn
added a commit
that referenced
this pull request
Jun 24, 2026
`openspec/specs/` was empty after the OpenSpec policy adoption (#323), so change proposals had no baseline to diff against. This backfills base specs documenting the CURRENT, already-shipping behavior of the dots CLI. Capabilities: - cli-framework: Cobra entry/command tree, component registry + dispatch, process-exit error model, pkg/run, pkg/path, cli/link, pkg/cache, cli/is - component-install: `dots install` selection, install-all orchestration, and each per-component installer (shell, editor, fonts, packages, languages, macOS defaults, tools, pi.dev) - agent-config-install: `dots install agents` symlinks + idempotent hook and status-line registration in ~/.claude/settings.json - config-update: `dots update` orchestration, weekly auto-clean, `dots clean` - system-doctor: `dots doctor` read-only diagnostics + remediation hints - cli-utilities: the 25 standalone cmd/ binaries Documents current truth (warts included: destructive no-backup symlinks, os.Exit error model). Specs are local docs only — not wired into CI. All six pass `openspec validate --strict`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OpenSpec was already initialized in this repo (
openspec/withAGENTS.md,project.md, and a sample change). This PR completes the integration by adopting the spec-driven development policy as the contributor workflow — adapted from ergane's policy todots' Go quality gate.Changes
AGENTS.md— new Spec-Driven Development (OpenSpec) section: route behavioral changes (new commands/components, changed install behavior, new skills/agents/hooks, altered conventions) throughopenspec/first (proposal + spec deltas + tasks), validate with--strict, get approval, implement, and archive into the base specs within the same PR (atomic with squash-merge). Specs stay local docs only — never wired into CI.openspec/project.md— matching OpenSpec note.README.md— Spec-Driven Development subsection under Development.Quality gate
Docs-only change (so no change folder required per the policy itself). Full Pre-Completion Checklist run green:
go install,revive,go test ./..., skill tests, skill linter,qlty check.🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com