Releases designer-prototype 0.6.2. The method now has the Designer prepare the scenario itself, then hand the Operator only the app's own commands needed to answer the design question.
Prerequisite for anodyine/relayview#991 (issue anodyine/relayview#955), which bundles `designer-prototype` from tag `v0.6.2` at `a04e3ed`.
## Summary
Releases `designer-prototype` 0.6.2. The method now has the Designer prepare the scenario itself, then hand the Operator only the app's own commands needed to answer the design question.
```diff
packages/designer-prototype/
- SKILL.md # relayview-version: 0.6.0
+ SKILL.md # relayview-version: 0.6.2, + handover checklist
relayview-skill.json # reference v0.6.0 → v0.6.2, new SKILL.md sha256
README.md # designer-prototype row → 0.6.2; + "Write the guidance"
tests/test_packages.py # expects 0.6.2 for designer-prototype
```
The new instructions cover these points:
- Set up the scenario data in the app's default locations under the workspace `HOME`.
- Make the Operator's first command the real one, run by its installed name.
- Add a reset command only when one of the Operator's commands changes the scenario. Put it in `/scratch/bin` and give it by its name.
`README.md` gains questions to ask before writing model-facing guidance.
**Merge with a merge commit, not squash or rebase.** RelayView pins commit `a04e3ed` through tag `v0.6.2`, so that commit must stay reachable from `main`.
## Evidence
- `python3 -m unittest discover -s tests` on `a04e3ed`: 13 tests, OK.
- RelayView's `python3 scripts/verify-first-party-skills-source.py` on relayview `7435adc9`: the bundled copy matches `v0.6.2` at `a04e3ed`.
- Live Designer runs with this method, run by the Operator against Chezmerge:
- session `47a7f49e` (2026-11-13, relayview `cbfe46aa`, this commit): the handover arrived 2m59s after agreement, with no unrequested reset helper;
- sessions `83d597ea` and `72d87437` ran on earlier revisions of the method.
Each run was assessed from the session's recorded tool calls.
## Merge Danger
**Door:** two-way. The change is to instructions only, and the existing `v0.6.0` packages are unchanged.
**Blast Radius:** RelayView uses this text only once #991 bundles it. Other packages are unaffected.
## Reviewer prerequisites
None.
## Manual Test Plan
None. Behavior with a model is covered by #991's manual plan.
## Post-Merge Cleanup
```zsh
git -C ~/Projects/relayview-skills push origin --delete ISSUE-955
```
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The Human answers a prototype's design question by using it as the
software's user will, so the prototype method now has the Designer prepare
the scenario itself and give the Human the real command, syntax and
directory a user would use, with any reset command offered for that
purpose alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A read-only command such as a dry-run leaves nothing to restore, yet naming a
reset command as the example helper led Designers to build one for every
prototype. The method and checklist now ask for a reset command only when a
command the Human will try changes the scenario.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A Designer met the reset-command condition by offering an optional real
update for contrast, then built and debugged a reset helper for it. The
method now gives the Human only the commands needed to answer the design
question, and asks for a reset command only when one of those changes the
scenario.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Prerequisite for anodyine/relayview#991 (issue anodyine/relayview#955), which bundles
designer-prototypefrom tagv0.6.2ata04e3ed.Summary
Releases
designer-prototype0.6.2. The method now has the Designer prepare the scenario itself, then hand the Operator only the app's own commands needed to answer the design question.The new instructions cover these points:
HOME./scratch/binand give it by its name.README.mdgains questions to ask before writing model-facing guidance.Merge with a merge commit, not squash or rebase. RelayView pins commit
a04e3edthrough tagv0.6.2, so that commit must stay reachable frommain.Evidence
python3 -m unittest discover -s testsona04e3ed: 13 tests, OK.RelayView's
python3 scripts/verify-first-party-skills-source.pyon relayview7435adc9: the bundled copy matchesv0.6.2ata04e3ed.Live Designer runs with this method, run by the Operator against Chezmerge:
47a7f49e(2026-11-13, relayviewcbfe46aa, this commit): the handover arrived 2m59s after agreement, with no unrequested reset helper;83d597eaand72d87437ran on earlier revisions of the method.Each run was assessed from the session's recorded tool calls.
Merge Danger
Door: two-way. The change is to instructions only, and the existing
v0.6.0packages are unchanged.Blast Radius: RelayView uses this text only once #991 bundles it. Other packages are unaffected.
Reviewer prerequisites
None.
Manual Test Plan
None. Behavior with a model is covered by #991's manual plan.
Post-Merge Cleanup
🤖 Generated with Claude Code