# OpenSpec Conventions — using-cash-app Every change to this codebase starts as an OpenSpec proposal. Code without a linked, merged proposal is not accepted. ## How to propose a change 1. Create `openspec/changes//proposal.md` 2. Describe: what changes, why, acceptance criteria, and any spec deltas to `openspec/project.md` or `openspec/capabilities/` 3. Run `openspec validate` — must pass before review 4. Self-review (for solo changes) or request Engineer review 5. Merge the proposal; add `.complete` file to the change directory 6. Implement the code change referencing the proposal slug in commits ## Validation gate `openspec validate` is run in CI. PRs fail if validation does not pass. ## Archive flow Completed changes stay in `openspec/changes/` indefinitely for audit trail. Add `.complete` to mark done. ## Naming convention Change slugs: `-` e.g. `scaffold-app`, `add-wallet-connection`, `add-pl-report`