Submit a framework or project

The observatory runs on community submissions and community tracking. Everything is a Markdown file in a public repo — you can open a structured issue and let a maintainer add it, or send the file yourself as a pull request. Repository metrics are fetched automatically once your entry is merged; you never need to fill in stars or commit counts.

Submissions use GitHub and require a free GitHub account. The structured issue forms usually take 5–10 minutes; you do not need to edit code or know YAML.

Inclusion criteria

Frameworks need a publicly documented, usable-today methodology for driving AI-assisted development from specifications — public docs, and ideally a public repo.
Projects need a public repository with observable spec artifacts in-tree (a spec directory that can be watched over time). Real projects are strongly preferred over demos; a vendor's own showcase is acceptable when labeled as such.
Every claim on a page should be verifiable from a linked public source.

Submit a framework

Answer a short set of questions about the framework and include links that let maintainers verify it.

Open the framework issue form

Submit a framework via pull request

Create src/content/frameworks/<slug>.md in a fork and open a pull request using this template:

---
name: Framework Name
website: https://example.com/
repo: owner/name            # omit if there is no public repo
summary: >-
  One-sentence description shown on cards.
coreApproach: >-
  One or two sentences on the methodology.
workflow:
  - "`/step-one` — as the framework's own docs define it (backticks render as code)"
  - "Step 2 — ..."
supportedTools:
  - Claude Code
  - Cursor
maturity: emerging          # experimental | emerging | established | mature
strengths:
  - "..."
limitations:
  - "..."
added: 2026-09-01
lastReviewed: 2026-09-01
featured: false
---

Optional free-form analysis notes go here.

Submit a project

Share the public repository, the framework it uses, and where its specification artifacts live.

Open the project issue form

Submit a project via pull request

Create src/content/projects/<slug>.md in a fork and open a pull request. The three ## body sections are required (write "Not yet assessed." where honest).

---
name: Project Name
repo: owner/name
framework: openspec         # slug of a framework file in src/content/frameworks/
summary: >-
  One-sentence description of what the project is.
status: active              # active | paused | archived
specStructure:
  location: openspec/       # where the spec artifacts live in the repo
  formats:
    - Markdown
  notes: >-
    What's inside the spec directory.
drift: unknown              # none | low | moderate | high | unknown
timeline:
  - date: 2026-09-01
    title: Framework adopted
    description: First commit to the spec directory.
added: 2026-09-01
lastReviewed: 2026-09-01
---

## Spec-to-code drift

What you observed, with dates. "Not yet assessed." is fine.

## Defects and rework

Not yet assessed.

## Maintenance outcomes

Not yet assessed.

Help with tracking

Just as valuable as new entries: pick an existing page whose "last reviewed" date has gone stale, re-check the project against its spec directory, and send a PR updating the drift rating, the narrative sections, and lastReviewed. See the methodology for how ratings are defined.

Found an incorrect or stale entry? Report a correction with the page URL, what should change, and a public source that supports the correction.