3ff9b70e4c
- Add complete agent harness structure with 8 roles (leader, triager, architect, implementer, reviewer, security, qa, documenter) - Implement strict workflow with 9 stages and mandatory gates - Add comprehensive verification script and runtime status tracking - Create artifact-based evidence system with contracts and schemas - Add agent policy matrix with permissions and anti-cheat rules - Include test suite (44 tests passing) and CI-ready structure - Add documentation: README, HOWTO, CHECKPOINTS, templates - Configure model routing policies and token-aware task assignment - Add BDD/SDD specification guides and feature templates - Include starter pack for quick project onboarding All verification checks pass. Framework ready for production use.
33 lines
1.3 KiB
Markdown
33 lines
1.3 KiB
Markdown
# TEMPLATE.md — Cómo adaptar ARNES a cualquier proyecto
|
|
|
|
## 1) Clonar y renombrar contexto
|
|
- Ajusta `backlog/features.json` (`project`, `description`).
|
|
- Crea primeras features reales en `features[]`.
|
|
|
|
## 2) Reglas específicas (sin tocar core)
|
|
- Opcional: crea `AGENTS.local.md` con reglas del dominio.
|
|
- Opcional: crea `scripts/verify.local.sh` con checks propios del stack.
|
|
- Mantén tickets y órdenes internas en English caveman (`harness/policies/language.md`).
|
|
- Ajusta routing de modelos por rol/tarea en `harness/models.profiles.yml`.
|
|
|
|
## 3) Flujo estándar
|
|
1. `./scripts/start.sh` (primer uso)
|
|
2. `python3 scripts/new_ticket.py` (leader/triager)
|
|
3. `python3 scripts/agent_status.py show`
|
|
4. Seleccionar 1 feature `pending` y pasarla a `in_progress`
|
|
5. Implementar con artefactos en `work/artifacts/<feature_id>/`
|
|
6. Cerrar solo con gates `review/security/qa` + `documenter` aprobados
|
|
7. `python3 scripts/agent_status.py reset`
|
|
|
|
## 4) Contrato de cierre
|
|
- `status=done` exige:
|
|
- `reviewer.json` APPROVED
|
|
- `security.json` APPROVED
|
|
- `qa.json` APPROVED
|
|
- `leader-close.json` APPROVED
|
|
- `./scripts/verify.sh` OK
|
|
|
|
## 5) Principio de template
|
|
- El core ARNES es agnóstico.
|
|
- Todo lo específico de proyecto vive en overlays (`AGENTS.local.md`, `verify.local.sh`, docs propias).
|