claude

aura

Harness de trabajo para agentes IA sobre Claude Code: memoria persistente, protocolos de sesion, ciclo de vida de objetivos y automatizacion del flujo git/GitHub.

1 on GitHubv2.9.1MITupdated 30 days ago
/

Plugin aura from marketplace aura-agent-kit in diegosvart/aura-agent-kit. Commands read from the repo's manifest — 30 days ago.

What it installs

Skills (20)

  • agentic-dev-loop

    Ejecuta issues con label ready usando agentes, separando desarrollo (no supervisado) de verificación (nunca mergea sola). Usar al correr /run-dev-loop.

  • auto-research

    Formaliza la mejora continua del harness con hipótesis documentadas. Usar cuando se detecta fricción repetida, un workaround recurrente, una pregunta que se repite entre sesiones, un paso de protocolo que se saltea sistemáticamente, o una inconsistencia entre skills/protocolos.

  • brainstorming

    Use before any creative work - creating features, building components, or modifying behavior.

  • e2e-testing

    Ejecuta un smoke test / flujo E2E headless contra una app web vía agent-browser, sin supervisión humana. Usar para validar un flujo crítico tras implementar un issue con impacto en UI, o capturar regresión visual.

  • finishing-a-development-branch

    Use when all tasks in a branch are complete and you're ready to close the work

  • harness-status

    Genera un inventario del harness (conteo de AGENTS/SKILLS/PROTOCOLS/RULES/COMMANDS/HOOKS) y detecta referencias rotas en la tabla de routing de protocols/router.md. Usar cuando el usuario pide /harness-status o un diagnóstico de qué existe realmente en el harness.

  • harness-update

    Detect and apply updates to the harness submodule

  • idea-management

    Captura, madura y promueve objetivos de alto nivel a través de un ciclo de vida estructurado. Usar cuando el usuario quiere registrar una idea, explorarla, o promoverla a planificación.

  • issue-planning

    Refina el requerimiento del usuario y lo convierte en uno o varios issues de GitHub listos para trabajar. Usar cuando el usuario describe trabajo nuevo o quiere planificar.

  • new-project-setup

    Crea un nuevo repositorio consumidor del harness Aura de punta a punta — directorio local, clonado del remoto, submodule .aura pinneado a un tag, identidad, hooks y primer push — dejándolo listo para arrancar `claude .` y empezar a trabajar. Usar cuando el usuario quiere iniciar un proyecto nuevo co

  • observability

    Tres modos. (1) Automático por sesión — process-session.sh calcula output_tokens, tool_uses por categoría, duration_ms y delegation_rate (Issue #179) y appendea a sessions.jsonl; invocado desde el Paso 3.5 de protocols/session_start.md. (2) Bajo demanda agregado — session-report.sh (Issue #265) lee

  • plan-reporting

    Genera reporte de gestión, tareas accionables y análisis de riesgo de un plan estratégico. Usar cuando el usuario pide un reporte de estado de un plan.

  • repo-integrity

    Detecta trabajo stranded (issue cerrado sin PR mergeada) y ramas que requieren limpieza. Invocada desde el Paso 3 de session_start.

  • requesting-code-review

    Use after completing significant implementation work, before merging or moving forward

  • session-trace

    Genera una traza cualitativa del comportamiento real de una sesión (no del flujo diseñado en router.md, sino de lo que efectivamente pasó) como diagrama Archify autoreado por el agente. Usar al cerrar sesión, cuando hubo fricción, decisiones no obvias, o desvíos del protocolo que valga la pena poder

  • spec-validation

    Valida técnicamente que una spec es implementable antes de pasarla al challenger. Usar después de aprobar el diseño en /brainstorm, antes de invocar challenger. HARD-GATE para /write-plan.

  • stack-selection

    Detecta o selecciona el stack tecnológico de la sesión y lo persiste en session-stack.json. Usar al iniciar sesión sin stack detectado, o al invocar /stack.

  • systematic-debugging

    Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

  • test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

  • writing-plans

    Use when you have a spec or requirements for a multi-step task, before touching code

Slash commands (17)

  • /aura:auto-research
  • /aura:brainstorm
  • /aura:doc-check
  • /aura:evaluate-sessions
  • /aura:execute-plan
  • /aura:finish-branch
  • /aura:harness-status
  • /aura:harness-update
  • /aura:idea
  • /aura:new-project
  • /aura:plan-report
  • /aura:plan-work
  • /aura:request-review
  • /aura:run-dev-loop
  • /aura:session-report
  • /aura:stack
  • /aura:write-plan

Subagents (11)

  • browser-control

    Use proactively when no CLI/MCP path solves the task, or the goal is specifically to show/guide the user through something on screen. Use after considering CLI and MCP options first (Pillar P1) and ruling them out.

  • browser-testing

    Use proactively after implementing an issue with UI impact, or after a critical flow change, to validate the app headlessly without human supervision. Use after code changes and before marking a task done, or inside a dev loop.

  • challenger

    Use after the user approves a spec in /brainstorm and before /write-plan, to challenge it against the harness's 7 pillars and spec quality. Use proactively when a harness change (protocols/skills/agents) is proposed without a documented hypothesis (P4).

  • complexity-tiering

    Use proactively before launching an ad-hoc agent outside agentic-dev-loop, to pick the model tier (Haiku/Sonnet/Opus). Use after determining no GitHub issue with a declared **Complejidad:** field exists to read the tier from.

  • doc-guardian

    Use proactively via /doc-check to detect broken references, version inconsistencies, and incomplete structure in Markdown files. Use after changes to .md files and before committing, or after session_end/auto-research when docs changed.

  • evaluator

    Use proactively via /evaluate-sessions to audit whether a past session (or range) respected the harness's declared protocol against the reference flow diagram. Use after a session or batch of sessions has completed, not during active work.

  • github

    Use proactively for git/GitHub operations — creating or cleaning up branches, opening or merging PRs, closing issues, checking branch protection. Use after implementation work is done and ready to open a PR toward develop.

  • infra

    Use proactively for Docker, CI/CD pipelines, environments, and secrets management work. Use after code changes require containerization, workflow, or deployment configuration updates.

  • language

    Use proactively when writing, modifying, or running code for the project's detected stack. Use after task_start.md confirms an issue to implement, applying the stack's conventions and best practices.

  • plan-reporter

    Use proactively via /plan-report to generate a management report (table + escalation/bucket/load/quality analysis) for a strategic plan in Microsoft Planner/Dataverse. Use after the user asks for a plan report, in isolated context so raw report engine output doesn't pollute the main session thread.

  • reviewer

    Use proactively when implementation work is complete and ready for a pre-merge quality gate — code quality, architecture, security, and test coverage. Use after tests pass locally and before opening or merging a PR.

View source on GitHub

Maintain aura?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted