agent-triforce

Guide for installing Agent Triforce CI/CD workflow templates into your GitHub Actions pipeline

View and manage context loading profiles for Agent Triforce skills.

Estimate token cost for an Agent Triforce workflow based on the routing configuration

Generate the Agent Triforce system dashboard (HTML overview of specs, reviews, tech debt, checklists, and workflow status)

View, create, approve, or override approval gates between agents.

Check growth phase, pre-launch readiness gates, and milestone-gated actions

Set up issue tracker integration (Linear, Jira, or GitHub Issues) via MCP

Set up LSP (Language Server Protocol) integration for real-time code intelligence

Set up MCP (Model Context Protocol) integrations for static analysis and issue tracking

View and resolve cross-agent memory conflicts (detects when agents hold contradictory assessments of the same entity)

Display the Agent Triforce checklist methodology reference

Rebuild the codebase knowledge index for the project.

Interactive setup wizard for Agent Triforce — detects tech stack, creates project structure, and configures agents

Show current workflow status, checklist progress, blockers, and session analytics

Display Agent Triforce team configuration, roles, and orchestration info

QA Engineer and Security Auditor agent for code review, security auditing, testing verification, compliance checking, dead code detection, and quality gates. MUST BE USED for any review, audit, quality check, or security assessment. Use PROACTIVELY after any code changes or before releases.

Developer and Software Architect agent for architecture decisions, full-stack implementation, code writing, testing, infrastructure, CI/CD, and technical documentation. MUST BE USED for any coding, implementation, architecture, refactoring, or technical task. Use PROACTIVELY when the user needs code written, bugs fixed, or systems built.

Product Manager agent for product strategy, feature specifications, user stories, business logic, prioritization, and roadmap management. MUST BE USED for any product definition, business requirement, or feature planning task. Use PROACTIVELY when the user discusses features, requirements, business logic, or product decisions.

Post-implementation business assessment by Prometeo (PM). Verifies success metrics achievement, scope compliance, acceptance criteria business interpretation, risk materialization, and product decision closure. Outputs structured report with verdict and confidence score.

Analyzes checklist effectiveness by tracking hit rates, identifying stale items, and finding coverage gaps. Generates evolution suggestions following Boorman's principles. Use periodically to keep checklists field-tested and relevant.

Scans the codebase for dead code, tech debt, outdated dependencies, and code quality issues. Use periodically or before releases to maintain code hygiene.

Creates a complete product feature specification. Use when defining new features, writing user stories, or planning product work. Generates structured specs in docs/specs/.

Generates test cases for a module or function following FIRST principles and Arrange-Act-Assert pattern. Detects test framework from project config. Use to bootstrap test coverage for existing code or as the Red phase of TDD.

Implements a feature from its specification. Reads the spec, designs architecture, writes code, tests, and documentation. Use after a feature spec has been approved.

Rebuilds the codebase knowledge index at docs/codebase-index.json. Scans all source files for module structure, exports, dependencies, and tech debt hotspots. Shared across all three agents.

Pre-release verification with structured report. Validates test coverage, security status, CHANGELOG completeness, dependency freshness, tech debt severity. Outputs GO/NO-GO recommendation with confidence score and specific remediation steps.

Addresses and fixes findings from a QA code review. Reads the review report, fixes critical and warning issues, and prepares for re-verification.

Deep security audit of code, dependencies, and infrastructure. Checks OWASP Top 10, authentication, authorization, data protection, and dependency vulnerabilities. Use before releases or after significant changes.

Runs controlled failure simulations to verify that agents correctly invoke their Non-Normal (emergency) checklists. Available scenarios: ambiguous-spec, failing-tests, security-finding. All outputs are labeled SIMULATION MODE and written to docs/training/.

Generates a spec-to-implementation traceability matrix linking acceptance criteria from specs to implementation files, test cases, and review findings. Supports IEEE 830 compliance audits.

4 hooks across 2 events