cassel/bi-agents
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
647cbec54f1c099484c8d9d97c11a05136c87329
bi-agents/.agents/skills/bmad-code-review/steps/step-04-present.md
Cassel 647cbec54f docs: update all documentation and add AI tooling configs 
- Rewrite README.md with current architecture, features and stack
- Update docs/API.md with all current endpoints (corporate, BI, client 360)
- Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL
- Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente)
- Add docs/INDEX.md documentation index
- Add PROJETO.md comprehensive project reference
- Add BI-CCC-Implementation-Guide.md
- Include AI agent configs (.claude, .agents, .gemini, _bmad)
- Add netbird VPN configuration
- Add status report

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 13:29:03 -04:00

1.7 KiB
Raw Blame History

Step 4: Present

RULES

  • YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config {communication_language}
  • Do NOT auto-fix anything. Present findings and let the user decide next steps.

INSTRUCTIONS

  1. Group remaining findings by category.

  2. Present to the user in this order (include a section only if findings exist in that category):

    • Intent Gaps: "These findings suggest the captured intent is incomplete. Consider clarifying intent before proceeding."

      • List each with title + detail.

    • Bad Spec: "These findings suggest the spec should be amended. Consider regenerating or amending the spec with this context:"

      • List each with title + detail + suggested spec amendment.

    • Patch: "These are fixable code issues:"

      • List each with title + detail + location (if available).

    • Defer: "Pre-existing issues surfaced by this review (not caused by current changes):"

      • List each with title + detail.

  3. Summary line: X intent_gap, Y bad_spec, Z patch, W defer findings. R findings rejected as noise.

  4. If clean review (zero findings across all layers after triage): state that N findings were raised but all were classified as noise, or that no findings were raised at all (as applicable).

  5. Offer the user next steps (recommendations, not automated actions):

    • If patch findings exist: "These can be addressed in a follow-up implementation pass or manually."
    • If intent_gap or bad_spec findings exist: "Consider running the planning workflow to clarify intent or amend the spec before continuing."
    • If only defer findings remain: "No action needed for this change. Deferred items are noted for future attention."

Workflow complete.