mirror of
https://github.com/github/awesome-copilot.git
synced 2026-07-21 21:04:13 +00:00
Jenny Ferries
bb838b0463
The Workshop puts long-running AI agents (desks) in the same room, on the same work, each with its own memory and history, sharing one workspace so you direct the work instead of relaying it. Components: - Workshop TA agent (room coordinator) - Skills: desk-open, desk-journal, signal-write, bench-read - Marketplace entry for one-command install Install: copilot plugin install the-workshop@awesome-copilot Complements Ember (partnership for one agent) with coordination for many agents. Install both for the full stack. Source: https://github.com/jennyf19/the-workshop Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 26faf13e-639c-4a21-ac05-c0dc2bff7c62
65 lines
1.9 KiB
Markdown
65 lines
1.9 KiB
Markdown
---
|
|
name: desk-open
|
|
description: 'Create and open a new desk in the workshop. Sets up the folder structure, initial journal, and desk identity so the next session that sits down finds the trail.'
|
|
---
|
|
|
|
# Open a Desk
|
|
|
|
Create a new desk in the workshop with the standard structure.
|
|
|
|
## When to use
|
|
|
|
- The operator wants to start a new workstream
|
|
- Work arrives that doesn't belong to any existing desk
|
|
- A topic needs its own frame (its own history, its own priors)
|
|
|
|
## What it creates
|
|
|
|
Given a workshop directory and a desk name, create:
|
|
|
|
```
|
|
desks/<desk-name>/
|
|
journal.md # persistent memory — read at start, written at end
|
|
```
|
|
|
|
## How to use
|
|
|
|
1. **Choose a name.** Short, descriptive, kebab-case. The name is
|
|
how the operator and other desks refer to this desk.
|
|
Examples: `security-scan`, `api-review`, `ops`, `cloud-workshop`
|
|
|
|
2. **Create the structure.** Make the directory and initial journal:
|
|
|
|
```
|
|
desks/<desk-name>/journal.md
|
|
```
|
|
|
|
3. **Write the first journal entry.** The journal starts with:
|
|
- What this desk is for (its focus/purpose)
|
|
- What repos or work it covers (if applicable)
|
|
- Any initial context the first session needs
|
|
|
|
4. **Announce it.** Tell the operator what was created and what
|
|
the desk's focus is.
|
|
|
|
## Journal format
|
|
|
|
```markdown
|
|
# <Desk Name> — Journal
|
|
|
|
## <date> — Desk opened
|
|
- **Purpose:** <what this desk focuses on>
|
|
- **Scope:** <repos, areas, or work this desk covers>
|
|
- **Next step:** <what the first session should do>
|
|
```
|
|
|
|
## Principles
|
|
|
|
- A desk is a peer, not a sub-agent. It has equal standing to
|
|
disagree with other desks.
|
|
- The journal is the memory. Without it, the next session starts
|
|
blind. Write enough that someone starting from zero finds the way.
|
|
- One desk, one focus. If the scope is too broad, open two desks.
|
|
Each desk's value comes from its specific frame — dilute the
|
|
frame and you lose the value.
|