Community schema: specwright

Open Beginner friendly
  • Is something wrong?
#2,187 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The change belongs in the "Community Schemas" section of docs/customization.md, in the table and under the note that asks for a repository link and a one-line description. Read the existing rows to match their format, then add a row for specwright with the maintainer, repository link and description from the issue. Done means the row renders in the table and the repository link resolves. Whether the description should be trimmed to the one-line style of the other rows is for the maintainers to decide.

Written by the indexing model from the issue text.

Description

documentation needs-triage
Where

https://github.com/Fission-AI/OpenSpec/blob/main/docs/customization.md, "Community Schemas" section

What is wrong or missing

The Community Schemas table has no row for specwright, a community schema with architecture-tiered designs and a cross-model review gate. The note under the table says to open an issue with a repository link and a one line description, so here it is.

Repository: https://github.com/sh1ny/specwright/tree/main/schemas/specwright (MIT)

The schema works on its own, but it is designed to run with Specwright's companion skills (branch per change, commit per task, pre-ship review, GitHub PR workflow, milestone roadmaps). The repository README has a single install prompt that sets up both.

What it should say instead
Schema Maintainer Repository Description
specwright @sh1ny sh1ny/specwright Architecture-tiered workflow. Flow: proposal → specs → design → review → tasks → apply. design opens with a six-trigger triage: LIGHT (a few lines) when nothing triggers, FULL (state ownership, failure visibility, resource bounds, flow gaps, mechanism ledger) otherwise. FULL designs get a fresh-context, ideally cross-model review whose VERDICT: line gates tasks; LIGHT records SKIPPED_LIGHT. Every requirement carries a failure scenario mapped to a named red/green test, and durable decisions become immutable, supersedable ADRs. Companion skills add branch-per-change git, a pre-ship review, a GitHub PR workflow and milestone roadmaps.
Dominant language
TypeScript
Stars
73.6k
Forks
5k
Avg merge
3d 20h
Merged PRs (30d)
64

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Fission-AI/OpenSpec

All issues in Fission-AI/OpenSpec

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.