The spec-driven development workspace for osapi-io. Every change is designed here first, then implemented in the repository it belongs to.
This repository holds no product code. It holds the design record and the durable knowledge behind osapi-io: what was agreed before something was built, and why it is built that way.
It is a Spec Kit monorepo, and knowledge sits at one of three levels:
.charter/ rules binding every repository
components/ one project per repository, for how that repository behaves
system/ agreements between repositories: protocols, conventions, the graph
A change is designed here first, reviewed as a pull request, then implemented in
the repository it belongs to. What survives is each project's
.specify/memory/, the standing description of how things behave, which every
later change reads first and keeps honest.
Two things make that worth the overhead. Reviewers read the design on its own, separate from the diff that implements it. And one place describes a change spanning several repositories, instead of scattering it across them.
CONTRIBUTING.md has the workflow, the skills that run it, and the test for which level a change belongs to.
Skills in this repository answer questions that span every repository in the organization, and carry the operational knowledge for working in them.
None of them lists what it describes. org-status takes the repository list
from GitHub on each run, and add-a-domain resolves its reference domain from
the codebase, so both stay correct as repositories and layers come and go. An
inventory written into a skill is right the day it is written and wrong after
the next change, with nothing marking the moment.
| Skill | Answers |
|---|---|
| org-status | Open pull requests, Dependabot bumps, security alerts, and whether CI is green across osapi-io |
| add-a-domain | Adding an osapi domain: the provider and every layer it has to appear in, in the order that avoids rework |
Each follows the Agent Skills format: a slim SKILL.md that routes, with the
detail in reference files an agent reads only when the question calls for them.
CONTRIBUTING.md covers prerequisites, setup, how to operate Spec Kit here, and the PR workflow. The Spec Kit repository documents the tool itself.
See the Contributing guide for prerequisites, setup, conventions, and the PR workflow.
The MIT License.