Lesson 08

Ship It

Your toast system works. The last step is to close out the change.

Run this:

/opsx:archive

OpenSpec moves the toast-notifications folder from changes/ to changes/archive/. Your change folder — the proposal, the specs, the design doc, the tasks — is preserved exactly where it is, just marked as done.

openspec/
└── changes/
    └── archive/
        └── toast-notifications/
            ├── .openspec.yaml
            ├── proposal.md
            ├── toast-appearance/
            │   └── spec.md
            ├── toast-lifecycle/
            │   └── spec.md
            ├── design.md
            └── tasks.md

That archive is the record of every decision made during this change — what it was, why it was built this way, what was left out and why. Six months from now, when someone asks why the exit animation works the way it does, the answer is in design.md.

This is the pattern. Proposal, spec, design, tasks, implement, archive. You've done it once end to end. The next change starts the same way — one sentence to /opsx:propose, and the artifacts follow.

The chaos tax doesn't go away entirely. But now your requirements have a home before the first line of code is written. The AI reads them instead of guessing. And when something goes sideways, you have a document to point at — not a chat history.

← Tasks