agent-triforce: Instructions file for Claude Code

🔱 Agent Triforce — Multi-Agent Development System

System Overview

This project uses 3 specialized agents. Always use the appropriate agent for each task:

• Prometeo (PM): Product strategy, feature specs, business logic, prioritization
• Forja (Dev): Architecture, implementation, infrastructure, documentation
• Centinela (QA): Security audit, code review, testing, compliance, dead code detection

Agent Invocation

Use agents explicitly:

• "Use Prometeo to define the feature for [X]"
• "Use Forja to implement [X]"
• "Use Centinela to audit [X]"

Or use skills:

• /feature-spec [description] → Runs with Prometeo
• /implement-feature [spec-name] → Runs with Forja
• /security-audit [scope] → Runs with Centinela
• /code-health → Runs with Centinela
• /release-check → Runs with Centinela
• /review-findings [review-file] → Runs with Forja
• /business-review [feature-name] → Runs with Prometeo

Checklist Methodology

This system applies principles from The Checklist Manifesto (Atul Gawande) and Boeing's checklist engineering (Daniel Boorman). Checklists are not training wheels — they are cognitive safety nets that catch the flaws of memory, attention, and thoroughness inherent in all of us.

Core Philosophy

• Ineptitude, not ignorance: Failures come from not applying what we already know, not from lack of knowledge
• Checklists supplement expertise: They are reminders of the most critical steps — not comprehensive how-to guides. They do not replace skill; they enhance it
• "FLY THE AIRPLANE": Step 1 of any emergency checklist is to remember your primary mission. Never get so lost in process that you forget the goal
• Discipline is professionalism: The discipline to consult a checklist, no matter how experienced you are, is what separates reliable systems from fragile ones
• Systems over components: Individually excellent agents aren't enough — they must mesh together through structured coordination

Checklist Design Rules (Boorman's Principles)

Every checklist in this system MUST follow these rules:

1. Clear pause point: A specific moment where you STOP and consult the checklist
2. 5-9 killer items only: Focused on the steps most dangerous to skip and most commonly overlooked. Not everything — just the critical few
3. Under 60 seconds: If it takes longer, it will be skipped or shortcut
4. Simple, exact wording: No vague language. Each item is a concrete, verifiable action
5. DO-CONFIRM or READ-DO: Every checklist declares its type (see below)
6. Field-tested and updated: Checklists evolve based on actual failures and lessons learned. Update them when they catch something new or miss something important