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.
59 lines
1.3 KiB
Markdown
59 lines
1.3 KiB
Markdown
# HOWTO (breve) — iniciar ARNES en proyecto nuevo o ya empezado
|
|
|
|
## 1) Proyecto nuevo (greenfield)
|
|
|
|
```bash
|
|
mkdir mi-proyecto && cd mi-proyecto
|
|
git init
|
|
# copiar contenido de arnes-fork aquí
|
|
./scripts/start.sh
|
|
./scripts/verify.sh
|
|
python3 scripts/agent_status.py show
|
|
```
|
|
|
|
Después:
|
|
- Edita `backlog/features.json` (`project`, `description`).
|
|
- Crea tu primera feature `pending` (puedes usar `starter-pack/backlog.features.bootstrap.json`).
|
|
- Empieza el ciclo SDD (una feature a la vez).
|
|
|
|
---
|
|
|
|
## 2) Proyecto ya empezado (brownfield)
|
|
|
|
Copia al repo existente solo el core ARNES:
|
|
- `harness/`
|
|
- `spec/`
|
|
- `backlog/`
|
|
- `work/`
|
|
- `scripts/`
|
|
- `platforms/`
|
|
- `AGENTS.md`, `CHECKPOINTS.md`
|
|
|
|
Luego ejecuta:
|
|
|
|
```bash
|
|
./scripts/start.sh
|
|
./scripts/verify.sh
|
|
python3 scripts/agent_status.py show
|
|
```
|
|
|
|
Y añade checks del dominio en:
|
|
- `scripts/verify.local.sh` (opcional)
|
|
|
|
---
|
|
|
|
Crear ticket nuevo (leader/triager, EN caveman):
|
|
```bash
|
|
python3 scripts/new_ticket.py
|
|
```
|
|
|
|
Modelo por tarea:
|
|
- Config base en `harness/models.profiles.yml`
|
|
- Reglas en `harness/policies/model-routing.md`
|
|
|
|
## Reglas operativas mínimas
|
|
- Máximo una feature en `in_progress`.
|
|
- `done` requiere gates `review/security/qa` aprobados.
|
|
- Evidencia siempre en `work/artifacts/<feature_id>/`.
|
|
- Si `verify.sh` falla, no se cierra la feature.
|