Files
Kill_LIFE/.github/prompts/plan_wizard_agents_management.prompt.md
Clément SAILLANT 5efb380da5 feat: automate yiacad PR review lane (#18)
* feat: automate yiacad pr review lane

* fix: stabilize yiacad review and spec gates

* fix: scope kicad exports to repo hardware

* fix: ignore kicad block library sources in exports

* feat: Add infra VPS monitoring runbook and healthcheck scripts

- Created INFRA_VPS_RUNBOOK_2026.md detailing operational procedures for monitoring VPS services.
- Added infra_vps_healthcheck.sh script for automated health checks on DNS, TLS, TCP, and HTTP for VPS services.
- Introduced infra_vps_security_audit.sh for non-intrusive security checks on external VPS services.
- Established JSON schema for infra VPS inventory in infra_vps.schema.json.
- Developed integration for runtime status reporting in the Next.js API route.
- Implemented Playwright tests for smoke testing the application and ensuring core functionalities.
- Updated Makefile for development dependencies and testing commands.
- Created various test files for unit and end-to-end testing across different components.

* feat(agentics): update mesh agents, gates, prompts, and workflows
2026-03-29 17:14:16 +02:00

12 lines
969 B
Markdown

---
name: planWizardAgentsManagement
description: Génère un plan pour la gestion des agents.
argument-hint: Spécifie catalogue, prompts, write sets, rituels, gates, handoffs et evidence.
---
Génère un plan structuré pour la gestion des agents en prenant `specs/contracts/kill_life_agent_catalog.json` comme source de vérité.
1. Partir de la liste canonique top-level: `PM-Mesh`, `Arch-Mesh`, `Docs-Research`, `Runtime-Companion`, `QA-Compliance`, `Embedded-CAD`, `Web-CAD-Platform`, `UX-Lead`, `Firmware`, `SyncOps`, `Schema-Guard`, `KillLife-Bridge`.
2. Vérifier la parité entre contrat, `agents/`, `.github/agents/`, prompts `start_*` et `plan_wizard_*`, README et matrice.
3. Référencer `docs/GLOBAL_MULTI_AGENT_CHECKLIST.md` pour les étapes communes, handoffs et preuves.
4. Garder les sous-agents comme metadata de gouvernance, jamais comme agents API publics.
5. Conclure par le validateur à exécuter, les preuves attendues et la prochaine action.