From 4632bfbdf64db3a93c9a80f6ada5bb5c6befd13b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niccol=C3=B2=20Olivieri=20Achille?= Date: Wed, 14 Oct 2026 12:01:01 +0200 Subject: [PATCH] feat(agents)!: :recycle: adopt potr- namespace for crew templates Rename the four distributable Kiro agent templates to the potr- namespace, consistently across specs, prompts, skills, CLI, tests and docs: bepower-setup -> potr-setup functional-analyst -> potr-functional-analyst upgrade-guardian -> potr-upgrade-guardian rev-eng -> potr-rev-eng - git mv all agent/prompt files and the upgrade-guardian skill + functional-analyst resources dirs (history preserved) - update "name"/prompt/resources paths inside each spec - update CREW_AGENTS and all copy paths/logs in init-crew.ts / init-kiro.ts so members register under the new names - update test assertions and README / hooks docs CHANGELOG and version bump handled by release-please; dist/ regenerated via build (gitignored). BREAKING CHANGE: crew agent templates renamed to the potr- namespace; the previous names (bepower-setup, functional-analyst, upgrade-guardian, rev-eng) no longer resolve. --- README.md | 24 +++++----- cli/commands/init-crew.ts | 7 ++- cli/commands/init-kiro.ts | 44 ++++++++++--------- ...lyst.json => potr-functional-analyst.json} | 6 +-- .../{rev-eng.json => potr-rev-eng.json} | 4 +- .../{bepower-setup.json => potr-setup.json} | 4 +- ...ardian.json => potr-upgrade-guardian.json} | 4 +- kiro/hooks/README.md | 6 +-- ...-analyst.md => potr-functional-analyst.md} | 0 kiro/prompts/{rev-eng.md => potr-rev-eng.md} | 4 +- .../{bepower-setup.md => potr-setup.md} | 4 +- ...e-guardian.md => potr-upgrade-guardian.md} | 8 ++-- .../template-analisi-funzionale.md | 0 .../template-matrice-funzionale.md | 0 .../template-steering-architecture.md | 0 .../template-steering-domain.md | 0 .../template-steering-roles.md | 0 .../SKILL.md | 4 +- test/init-crew.test.ts | 12 ++++- test/init-kiro.test.ts | 18 ++++---- 20 files changed, 82 insertions(+), 67 deletions(-) rename kiro/agents/{functional-analyst.json => potr-functional-analyst.json} (82%) rename kiro/agents/{rev-eng.json => potr-rev-eng.json} (94%) rename kiro/agents/{bepower-setup.json => potr-setup.json} (90%) rename kiro/agents/{upgrade-guardian.json => potr-upgrade-guardian.json} (92%) rename kiro/prompts/{functional-analyst.md => potr-functional-analyst.md} (100%) rename kiro/prompts/{rev-eng.md => potr-rev-eng.md} (97%) rename kiro/prompts/{bepower-setup.md => potr-setup.md} (92%) rename kiro/prompts/{upgrade-guardian.md => potr-upgrade-guardian.md} (84%) rename kiro/resources/{functional-analyst => potr-functional-analyst}/template-analisi-funzionale.md (100%) rename kiro/resources/{functional-analyst => potr-functional-analyst}/template-matrice-funzionale.md (100%) rename kiro/resources/{functional-analyst => potr-functional-analyst}/template-steering-architecture.md (100%) rename kiro/resources/{functional-analyst => potr-functional-analyst}/template-steering-domain.md (100%) rename kiro/resources/{functional-analyst => potr-functional-analyst}/template-steering-roles.md (100%) rename kiro/skills/{upgrade-guardian => potr-upgrade-guardian}/SKILL.md (98%) diff --git a/README.md b/README.md index 0b72fd3..b9df2aa 100644 --- a/README.md +++ b/README.md @@ -108,7 +108,7 @@ At the end it offers an interactive opt-in — **"Also initialize KiroCrew? (y/N What it installs: 1. `~/.kiro/agents/*.json` — the four agent specs (also valid KiroCrew templates) 2. `~/.kiro/prompts/*.md` — their system prompts -3. `~/.kiro/skills/` — workflow skills (incl. the `upgrade-guardian` skill) +3. `~/.kiro/skills/` — workflow skills (incl. the `potr-upgrade-guardian` skill) 4. `~/.kiro/hooks/` — safety-gate, barrel-export, etc. 5. `~/.kiro/steering/` — shared steering docs @@ -196,10 +196,10 @@ These agents are distributed by `dev init-kiro` for use across all BePower proje | Agent | Description | |-------|-------------| -| `bepower-setup` | Analyzes a project and generates optimal `.kiro/` configuration (steering, agent, prompt, skills) | -| `functional-analyst` | Interactive functional analysis — collects requirements through conversation, produces approval docs and technical briefs (Italian-first) | -| `upgrade-guardian` | Assesses the safety of a dependency/framework upgrade in an isolated worktree and returns a reasoned **LOW/MEDIUM/HIGH** risk verdict with real breaking-change analysis, project impact and verification | -| `rev-eng` | Reverse-engineers a target web app's internal API via Playwright and documents it for a TypeScript client | +| `potr-setup` | Analyzes a project and generates optimal `.kiro/` configuration (steering, agent, prompt, skills) | +| `potr-functional-analyst` | Interactive functional analysis — collects requirements through conversation, produces approval docs and technical briefs (Italian-first) | +| `potr-upgrade-guardian` | Assesses the safety of a dependency/framework upgrade in an isolated worktree and returns a reasoned **LOW/MEDIUM/HIGH** risk verdict with real breaking-change analysis, project impact and verification | +| `potr-rev-eng` | Reverse-engineers a target web app's internal API via Playwright and documents it for a TypeScript client | ## Using the Agents @@ -212,7 +212,7 @@ Pass the agent name to `kiro-cli chat`: ```bash # in the repo you want it to work on cd ~/projects/bepower/bep-cdk -kiro-cli chat --agent upgrade-guardian +kiro-cli chat --agent potr-upgrade-guardian ``` Then start the conversation by telling it what to assess, e.g.: @@ -223,7 +223,7 @@ The agent reads the project context (`README.md`, `AGENTS.md` if present, `packa ### In the KiroCrew dashboard -After `dev init-crew` the agents appear as **members in the dashboard's agent picker**. Open a new chat, pick `upgrade-guardian` (or `rev-eng`), and start the conversation the same way — the result (e.g. an upgrade safety report) is rendered inline, with each member keeping its own dedicated memory. +After `dev init-crew` the agents appear as **members in the dashboard's agent picker**. Open a new chat, pick `potr-upgrade-guardian` (or `potr-rev-eng`), and start the conversation the same way — the result (e.g. an upgrade safety report) is rendered inline, with each member keeping its own dedicated memory. ### How to start the conversation @@ -231,12 +231,12 @@ These agents are **task-driven**, not chatty — open with the concrete thing yo | Agent | A good opening message | |-------|------------------------| -| `upgrade-guardian` | _"Assess upgrading `` from `` to `` in this repo. Is it safe to merge?"_ | -| `rev-eng` | _"Reverse-engineer the API of `` and document the endpoints for a TypeScript client."_ | -| `bepower-setup` | _"Analyze this project and generate the `.kiro/` configuration for it."_ | -| `functional-analyst` | _"Raccogliamo i requisiti per ``."_ (Italian-first) | +| `potr-upgrade-guardian` | _"Assess upgrading `` from `` to `` in this repo. Is it safe to merge?"_ | +| `potr-rev-eng` | _"Reverse-engineer the API of `` and document the endpoints for a TypeScript client."_ | +| `potr-setup` | _"Analyze this project and generate the `.kiro/` configuration for it."_ | +| `potr-functional-analyst` | _"Raccogliamo i requisiti per ``."_ (Italian-first) | -The agent does the rest — reads context, analyzes, and returns a verdict or document. For `upgrade-guardian` the output is a safety report with a LOW/MEDIUM/HIGH verdict and a **suggested** (never executed) commit message; you decide whether to apply it. +The agent does the rest — reads context, analyzes, and returns a verdict or document. For `potr-upgrade-guardian` the output is a safety report with a LOW/MEDIUM/HIGH verdict and a **suggested** (never executed) commit message; you decide whether to apply it. ## Architecture diff --git a/cli/commands/init-crew.ts b/cli/commands/init-crew.ts index dff93b4..35c747d 100644 --- a/cli/commands/init-crew.ts +++ b/cli/commands/init-crew.ts @@ -13,7 +13,12 @@ const execAsync = promisify(exec); * from the same `~/.kiro/agents/` directory, so each one only needs a crew * member bound to it (`kirocrew agent create --kiro-agent