Add rapoport-prose schema to Schemas & Extensions#1
Open
paveliko wants to merge 1 commit into
Open
Conversation
Prose-style OpenSpec custom schema bundle published at github.com/rapoport-studio/rapoport.studio. Four artifacts (proposal + design + tasks + verification), no `specs/` deltas. Inserted alphabetically between openspec-spec-driven-superpowers and SuperSpec.
mipmip
requested changes
May 18, 2026
Contributor
mipmip
left a comment
mipmip
left a comment
There was a problem hiding this comment.
Sounds interesting but the link gives a 404. Please fix this.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds rapoport-prose to the Schemas & Extensions section.
What it is
A prose-style OpenSpec custom schema bundle used in production at Rapoport Studio. Each change is four markdown artifacts (
proposal.md+design.md+tasks.md+verification.md) rather than the built-in delta-stylespec-drivenshape — capability specs inopenspec/current/are amended in place at archive time, not delta-restructured during proposals.Inserted alphabetically between
openspec-spec-driven-superpowersandSuperSpec.Verified against
1.3.1—openspec schemaslistsrapoport-prose (project),openspec schema validate rapoport-proseexits 0,openspec listparses tasks-completion counts per the schema.openspec/schemas/rapoport-prose/without anopenspec/config.yaml.How it differs from existing entries
specs/deltasThe differentiator is the absence of a
specs/artifact entirely — capability spec amendments happen againstopenspec/current/*.mdfiles at archive time using the live-amendment pattern documented in the source repo'sopenspec/AGENTS.md.Trying it