docs(the-workshop): fix workshop scaffold, bench location, and component list

Address the remaining doc/skill review findings:
- workshop-create: 'gh repo create --clone' clones into the CWD, which
  nests the new repo when run from inside a checkout. Add an explicit
  clone-parent selection + 'rev-parse --is-inside-work-tree' guard, and
  run the create from that parent.
- workshop-create: desks/ and bench/ were scaffolded empty, so Git drops
  them and a later clone loses the scaffold. Scaffold .gitkeep in each
  and commit the placeholders.
- bench-read: make <workshop>/bench/ the primary shared location (the
  directory workshop-create actually establishes) with desk-local
  artifacts as a secondary source, instead of treating the repo root as
  the bench.
- the-workshop README: add the Workshop Create skill to the component
  table so all six packaged components are documented.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 26faf13e-639c-4a21-ac05-c0dc2bff7c62
This commit is contained in:
jennyf19
2026-07-18 19:56:18 -07:00
parent f9061f6fcc
commit fa1f154155
3 changed files with 36 additions and 17 deletions
+14 -9
View File
@@ -17,10 +17,11 @@ leave work products for each other.
## What the bench is
The bench is the shared filesystem of the workshop. It's not a
The bench is `<workshop>/bench/` — the shared workspace directory
that `workshop-create` establishes for cross-desk work. It's not a
message queue or a chat channel — it's files. When Desk A produces
a finding and Desk B needs to review it, the finding is a file
on the bench. When the operator asks "what did the scanning desk
in `bench/`. When the operator asks "what did the scanning desk
find?" — you read the bench.
Typical bench artifacts:
@@ -31,15 +32,19 @@ Typical bench artifacts:
## Where to look
The bench is the workshop directory itself and its subdirectories.
Common patterns:
The primary shared location is the `bench/` directory at the
workshop root — the designated cross-desk workspace. Desk-local
artifacts under `desks/<desk-name>/` are a secondary source: read
them when you need a specific desk's own work, but shared artifacts
belong in `bench/`.
```
desks/<desk-name>/ # each desk's own workspace
journal.md # the desk's memory
<artifacts> # work products from this desk
<shared files at root> # cross-desk artifacts
<workshop>/
bench/ # PRIMARY — shared cross-desk artifacts
<findings, verdicts, drafts, reports>
desks/<desk-name>/ # secondary — a desk's own workspace
journal.md # the desk's memory
<artifacts> # work still local to this desk
```
## How to read