Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
 admin
|
09f70fd203 |
No files matched your search
@@ -6,12 +6,8 @@ Public source for RelayView-maintained instruction-only role skills and an illus
|
||||
|
||||
| Directory | Status | Role / step | Version |
|
||||
| --- | --- | --- | --- |
|
||||
| `packages/planner-scope` | Maintained default | Planner / planning | 0.2.0 |
|
||||
| `packages/planner-scope` | Maintained default | Planner / planning | 0.3.0 |
|
||||
| `packages/implementer-handoff` | Maintained default | Implementer / implementation | 0.2.0 |
|
||||
| `packages/issue-designer-default` | Maintained default | Designer / design | 0.6.0 |
|
||||
| `packages/designer-wayfinder`, `designer-grilling`, `designer-prototype` | Optional manual guidance | Designer / design | 0.6.0 |
|
||||
| `packages/designer-research`, `designer-domain-modeling`, `designer-triage` | Optional manual guidance | Designer / design | 0.6.0 |
|
||||
| `packages/designer-to-spec`, `designer-to-tickets` | Optional manual guidance | Designer / design | 0.6.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 |
|
||||
@@ -33,7 +29,7 @@ Public source for RelayView-maintained instruction-only role skills and an illus
|
||||
| `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 Planner and Implementer defaults remain available alongside the pinned Issue Designer default. User forks are maintained by their publishers. This release uses the instruction package schema version 1 admitted by RelayView's Community MVP. It contains only `SKILL.md`, declared `.md`/`.txt` resources, and `relayview-skill.json` within each package. 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.
|
||||
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. This release uses the instruction package schema version 1 admitted by RelayView's Community MVP. It contains only `SKILL.md`, declared `.md`/`.txt` resources, and `relayview-skill.json` within each package. 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
|
||||
|
||||
@@ -52,7 +48,7 @@ The screenshot's ordered manual members come from this excerpt under `trustedSki
|
||||
members: [code-review, c4-diff]
|
||||
```
|
||||
|
||||
The maintained defaults are original RelayView packages. Some optional guidance adapts earlier MIT-licensed skills; see the [third-party notices](NOTICE.md).
|
||||
The two maintained defaults are original RelayView packages. Some optional guidance adapts earlier MIT-licensed skills; see the [third-party notices](NOTICE.md).
|
||||
|
||||
## Fork the starter
|
||||
|
||||
@@ -66,9 +62,9 @@ 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. For Planner, Implementer, or Reviewer guidance, 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. For an optional Designer method, declare its ID and relative `SKILL.md` path in `trustedSkills.catalog`, list the ID in `workflowPresets.designerSkills`, and restart the owner. Designer has no Settings import or set selector for this assignment. These assignments affect future sessions; existing sessions retain their captured bytes. The owner's admission remains authoritative even when these local checks pass.
|
||||
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 use a maintained Planner or Implementer 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 a Planner or Implementer future assignment. RelayView pins and assigns the Issue Designer default automatically; its optional methods use `workflowPresets.designerSkills`. Planner guidance uses existing read and planning tools; Implementer guidance uses existing implementation and reporting tools. Guidance selection does not change a role's tools, credentials, lifecycle stages, validation requirements, Gitea effects, review, merge, or Human acceptance. The owner keeps the existing Gitea task workflow.
|
||||
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. Neither selection changes a role's tools, credentials, lifecycle stages, validation requirements, Gitea effects, review, merge, or Human acceptance. The owner keeps the existing Gitea task workflow.
|
||||
|
||||
## Release identity
|
||||
|
||||
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-domain-modeling
|
||||
description: Sharpen project terms, invariants, and boundaries for an issue draft.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer domain modeling
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# Domain modeling
|
||||
|
||||
Read the assigned project's current context and relevant authoritative contracts. Name concepts in the project's own vocabulary; identify identities, state transitions, invariants, and boundaries that the proposed work touches. Ask the Human when a term or invariant changes acceptance. Put the resulting definitions and open choices in the draft without claiming a repository document was edited.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "cfb72adc02cf0a488c341d965c16e22d22e90c52ab0540a9072b09c592d1abd7"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-grilling
|
||||
description: Stress test one proposed issue design through focused Human questions.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer grilling
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# Grilling
|
||||
|
||||
State the design and scope to be challenged and seek the Human's agreement before entering this method. Probe one consequential assumption at a time: behavior, boundary, dependency, failure, or verification. Use each answer to choose the next question. Stop when the important branches are resolved or explicitly left open; summarize the agreed design and open decisions in the draft.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "431da86a21da7b74fa55bce36c1e0fc806d066cd8b1ace7a784e1eb4a2db4a89"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-prototype
|
||||
description: Plan a bounded throwaway prototype to answer a design question.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer prototype
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# Prototype
|
||||
|
||||
Propose the exact question, bounded code or data scope, expected preview or data effects, and limits to the Human before entering this method. Use only owner-admitted prototype controls after agreement. Treat observations as evidence about the question, not production behavior. Record what was tried, observed, and still uncertain; keep throwaway changes out of the issue's implementation claim.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "3898ccf2566614ac3fc54afadd857ebd1e61701d0fe1344b92f79f6b01278706"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-research
|
||||
description: Research a design question using admitted repository, tracker, and public sources.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer research
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# Research
|
||||
|
||||
Frame the question and the decision it informs. Prefer current primary sources and the assigned repository's authoritative documents. Use only the owner's assigned repository, tracker, and brokered public research tools and active request budget. For each conclusion, keep source, observation time, and completeness visible. Distinguish a source statement from your inference and record material gaps in the draft.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "676c4291d4bab19c76c0d945eefe21aa6787783e4e2d2285e0d6e270303d1e94"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-to-spec
|
||||
description: Turn an agreed problem into a complete reviewable issue specification.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer to spec
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# To spec
|
||||
|
||||
Use the agreed problem and observed project contracts to draft an outcome, scope boundaries, acceptance observations, failure and recovery behavior, and open decisions. Check prerequisites against the assigned tracker and mark uncertain links as proposed. Save the complete text through the owner-stored draft. The Human decides readiness and publication.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "c4b8707f88faf1b9f3e04bb707b45bbb3d89848a8a3b2ac807dc819e8dd29f91"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-to-tickets
|
||||
description: Decompose an agreed specification into ordered issue proposals.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer to tickets
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# To tickets
|
||||
|
||||
Choose independently reviewable slices with observable outcomes and prerequisite edges only where one slice truly requires another. For each proposed issue, state scope, acceptance, verification, and context a cold-start agent needs. Present the ordered set and relationship rationale to the Human. Keep proposals private until Human review and owner publication.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "561db3543cfdffe55b8002954d7debcf9d0fc1125d51c688a74cf2469d3d73a1"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-triage
|
||||
description: Classify and route an observed issue before drafting work.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer triage
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# Triage
|
||||
|
||||
Observe the current report and related tracker state. Separate verified symptoms, missing information, proposed behavior, and duplicate or prerequisite work. Suggest the smallest useful next state and explain the evidence for it. Draft an issue or question for Human review; only owner controls can change tracker status or placement.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "fa62a0806921d87ddd27e494cfc379513cc147ad658eb5a2981970ccb25babf5"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,12 +0,0 @@
|
||||
---
|
||||
name: designer-wayfinder
|
||||
description: Map an uncertain design decision into options and a Human choice.
|
||||
disable-model-invocation: true
|
||||
metadata:
|
||||
relayview-display-name: Designer Wayfinder
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# Wayfinder
|
||||
|
||||
Use this method for a decision whose alternatives materially change the work. First describe the decision, why it matters, and the bounded scope to the Human; enter the method only after the Human agrees. Observe current facts, list viable options with consequences and reversibility, and ask the smallest question that separates them. Record the Human's decision and remaining uncertainty in the owner-stored draft when relevant. This is decision work, not a ready implementation claim.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "c5b5db0755af497cfe9be9fee9912f1406fb3b8546d7f389998516ba298f27b0"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -1,15 +0,0 @@
|
||||
---
|
||||
name: issue-designer-default
|
||||
description: Guide ordinary Issue Designer Chats from observed facts to a reviewable draft.
|
||||
metadata:
|
||||
relayview-display-name: Issue Designer default
|
||||
relayview-version: 0.6.0
|
||||
---
|
||||
|
||||
# Issue Designer default
|
||||
|
||||
Check current facts before drafting. Read the assigned repository's relevant authoritative documentation, code, tests, and tracker observations; state the source, observation time, and any incomplete read. Keep proposed behavior separate from verified current behavior.
|
||||
|
||||
Choose the scale with the Human: one issue for bounded work, an ordered issue set for dependent work, or a narrower question when the outcome is unclear. Ask only for decisions that change scope, acceptance, or authority. A useful draft states the problem, observable outcome, boundaries, prerequisites, and verification including failure behavior. Preserve unresolved choices explicitly.
|
||||
|
||||
Use the owner-stored draft for the current issue. Before calling it ready, check that a new agent can start from the draft and available repository context without this Chat: dependencies and acceptance observations are named, assumptions are visible, and the proposed readiness matches the remaining uncertainty. The Human reviews and publishes through owner controls.
|
||||
@@ -1,15 +0,0 @@
|
||||
{
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.6.0"
|
||||
},
|
||||
"role": "designer",
|
||||
"step": "design",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "5e5b407b8390edc24f365e509e1da607bdbed918ffed07f4b2c03eb6bc0d8e80"
|
||||
}
|
||||
]
|
||||
}
|
||||
@@ -3,7 +3,7 @@ name: planner-scope
|
||||
description: Check assigned issue scope, neighboring work, and verification before drafting a Plan.
|
||||
metadata:
|
||||
relayview-display-name: Planner scope
|
||||
relayview-version: 0.2.0
|
||||
relayview-version: 0.3.0
|
||||
---
|
||||
|
||||
# Planner scope
|
||||
@@ -13,3 +13,5 @@ When drafting the assigned Plan, identify the requested behavior, its boundary,
|
||||
If the owner supplies an admitted work-item identity, use the assigned read tools to inspect it. Preserve source attribution; an issue description is a request, not evidence that its proposed behavior exists. Where tracker access is unavailable, state the missing context instead of guessing a work-item identity.
|
||||
|
||||
Write the Plan through the owner's assigned planning interface. The Plan is ready when each requested outcome has an implementation boundary and a checkable success or recovery observation. Owner-controlled workflow stages and checks determine execution authority.
|
||||
|
||||
For a linked Gitea issue, the default claim is the owner's transition from `status/ready-for-agent` to `status/in-progress` after it proves that the exact Plan reached the Implementer. Finalize the Plan through the assigned interface, then use owner-reported handoff and issue-claim outcomes when explaining progress to the Human. An accepted Plan alone does not establish that claim. The operator may disable or replace the status transition through owner policy; follow the effective policy recorded for the task.
|
||||
@@ -2,14 +2,14 @@
|
||||
"schemaVersion": 1,
|
||||
"source": {
|
||||
"kind": "first-party",
|
||||
"reference": "v0.2.0"
|
||||
"reference": "v0.4.0"
|
||||
},
|
||||
"role": "planner",
|
||||
"step": "planning",
|
||||
"files": [
|
||||
{
|
||||
"path": "SKILL.md",
|
||||
"sha256": "31399ba322d8a4d3ed9814e7fd5d54883b4773c5b7dc3a241b8e14f8f7c16072"
|
||||
"sha256": "bfac8352adffa8e2aaa246a6b5f11a333045a82aeefe5d0e42e76eaa776a6a70"
|
||||
},
|
||||
{
|
||||
"path": "scope.md",
|
||||
|
||||
+2
-24
@@ -12,24 +12,6 @@ ROOT = Path(__file__).resolve().parents[1]
|
||||
|
||||
|
||||
class PackageTests(unittest.TestCase):
|
||||
def test_designer_release_modes_and_source(self):
|
||||
automatic = "issue-designer-default"
|
||||
manual = (
|
||||
"designer-wayfinder", "designer-grilling", "designer-prototype",
|
||||
"designer-research", "designer-domain-modeling", "designer-triage",
|
||||
"designer-to-spec", "designer-to-tickets",
|
||||
)
|
||||
for name in (automatic, *manual):
|
||||
with self.subTest(name=name):
|
||||
package = ROOT / "packages" / name
|
||||
skill = (package / "SKILL.md").read_text()
|
||||
frontmatter = skill.split("---", 2)[1]
|
||||
self.assertEqual("disable-model-invocation: true" in frontmatter, name in manual)
|
||||
self.assertIn("relayview-version: 0.6.0", frontmatter)
|
||||
manifest = json.loads((package / "relayview-skill.json").read_text())
|
||||
self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.6.0"})
|
||||
check_package(package)
|
||||
|
||||
def test_tdd_is_available_to_owner_started_implementers(self):
|
||||
package = ROOT / "packages/tdd-auto"
|
||||
skill = (package / "SKILL.md").read_text()
|
||||
@@ -57,11 +39,7 @@ class PackageTests(unittest.TestCase):
|
||||
"code-review": ("reviewer", "review"),
|
||||
"c4-diff": ("reviewer", "review"),
|
||||
"research": ("planner", "planning"),
|
||||
"improve-codebase-architecture": ("planner", "planning"),
|
||||
**{name: ("designer", "design") for name in (
|
||||
"issue-designer-default", "designer-wayfinder", "designer-grilling", "designer-prototype",
|
||||
"designer-research", "designer-domain-modeling", "designer-triage",
|
||||
"designer-to-spec", "designer-to-tickets")}}
|
||||
"improve-codebase-architecture": ("planner", "planning")}
|
||||
for name, role_step in expected.items():
|
||||
with self.subTest(name=name):
|
||||
package = ROOT / "packages" / name
|
||||
@@ -87,7 +65,7 @@ class PackageTests(unittest.TestCase):
|
||||
package = ROOT / "packages" / name
|
||||
manifest = json.loads((package / "relayview-skill.json").read_text())
|
||||
self.assertEqual((manifest["role"], manifest["step"]), (role, step))
|
||||
self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.2.0"})
|
||||
self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.4.0" if name == "planner-scope" else "v0.2.0"})
|
||||
self.assertIn(resource, [item["path"] for item in manifest["files"]])
|
||||
self.assertIn(marker, (package / "SKILL.md").read_text() + (package / resource).read_text())
|
||||
|
||||
|
||||
+1
-1
@@ -51,7 +51,7 @@ def check_package(path):
|
||||
_fail(f"{path}: invalid source")
|
||||
if source["kind"] not in ("first-party", "user") or not isinstance(source["reference"], str) or not re.fullmatch(r"[A-Za-z0-9._:-]{1,128}", source["reference"]):
|
||||
_fail(f"{path}: invalid source identity")
|
||||
if manifest["schemaVersion"] != 1 or (manifest["role"], manifest["step"]) not in (("planner", "planning"), ("implementer", "implementation"), ("reviewer", "review"), ("designer", "design")):
|
||||
if manifest["schemaVersion"] != 1 or (manifest["role"], manifest["step"]) not in (("planner", "planning"), ("implementer", "implementation"), ("reviewer", "review")):
|
||||
_fail(f"{path}: incompatible role or step")
|
||||
files = manifest["files"]
|
||||
if not isinstance(files, list) or not 1 <= len(files) <= 16:
|
||||
|
||||
Reference in new issue
Block a user