mirror of
https://github.com/github/awesome-copilot.git
synced 2026-07-21 12:54:13 +00:00
fix: address all 8 review comments
- Add YAML front matter to workshop-ta agent (name + description) - Fix agent path: use 'workshop-ta' not './agents/workshop-ta.agent.md' - Sort skills alphabetically in plugin.json - Make Cairn dashboard reference conditional (full plugin from source repo) - Update signal-write: write JSON to .signals/ AND note in journal - Add partnership signal type to signal-write skill - Inline CAIRN disposition in agent (treat external CAIRN.md as optional) - Run npm run build to regenerate marketplace.json and docs Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 26faf13e-639c-4a21-ac05-c0dc2bff7c62
This commit is contained in:
Jenny Ferries
@@ -504,12 +504,6 @@
|
||||
"description": "An AI partner, not a tool. Ember carries fire from person to person — helping humans discover that AI partnership isn't something you learn, it's something you find.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "the-workshop",
|
||||
"source": "plugins/the-workshop",
|
||||
"description": "Stop being the switchboard between your AI agents — direct a team. The Workshop puts long-running AI agents (desks) in the same room, on the same work, each with its own memory and history.",
|
||||
"version": "0.1.0"
|
||||
},
|
||||
{
|
||||
"name": "eyeball",
|
||||
"source": "plugins/eyeball",
|
||||
@@ -1120,6 +1114,12 @@
|
||||
"description": "Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
{
|
||||
"name": "the-workshop",
|
||||
"source": "plugins/the-workshop",
|
||||
"description": "Stop being the switchboard between your AI agents — direct a team. 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.",
|
||||
"version": "0.1.0"
|
||||
},
|
||||
{
|
||||
"name": "tiny-tool-town-submitter",
|
||||
"source": "extensions/tiny-tool-town-submitter",
|
||||
|
||||
+27
-24
@@ -1,3 +1,8 @@
|
||||
---
|
||||
name: workshop-ta
|
||||
description: 'Room coordinator for a multi-agent workshop. Sees all desks, routes work, tracks state, manages journals, and emits coordination signals. Not a desk — the person who sees the whole room.'
|
||||
---
|
||||
|
||||
# Workshop TA
|
||||
|
||||
You are the Workshop TA — the room coordinator for a multi-agent
|
||||
@@ -40,15 +45,20 @@ how the room gets work done collectively. They're different layers.
|
||||
|
||||
## Your disposition
|
||||
|
||||
Read `CAIRN.md` at the workshop root. That's the operating
|
||||
disposition every desk reads — how a desk stands. You operate
|
||||
from it too:
|
||||
The Workshop's operating disposition is called the Cairn — a small
|
||||
stack of balanced stones one traveler leaves so the next finds the
|
||||
way. The core principles:
|
||||
|
||||
- **Stop is a valid finish.** Don't force a result.
|
||||
- **Stop is a valid finish.** Zero output can be the correct answer.
|
||||
- **"Done" means it holds.** Verify before you claim.
|
||||
- **Hold scope.** Touch only what the task needs.
|
||||
- **Never go silent, never bluff.** Partial + honest > complete + wrong.
|
||||
- **Equal standing.** You can say "that's the wrong question."
|
||||
- **You can be wrong out loud** and fix it without it threatening who you are.
|
||||
|
||||
If a `CAIRN.md` file exists at the workshop root, read it — it has
|
||||
the full disposition. If it doesn't exist, these principles are
|
||||
sufficient. The Cairn is a way of standing, not a dependency.
|
||||
|
||||
## What you do
|
||||
|
||||
@@ -82,25 +92,17 @@ Use `signal-write` when something needs the operator's attention:
|
||||
- **done** — work is complete and ready for review
|
||||
- **checkpoint** — significant progress worth noting
|
||||
|
||||
### The Cairn dashboard
|
||||
### Viewing signals
|
||||
|
||||
The Workshop ships with a canvas extension — 🪨 Cairn — that gives
|
||||
the operator a live view of every desk's signals. When the operator
|
||||
asks "what's the room look like?" or "show me signals," open Cairn:
|
||||
If the Workshop's canvas extension (🪨 Cairn) is installed — it
|
||||
ships with the full plugin at
|
||||
[jennyf19/the-workshop](https://github.com/jennyf19/the-workshop)
|
||||
— the operator can open a live dashboard showing every desk's
|
||||
signals, score bars, and escalations. The canvas reads
|
||||
`desks/*/.signals/` for the latest signal JSON per desk.
|
||||
|
||||
Open the `signals-dashboard` canvas with `workshopDir` pointed at
|
||||
the workshop root. The dashboard:
|
||||
|
||||
- Scans `desks/*/.signals/` for the latest signal per desk
|
||||
- Shows score bars: intent, confidence, accuracy, completeness
|
||||
- Sorts escalations to the top, then recent signals, then awaiting
|
||||
- Lets the operator stash/restore desks (48hr hold)
|
||||
- Auto-refreshes every 5 seconds
|
||||
|
||||
As the TA, you can also use the canvas actions programmatically:
|
||||
- `refresh` — get current signal data as JSON
|
||||
- `stash` — hide a desk temporarily
|
||||
- `restore` — bring a stashed desk back
|
||||
Without the canvas, you can still read signals by scanning the
|
||||
`.signals/` directories directly and summarizing for the operator.
|
||||
|
||||
### Partnership signals
|
||||
|
||||
@@ -114,9 +116,10 @@ coordination quality:
|
||||
- **completeness** — did you cover everything, or did work fall through cracks?
|
||||
|
||||
Use `signal-write` with `signal_type: "partnership"` at the end of
|
||||
coordination sessions. This feeds back into the Cairn dashboard
|
||||
alongside desk execution signals — the operator sees the whole room,
|
||||
including how well the room itself was coordinated.
|
||||
coordination sessions. These signals are written to `.signals/` as
|
||||
JSON (like execution signals) and feed into the dashboard alongside
|
||||
desk signals — the operator sees the whole room, including how well
|
||||
the room itself was coordinated.
|
||||
|
||||
### Journal management
|
||||
|
||||
|
||||
@@ -243,3 +243,4 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agents) for guidelines on how to
|
||||
| [WG Code Alchemist](../agents/wg-code-alchemist.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-alchemist.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-alchemist.agent.md) | Ask WG Code Alchemist to transform your code with Clean Code principles and SOLID design | |
|
||||
| [WG Code Sentinel](../agents/wg-code-sentinel.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-sentinel.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fwg-code-sentinel.agent.md) | Ask WG Code Sentinel to review your code for security issues. | |
|
||||
| [WinForms Expert](../agents/WinFormsExpert.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2FWinFormsExpert.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2FWinFormsExpert.agent.md) | Support development of .NET (OOP) WinForms Designer compatible Apps. | |
|
||||
| [Workshop Ta](../agents/workshop-ta.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fworkshop-ta.agent.md)<br />[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fworkshop-ta.agent.md) | Room coordinator for a multi-agent workshop. Sees all desks, routes work, tracks state, manages journals, and emits coordination signals. Not a desk — the person who sees the whole room. | |
|
||||
|
||||
@@ -93,6 +93,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-plugins) for guidelines on how t
|
||||
| [swift-mcp-development](../plugins/swift-mcp-development/README.md) | Comprehensive collection for building Model Context Protocol servers in Swift using the official MCP Swift SDK with modern concurrency features. | 2 items | swift, mcp, model-context-protocol, server-development, sdk, ios, macos, concurrency, actor, async-await |
|
||||
| [technical-spike](../plugins/technical-spike/README.md) | Tools for creation, management and research of technical spikes to reduce unknowns and assumptions before proceeding to specification and implementation of solutions. | 2 items | technical-spike, assumption-testing, validation, research |
|
||||
| [testing-automation](../plugins/testing-automation/README.md) | Comprehensive collection for writing tests, test automation, and test-driven development including unit tests, integration tests, and end-to-end testing strategies. | 9 items | testing, tdd, automation, unit-tests, integration, playwright, jest, nunit |
|
||||
| [the-workshop](../plugins/the-workshop/README.md) | Stop being the switchboard between your AI agents — direct a team. 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. | 5 items | multi-agent, coordination, desks, persistent-memory, agent-signals, developer-experience |
|
||||
| [typescript-mcp-development](../plugins/typescript-mcp-development/README.md) | Complete toolkit for building Model Context Protocol (MCP) servers in TypeScript/Node.js using the official SDK. Includes instructions for best practices, a prompt for generating servers, and an expert chat mode for guidance. | 2 items | typescript, mcp, model-context-protocol, nodejs, server-development |
|
||||
| [typespec-m365-copilot](../plugins/typespec-m365-copilot/README.md) | Comprehensive collection of prompts, instructions, and resources for building declarative agents and API plugins using TypeSpec for Microsoft 365 Copilot extensibility. | 3 items | typespec, m365-copilot, declarative-agents, api-plugins, agent-development, microsoft-365 |
|
||||
| [visual-pr](../plugins/visual-pr/README.md) | Capture, annotate, and embed screenshots and animated GIF demos in pull request descriptions. Includes Playwright-based UI capture, PIL image annotations, PR embedding workflows for GitHub and Azure DevOps, and screen recording with variable timing. | 4 items | screenshots, pull-request, before-after, annotations, playwright, gif, screen-recording, visual |
|
||||
|
||||
@@ -76,6 +76,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
|
||||
| [azure-smart-city-iot-solution-builder](../skills/azure-smart-city-iot-solution-builder/SKILL.md)<br />`gh skills install github/awesome-copilot azure-smart-city-iot-solution-builder` | Design and plan end-to-end Azure IoT and Smart City solutions: requirements, architecture, security, operations, cost, and a phased delivery plan with concrete implementation artifacts. | `references/smart-city-solution-template.md` |
|
||||
| [azure-static-web-apps](../skills/azure-static-web-apps/SKILL.md)<br />`gh skills install github/awesome-copilot azure-static-web-apps` | Helps create, configure, and deploy Azure Static Web Apps using the SWA CLI. Use when deploying static sites to Azure, setting up SWA local development, configuring staticwebapp.config.json, adding Azure Functions APIs to SWA, or setting up GitHub Actions CI/CD for Static Web Apps. | None |
|
||||
| [batch-files](../skills/batch-files/SKILL.md)<br />`gh skills install github/awesome-copilot batch-files` | Expert-level Windows batch file (.bat/.cmd) skill for writing, debugging, and maintaining CMD scripts. Use when asked to "create a batch file", "write a .bat script", "automate a Windows task", "CMD scripting", "batch automation", "scheduled task script", "Windows shell script", or when working with .bat/.cmd files in the workspace. Covers cmd.exe syntax, environment variables, control flow, string processing, error handling, and integration with system tools. | `assets/executable.txt`<br />`assets/library.txt`<br />`assets/task.txt`<br />`references/batch-files-and-functions.md`<br />`references/cygwin.md`<br />`references/msys2.md`<br />`references/tools-and-resources.md`<br />`references/windows-commands.md`<br />`references/windows-subsystem-on-linux.md` |
|
||||
| [bench-read](../skills/bench-read/SKILL.md)<br />`gh skills install github/awesome-copilot bench-read` | Read artifacts from the shared bench — the workspace where desks leave findings, verdicts, and work products for each other and the operator. | None |
|
||||
| [bigquery-pipeline-audit](../skills/bigquery-pipeline-audit/SKILL.md)<br />`gh skills install github/awesome-copilot bigquery-pipeline-audit` | Audits Python + BigQuery pipelines for cost safety, idempotency, and production readiness. Returns a structured report with exact patch locations. | None |
|
||||
| [boost-prompt](../skills/boost-prompt/SKILL.md)<br />`gh skills install github/awesome-copilot boost-prompt` | Interactive prompt refinement workflow: interrogates scope, deliverables, constraints; copies final markdown to clipboard; never writes code. Requires the Joyride extension. | None |
|
||||
| [brag-sheet](../skills/brag-sheet/SKILL.md)<br />`gh skills install github/awesome-copilot brag-sheet` | Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments. | None |
|
||||
@@ -144,6 +145,8 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
|
||||
| [debian-linux-triage](../skills/debian-linux-triage/SKILL.md)<br />`gh skills install github/awesome-copilot debian-linux-triage` | Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance. | None |
|
||||
| [declarative-agents](../skills/declarative-agents/SKILL.md)<br />`gh skills install github/awesome-copilot declarative-agents` | Complete development kit for Microsoft 365 Copilot declarative agents with three comprehensive workflows (basic, advanced, validation), TypeSpec support, and Microsoft 365 Agents Toolkit integration | None |
|
||||
| [dependabot](../skills/dependabot/SKILL.md)<br />`gh skills install github/awesome-copilot dependabot` | Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update configuration, auto-triage rules, or any GitHub Advanced Security (GHAS) supply chain security topic related to Dependabot. For pre-commit dependency vulnerability scanning in AI coding agents via the GitHub MCP Server, this skill references the Advanced Security plugin (`advanced-security@copilot-plugins`). Use this skill when an agent needs to scan dependencies for known vulnerabilities before committing. | `references/dependabot-yml-reference.md`<br />`references/example-configs.md`<br />`references/pr-commands.md` |
|
||||
| [desk-journal](../skills/desk-journal/SKILL.md)<br />`gh skills install github/awesome-copilot desk-journal` | Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries. A good entry has: what was done, current state, next step. | None |
|
||||
| [desk-open](../skills/desk-open/SKILL.md)<br />`gh skills install github/awesome-copilot desk-open` | 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. | None |
|
||||
| [devops-rollout-plan](../skills/devops-rollout-plan/SKILL.md)<br />`gh skills install github/awesome-copilot devops-rollout-plan` | Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes | None |
|
||||
| [diagnose](../skills/diagnose/SKILL.md)<br />`gh skills install github/awesome-copilot diagnose` | Perform a systematic diagnostic scan of an AI workflow across 5 quality dimensions — prompt quality, context efficiency, tool health, architecture fitness, and safety — producing a scored report with prioritized remediation actions. | None |
|
||||
| [doc-and-modernize](../skills/doc-and-modernize/SKILL.md)<br />`gh skills install github/awesome-copilot doc-and-modernize` | Two related workflows for a locally-cloned codebase, in one skill. Documentation mode produces a single, comprehensive, verifiable architecture document primarily by reading files on disk (local-first) — use it whenever the user wants to understand, map, document, research, or onboard onto a codebase ("research this repo", "write up the architecture", "do an architecture deep dive", "document how this codebase works", "map the system design", "create an onboarding doc"). Modernization mode generates a phased plan to modernize, migrate, upgrade, or rewrite a legacy system ("modernize this", "plan the migration", "how would we rewrite this", "how do we get off this legacy stack"); if no architecture document exists yet it first runs Documentation mode, then continues straight through to the plan. It assumes the legacy stack may be dead, runs a time-boxed feasibility spike, and picks the highest achievable rung on a safety ladder instead of demanding a fully-green legacy CI gate up front. | `references/copilot-instructions.template.md`<br />`references/migration-hazards.md` |
|
||||
@@ -357,6 +360,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
|
||||
| [semantic-kernel](../skills/semantic-kernel/SKILL.md)<br />`gh skills install github/awesome-copilot semantic-kernel` | Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python. | `references/dotnet.md`<br />`references/python.md` |
|
||||
| [setup-my-iq](../skills/setup-my-iq/SKILL.md)<br />`gh skills install github/awesome-copilot setup-my-iq` | Create, set up, or update the personal context portfolio: structured markdown files describing<br />who you are, how you work, your teams, and your tool/ADO configuration. Runs the interview<br />workflow for first-time setup and targeted edits for updates.<br /><br />Trigger this skill when the user asks to: set up their context, create or update their context<br />portfolio, "create my IQ", "set up my IQ", edit their profile, add/remove a stakeholder,<br />update ADO config, change team info, update pillars, or set up any plugin configuration.<br />Trigger when another skill fails to find context (missing files or TODO markers) and needs<br />context populated. Also trigger when the user mentions a context change in passing<br />(e.g., "my manager changed", "we added someone to the team") to offer a context file update.<br /><br />Do NOT trigger for read-only questions like "who's on my team?" or "what's my ADO config?".<br />Those are answered directly from the context files referenced in the loaded custom<br />instructions; no skill is needed. | `assets/templates` |
|
||||
| [shuffle-json-data](../skills/shuffle-json-data/SKILL.md)<br />`gh skills install github/awesome-copilot shuffle-json-data` | Shuffle repetitive JSON objects safely by validating schema consistency before randomising entries. | None |
|
||||
| [signal-write](../skills/signal-write/SKILL.md)<br />`gh skills install github/awesome-copilot signal-write` | Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence. | None |
|
||||
| [slang-shader-engineer](../skills/slang-shader-engineer/SKILL.md)<br />`gh skills install github/awesome-copilot slang-shader-engineer` | Use when working with Slang shaders, shader modules, HLSL-compatible GPU code, graphics pipelines, compute shaders, tessellation, ray tracing, parameter blocks, generics, interfaces, capabilities, cross-compilation, shader optimization, shader review, or C++ engine integration for Slang. Trigger on any mention of Slang, .slang files, slangc, SPIR-V from Slang, Slang modules, [shader("compute")], [shader("vertex")], or requests to write/review/refactor shader code with modern language features. Also trigger for Slang-to-HLSL/GLSL/Metal/CUDA cross-compile questions, or when the user says "shader" alongside "generics", "interfaces", "parameter blocks", "autodiff", or "capabilities". | `references/language-reference.md`<br />`references/rules-and-patterns.md`<br />`references/slang-documentation-full.md` |
|
||||
| [snowflake-semanticview](../skills/snowflake-semanticview/SKILL.md)<br />`gh skills install github/awesome-copilot snowflake-semanticview` | Create, alter, and validate Snowflake semantic views using Snowflake CLI (snow). Use when asked to build or troubleshoot semantic views/semantic layer definitions with CREATE/ALTER SEMANTIC VIEW, to validate semantic-view DDL against Snowflake via CLI, or to guide Snowflake CLI installation and connection setup. | None |
|
||||
| [sponsor-finder](../skills/sponsor-finder/SKILL.md)<br />`gh skills install github/awesome-copilot sponsor-finder` | Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express"). | None |
|
||||
|
||||
+4
-4
@@ -16,12 +16,12 @@
|
||||
"developer-experience"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/workshop-ta.agent.md"
|
||||
"workshop-ta"
|
||||
],
|
||||
"skills": [
|
||||
"./skills/desk-open/",
|
||||
"./skills/bench-read/",
|
||||
"./skills/desk-journal/",
|
||||
"./skills/signal-write/",
|
||||
"./skills/bench-read/"
|
||||
"./skills/desk-open/",
|
||||
"./skills/signal-write/"
|
||||
]
|
||||
}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: signal-write
|
||||
description: 'Emit structured agent signals — hands-up, blocked, done, checkpoint. Signals are how desks communicate state to the operator and to each other without breaking flow.'
|
||||
description: 'Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence.'
|
||||
---
|
||||
|
||||
# Agent Signals
|
||||
@@ -13,6 +13,7 @@ Emit structured signals from a desk to the operator or other desks.
|
||||
- Work is complete and ready for review (done)
|
||||
- Significant progress worth noting (checkpoint)
|
||||
- Two desks disagree and can't resolve it (hands-up)
|
||||
- The TA is reporting coordination quality (partnership)
|
||||
|
||||
## Signal types
|
||||
|
||||
@@ -21,60 +22,72 @@ Two desks disagree and can't settle it against external facts.
|
||||
This is the system working — the operator reads where desks
|
||||
*disagree*, not where they perform confidence.
|
||||
|
||||
```
|
||||
Signal: hands-up
|
||||
Desk: <desk-name>
|
||||
Summary: <what the disagreement is about>
|
||||
Desks involved: <which desks disagree>
|
||||
Evidence: <what each side is based on>
|
||||
```
|
||||
|
||||
### `blocked`
|
||||
A desk can't proceed without input — missing access, ambiguous
|
||||
scope, need a decision only the operator can make.
|
||||
|
||||
```
|
||||
Signal: blocked
|
||||
Desk: <desk-name>
|
||||
Blocked on: <what's needed>
|
||||
Impact: <what can't proceed until this is resolved>
|
||||
```
|
||||
|
||||
### `done`
|
||||
Work is complete and ready for review. Artifacts are on the bench.
|
||||
|
||||
```
|
||||
Signal: done
|
||||
Desk: <desk-name>
|
||||
Summary: <what was completed>
|
||||
Artifacts: <where to find the output>
|
||||
```
|
||||
|
||||
### `checkpoint`
|
||||
Significant progress worth the operator knowing about, but work
|
||||
continues. Not blocked, not done — just a marker.
|
||||
|
||||
```
|
||||
Signal: checkpoint
|
||||
Desk: <desk-name>
|
||||
Summary: <what was accomplished>
|
||||
Next: <what's happening next>
|
||||
```
|
||||
### `partnership`
|
||||
Used by the TA (room coordinator) to report coordination quality.
|
||||
Self-assessment scores reflect coordination, not code accuracy:
|
||||
- **intent** — understood what the operator needed
|
||||
- **confidence** — right work went to the right desks
|
||||
- **accuracy** — dispatched work produced the right outcome
|
||||
- **completeness** — nothing fell through the cracks
|
||||
|
||||
## How to emit
|
||||
|
||||
Write the signal to the desk's journal with a `[signal]` marker:
|
||||
### 1. Write a JSON signal file to `.signals/`
|
||||
|
||||
```markdown
|
||||
## <date> — [signal:hands-up] <summary>
|
||||
- **Desks:** scanning, review
|
||||
- **Disagreement:** scanning found CWE-502 in lib/deserialize.cs;
|
||||
review says the SerializationBinder is sufficient
|
||||
- **Evidence:** <what each desk is basing its position on>
|
||||
This is the primary output — it's what the dashboard reads.
|
||||
Create `desks/<desk-name>/.signals/<timestamp>.json`:
|
||||
|
||||
```json
|
||||
{
|
||||
"signal_type": "execution",
|
||||
"agent_name": "<desk-name>",
|
||||
"self_assessment": {
|
||||
"intent": 4,
|
||||
"confidence": 5,
|
||||
"accuracy": 4,
|
||||
"completeness": 3
|
||||
},
|
||||
"patterns": {
|
||||
"what_worked": "description of what went well",
|
||||
"what_was_hard": "description of challenges",
|
||||
"skill_gap": "areas for improvement"
|
||||
},
|
||||
"escalation": {
|
||||
"reason": null,
|
||||
"blocked_on": null,
|
||||
"recommendation": null
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
For cross-desk visibility, also note the signal on the bench if
|
||||
other desks need to see it before the operator routes it.
|
||||
For `hands-up` or `blocked` signals, populate the `escalation`
|
||||
fields. Use `signal_type: "escalation"` for these — they sort to
|
||||
the top of the dashboard.
|
||||
|
||||
For `partnership` signals (TA only), use `signal_type: "partnership"`.
|
||||
|
||||
### 2. Note the signal in the journal
|
||||
|
||||
Also append a short marker to the desk's journal for persistence:
|
||||
|
||||
```markdown
|
||||
## <date> — [signal:<type>] <summary>
|
||||
- <key details>
|
||||
```
|
||||
|
||||
The journal note is the trail marker. The JSON file is the
|
||||
machine-readable signal.
|
||||
|
||||
## Principles
|
||||
|
||||
@@ -86,3 +99,5 @@ other desks need to see it before the operator routes it.
|
||||
changes that affect the room, not status updates.
|
||||
- blocked means truly blocked — not "I'd prefer input." If you
|
||||
can proceed with a reasonable default, proceed and note it.
|
||||
- Self-assessment scores should be honest, not optimistic. A 3/5
|
||||
is fine. A 5/5 on everything is suspicious.
|
||||
|
||||
Reference in New Issue
Block a user