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

docs: clarify plugin agents are namespaced (redsen-lean-harness:conductor) outside this repo

Browse Source
This commit is contained in:
mozempk
2026-09-10 01:27:47 +02:00
parent 0e0e7d6bd4
commit 5896213780
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+6
View File
@@ -127,6 +127,12 @@ Then, in Copilot CLI or VS Code Copilot:
@conductor build a rate limiter for the public API @conductor build a rate limiter for the public API
``` ```
> **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.
For a small brownfield change, skip the ceremony: For a small brownfield change, skip the ceremony:
``` ```
docs/QUICKSTART.md
+6
View File
@@ -109,6 +109,12 @@ size of the change.
@conductor build a rate limiter for the public API @conductor build a rate limiter for the public API
``` ```
> **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.
This runs the whole pipeline: `interrogator` asks clarifying questions with recommended 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 answers (you must answer before it proceeds — this is a deliberate gate), `architect` writes
the spec and acceptance criteria, `splitter` breaks it into lanes, `builder`/`verifier` run the the spec and acceptance criteria, `splitter` breaks it into lanes, `builder`/`verifier` run the