Add Issue Designer instruction packages
Check instruction packages / check (push) Successful in 5s
Check instruction packages / check (pull_request) Successful in 4s

This commit is contained in:
admin committed 2026-11-04 20:21:54 -05:00
1 parent ea94dc877e
commit a3928187b9
21 files changed
+256 -2

No files matched your search

+4
View File
@@ -8,6 +8,10 @@ Public source for RelayView-maintained instruction-only role skills and an illus
| --- | --- | --- | --- |
| `packages/planner-scope` | Maintained default | Planner / planning | 0.2.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 |
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "cfb72adc02cf0a488c341d965c16e22d22e90c52ab0540a9072b09c592d1abd7"
}
]
}
+12
View File
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "431da86a21da7b74fa55bce36c1e0fc806d066cd8b1ace7a784e1eb4a2db4a89"
}
]
}
+12
View File
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "3898ccf2566614ac3fc54afadd857ebd1e61701d0fe1344b92f79f6b01278706"
}
]
}
+12
View File
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "676c4291d4bab19c76c0d945eefe21aa6787783e4e2d2285e0d6e270303d1e94"
}
]
}
+12
View File
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "c4b8707f88faf1b9f3e04bb707b45bbb3d89848a8a3b2ac807dc819e8dd29f91"
}
]
}
+12
View File
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "561db3543cfdffe55b8002954d7debcf9d0fc1125d51c688a74cf2469d3d73a1"
}
]
}
+12
View File
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "fa62a0806921d87ddd27e494cfc379513cc147ad658eb5a2981970ccb25babf5"
}
]
}
+12
View File
@@ -0,0 +1,12 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "c5b5db0755af497cfe9be9fee9912f1406fb3b8546d7f389998516ba298f27b0"
}
]
}
+15
View File
@@ -0,0 +1,15 @@
---
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.
@@ -0,0 +1,15 @@
{
"schemaVersion": 1,
"source": {
"kind": "first-party",
"reference": "v0.6.0"
},
"role": "designer",
"step": "design",
"files": [
{
"path": "SKILL.md",
"sha256": "5e5b407b8390edc24f365e509e1da607bdbed918ffed07f4b2c03eb6bc0d8e80"
}
]
}
+5 -1
View File
@@ -39,7 +39,11 @@ class PackageTests(unittest.TestCase):
"code-review": ("reviewer", "review"),
"c4-diff": ("reviewer", "review"),
"research": ("planner", "planning"),
"improve-codebase-architecture": ("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")}}
for name, role_step in expected.items():
with self.subTest(name=name):
package = ROOT / "packages" / name
+1 -1
View File
@@ -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")):
if manifest["schemaVersion"] != 1 or (manifest["role"], manifest["step"]) not in (("planner", "planning"), ("implementer", "implementation"), ("reviewer", "review"), ("designer", "design")):
_fail(f"{path}: incompatible role or step")
files = manifest["files"]
if not isinstance(files, list) or not 1 <= len(files) <= 16: