mozempk/redsen-lean-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: verify and clarify agent-namespacing vs skill-namespacing, add stale-session note

Browse Source
This commit is contained in:
mozempk
2026-09-10 01:34:26 +02:00
parent 5896213780
commit d74cb58821
2 changed files with 26 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+13 -3
View File
@@ -129,9 +129,19 @@ Then, in Copilot CLI or VS Code Copilot:
> **Agent name note:** inside this repo (or any repo where the harness lives natively in
> `.github/agents`), `@conductor` works unprefixed. Once installed as a *plugin* into another
> project, Copilot CLI namespaces plugin agents to avoid name collisions — use
> `@redsen-lean-harness:conductor` (tab-complete via `/agent` shows the full list). Skills
> (`/fast-track`, `/design`, etc.) are not namespaced and work either way.
> project, Copilot CLI namespaces **agents only** — use `@redsen-lean-harness:conductor`,
> `@redsen-lean-harness:architect`, etc. (`/agent` lists the full namespaced set). **Skills are
> never namespaced** — `/fast-track`, `/design`, `/build`, `/verify`, `/onboard`, etc. work as
> plain slash commands regardless of install method. Verified with
> `copilot plugins list --kind skill --json` (skill `name` fields have no prefix) vs.
> `copilot --agent <bad-name>` (the "available" list always shows plugin agents as
> `plugin-name:agent-name`).
>
> If `@redsen-lean-harness:conductor` (or any plugin skill) still isn't found: the plugin was
> likely loaded before a fix landed. Run
> `copilot plugin marketplace update redsen && copilot plugin update redsen-lean-harness`,
> then start a **new** `copilot` session — an already-running session keeps the plugin
> snapshot it loaded at startup and won't pick up the update until restarted.
For a small brownfield change, skip the ceremony:
docs/QUICKSTART.md
+13 -3
View File
@@ -111,9 +111,19 @@ size of the change.
> **Agent name note:** inside this repo (or any repo where the harness lives natively in
> `.github/agents`), `@conductor` works unprefixed. Once installed as a *plugin* into another
> project, Copilot CLI namespaces plugin agents to avoid name collisions — use
> `@redsen-lean-harness:conductor` (tab-complete via `/agent` shows the full list). Skills
> (`/fast-track`, `/design`, etc.) are not namespaced and work either way.
> project, Copilot CLI namespaces **agents only** — use `@redsen-lean-harness:conductor`,
> `@redsen-lean-harness:architect`, etc. (`/agent` lists the full namespaced set). **Skills are
> never namespaced** — `/fast-track`, `/design`, `/build`, `/verify`, `/onboard`, etc. work as
> plain slash commands regardless of install method. Verified with
> `copilot plugins list --kind skill --json` (skill `name` fields have no prefix) vs.
> `copilot --agent <bad-name>` (the "available" list always shows plugin agents as
> `plugin-name:agent-name`).
>
> If `@redsen-lean-harness:conductor` (or any plugin skill) still isn't found: the plugin was
> likely loaded before a fix landed. Run
> `copilot plugin marketplace update redsen && copilot plugin update redsen-lean-harness`,
> then start a **new** `copilot` session — an already-running session keeps the plugin
> snapshot it loaded at startup and won't pick up the update until restarted.
This runs the whole pipeline: `interrogator` asks clarifying questions with recommended
answers (you must answer before it proceeds — this is a deliberate gate), `architect` writes