rikrdo/arnes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
3ff9b70e4c8103731cbaf927baf023f67f0d01c5
arnes/AGENTS.md
rikrdo 3ff9b70e4c refactor: complete bootstrap of ARNES agent harness framework 
- 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.
2026-05-17 23:25:35 +02:00

2.1 KiB
Raw Blame History

AGENTS.md — Entry point del template ARNES

Este repositorio es un template genérico para cualquier proyecto nuevo o en curso.

Arranque obligatorio

  1. Si es primer uso en proyecto: ejecutar ./scripts/start.sh.
  2. Leer work/current.md.
  3. Leer backlog/features.json y seleccionar una feature pending.
  4. Ejecutar ./scripts/verify.sh.
  5. Mostrar estado runtime: python3 scripts/agent_status.py show.
  6. Seguir harness/workflow.stages.yml y harness/agents.matrix.yml.

Ticket creation policy

  • Tickets are created by leader (or triager) only.
  • Use: python3 scripts/new_ticket.py
  • Ticket language: English caveman.
  • Internal orders/handoffs: English caveman.

Estado visible del arnés

  • Estado runtime: work/runtime-status.json.
  • Mostrar: python3 scripts/agent_status.py show.
  • Actualizar transición:
    • python3 scripts/agent_status.py set --feature-id F-123 --stage build --agent implementer --action "Implementando" --state running --next-agent reviewer --waiting-for "work/artifacts/F-123/implementer.md"
  • Cerrar/idle:
    • python3 scripts/agent_status.py reset

Reglas duras

  • Una sola feature en in_progress.
  • Ningún agente pasa código por chat: todo va a work/artifacts/<feature_id>/.
  • implementer nunca marca done.
  • done requiere gates aprobados: reviewer, security, qa.
  • done requiere evidencia de documenter: work/artifacts/<feature_id>/documenter.md.
  • Si verify.sh falla, no se cierra la feature.

Modelo por tarea (token-aware)

  • Use smallest model that fits task.
  • Routing config: harness/models.profiles.yml
  • Rules: harness/policies/model-routing.md

Extensión por proyecto (overlay)

  • Opcional: AGENTS.local.md para reglas específicas del proyecto actual.
  • Opcional: scripts/verify.local.sh para checks de dominio.
  • El core de ARNES debe seguir siendo agnóstico.

Reentrada (context loss)

  • Releer work/current.md y artefactos de la feature activa.
  • Ejecutar ./scripts/verify.sh.
  • Mostrar python3 scripts/agent_status.py show.
  • Continuar desde “Próximo paso”.