Start using OpenSpec for Braid

cmoriarty commented

2026-09-13 16:07:31 -04:00

Owner

This project has been mostly done without a good process, despite that being the main mission of braid. We did some dogfood experiments to try and use a bit better process to develop, but I'm finding that many requests that have been made have not been fulfilled.

The main process will be that Forgejo tickets should be passed to Openspec explore, and then ushered through the whole process until archive.

This project has been mostly done without a good process, despite that being the main mission of braid. We did some dogfood experiments to try and use a bit better process to develop, but I'm finding that many requests that have been made have not been fulfilled. The main process will be that Forgejo tickets should be passed to Openspec explore, and then ushered through the whole process until archive.

cmoriarty referenced this issue from a commit

2026-09-13 17:21:23 -04:00

chore(openspec): Braid is developed through OpenSpec, from Forgejo issue to archive

cmoriarty closed this issue

2026-09-13 17:21:23 -04:00

cmoriarty commented

2026-09-13 17:21:42 -04:00

Author

Owner

OpenSpec is now initialized on this repository, in 2624771.

openspec init (OpenSpec 1.10.0, spec-driven schema) with the Claude Code tooling: the /opsx:explore, /opsx:propose, /opsx:apply, /opsx:sync, /opsx:update and /opsx:archive commands, and their skills, under .claude/.
openspec/config.yaml holds the project context every artifact is written against: what Braid is, the stack, the conventions (commit style, UI code style, a test with every behaviour change), the verification commands, and the process.
CLAUDE.md states the process for every session. A Forgejo issue is explored, proposed (proposal, specs, design, tasks), applied, verified (including a real browser for UI work) and archived. Its issue then gets a comment on what shipped and is closed.
Two artifact rules: a proposal links the issue it came from, and a change that touches ui/ has its own Playwright verification task.

openspec/specs/ starts empty; the specs accumulate as changes are archived. #6 is the first issue going through this process.

OpenSpec is now initialized on this repository, in 2624771. - **`openspec init`** (OpenSpec 1.10.0, `spec-driven` schema) with the Claude Code tooling: the `/opsx:explore`, `/opsx:propose`, `/opsx:apply`, `/opsx:sync`, `/opsx:update` and `/opsx:archive` commands, and their skills, under `.claude/`. - **`openspec/config.yaml`** holds the project context every artifact is written against: what Braid is, the stack, the conventions (commit style, UI code style, a test with every behaviour change), the verification commands, and the process. - **`CLAUDE.md`** states the process for every session. A Forgejo issue is explored, proposed (proposal, specs, design, tasks), applied, verified (including a real browser for UI work) and archived. Its issue then gets a comment on what shipped and is closed. - **Two artifact rules:** a proposal links the issue it came from, and a change that touches `ui/` has its own Playwright verification task. `openspec/specs/` starts empty; the specs accumulate as changes are archived. #6 is the first issue going through this process.

cmoriarty referenced this issue

2026-09-29 01:27:40 -04:00

A repository with no .gitignore gets one for its stack: from the proposal, or from its files before the first code commit #107

Rows
Columns

Start using OpenSpec for Braid #8