Public source for RelayView-maintained instruction-only role skills and an illustrative author starter. The proprietary RelayView owner controls workflow stages, role tools, verification, and Human acceptance. A skill guides one assigned role during one step; it does not add tools, credentials, network access, or workflow authority.

Packages and support

Directory	Status	Role / step	Version
`packages/planner-scope`	Maintained default	Planner / planning	0.4.0
`packages/implementer-handoff`	Maintained default	Implementer / implementation	0.2.0
`packages/codebase-design`	Optional guidance	Planner / planning	0.3.0
`packages/grill-me`	Optional guidance	Planner / planning	0.3.0
`packages/grilling`	Optional guidance	Planner / planning	0.3.0
`packages/to-questionnaire`	Optional guidance	Planner / planning	0.3.0
`packages/research`	Optional guidance	Planner / planning	0.3.0
`packages/improve-codebase-architecture`	Optional guidance	Planner / planning	0.3.0
`packages/diagnosing-bugs`	Optional guidance	Implementer / implementation	0.3.0
`packages/domain-modeling`	Optional guidance	Implementer / implementation	0.3.0
`packages/migrate-to-shoehorn`	Optional guidance	Implementer / implementation	0.3.0
`packages/pr`	Optional guidance	Implementer / implementation	0.3.0
`packages/prototype`	Optional guidance	Implementer / implementation	0.3.0
`packages/scaffold-exercises`	Optional guidance	Implementer / implementation	0.3.0
`packages/shared-abstraction-refactor`	Optional guidance	Implementer / implementation	0.3.0
`packages/split-large-files`	Optional guidance	Implementer / implementation	0.3.0
`packages/tdd`	Optional manual guidance	Implementer / implementation	0.3.0
`packages/tdd-auto`	Optional automatic guidance	Implementer / implementation	0.3.1
`packages/writing-for-agents`	Optional guidance	Implementer / implementation	0.3.0
`packages/code-review`	Optional guidance	Reviewer / review	0.3.0
`packages/c4-diff`	Optional guidance	Reviewer / review	0.3.0
`examples/starter-planner`	Illustrative starter; not a production default	Planner / planning	0.1.0

Only named releases of maintained packages receive RelayView compatibility testing and maintenance. Optional guidance requires explicit role assignment; the two original defaults remain available. User forks are maintained by their publishers. The Planner default uses instruction package schema version 2 for its bounded issue-claim policy; other packages retain version 1. Packages contain only SKILL.md, declared .md/.txt resources, and relayview-skill.json. Scripts, executable files, undeclared files, and requested permissions fail checks and owner admission. There is no fixed release calendar: maintained packages are versioned when their content or compatibility changes. A breaking owner contract requires a new compatible maintained release before the product depends on it.

A named set in RelayView

A named set groups admitted packages for one role and workflow step. In Settings → Skills, the Reviewer has Reviewer inspection on request selected as its manual set. Its saved and effective choices match, so future Reviewer sessions capture these two skills for manual invocation. The automatic selector remains at its configured default, which is empty in this example.

The screenshot's ordered manual members come from this excerpt under trustedSkills.sets in the owner configuration. Both member IDs must also be admitted in trustedSkills.catalog; defining a set makes it available, while selecting and saving it makes it effective for future sessions.

- id: reviewer-inspection
  name: Reviewer inspection on request
  role: reviewer
  step: review
  invocationMode: manual
  members: [code-review, c4-diff]

The two maintained defaults are original RelayView packages. Some optional guidance adapts earlier MIT-licensed skills; see the third-party notices.

Fork the starter

Clone this repository, copy examples/starter-planner to a new directory named for your skill, and edit its SKILL.md and local-guidance.md. Set the frontmatter name to the directory name and give it a distinct version. Keep source.kind as user and set source.reference to your fork's release identifier. Update each files[].sha256 with the SHA-256 of the exact file bytes. Then run:

python -m unittest discover -s tests -v
python -m tools.packages check examples/starter-planner
python -m tools.packages pack examples/starter-planner dist/starter-planner.zip

Replace examples/starter-planner in the last two commands with your package directory. The pack command writes a reproducible ZIP containing the package, LICENSE, and NOTICE.md, then prints its SHA-256. The check returns the owner's package identity digest. Both use only Python 3's standard library and this repository's source. Preserve the license and notice when redistributing the package or fork.

To use a user fork, place its closed package directory under the owner's configured trusted root and use Settings → Skills to import the relative SKILL.md path under a new unique ID. Import validates and records the package; it does not assign it. Add that ID to a role-compatible named set in the owner configuration and restart the owner to load the set. Then select the set for the matching role in Settings → Skills and save. That selection takes effect for future sessions immediately; existing sessions retain their captured bytes. The Settings catalog displays source, version, digest, role, step, and pending versus effective assignment. The owner's admission remains authoritative even when these local checks pass.

To replace the linked-issue claim convention, fork planner-scope as a schema-version-2 Planner package and set issueClaim.statusLabel to another existing status/ label, or to null to disable the claim. Update the package's source reference and file hashes, import it, and select it as the automatic Planner skill for future tasks. The owner validates this declaration and freezes the selected package digest and target with each new linked task. Skill text cannot itself dispatch the Gitea effect.

To use a maintained default, copy its release package under the same trusted root, admit its SKILL.md through the owner catalog, then select it for its declared role in Settings. Settings import accepts user-source packages; configure first-party packages in the owner catalog. Select a fork with source.kind: user and a distinct ID to replace that role's future assignment. Planner guidance uses existing read and planning tools; Implementer guidance uses existing implementation and reporting tools. Skill selection does not change a role's tools, credentials, lifecycle stages, validation requirements, review, merge, or Human acceptance. The owner keeps custody of the Gitea credential and executes only its validated claim policy.

Release identity

A release tag pins public source. CI runs package checks and archives from that source. RelayView's bundled copy records the source tag and commit plus each package identity and file hash, then verifies the bytes in its own focused test. A bundled update creates a new release identity; it does not overwrite a user fork.

The MIT license covers this repository only. The contribution policy is in CONTRIBUTING.md; dependency notices are in NOTICE.md.