tribunal-kit 5.8.5 → 6.0.1

package/.agent/workflows/brainstorm.md

@@ -1,6 +1,14 @@
 ---
 description: Structured brainstorming for projects and features. Uses Socratic questioning to explore multiple options before committing to an approach. No implementation during this phase — only exploration.
-required-skills: brainstorming
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - brainstorming
+  - shape
+  - project-planner
+scripts-binding:
+  - .agent/scripts/verify_all.js
 ---
 
 # /brainstorm — Structured Idea Exploration
@@ -9,15 +17,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE generating any options:
-□ package.json         → Understand existing stack constraints
-□ tsconfig.json        → Understand language/framework version
-□ Project root listing → Understand project structure and scale
-□ .agent/skills/brainstorming/SKILL.md → Load domain question banks
-```
+Before generating options or conducting Socratic architectural exploration, you MUST inspect:
+1. Technology Stack Manifest (`package.json`, `tsconfig.json`) → Confirm existing language/framework versions and active library boundaries
+2. Workspace File Layout → Understand current module scale and project structure before proposing architectural shifts
+3. Pure Exploration Constraint → Enforce zero code edits or file creation during brainstorm phase; restrict output to options, tradeoffs, and recommendations
 
 ---
 

package/.agent/workflows/changelog.md

@@ -1,6 +1,14 @@
 ---
 description: Auto-generate changelogs from git history. Categorizes commits by type (feat/fix/chore/breaking) and follows Keep a Changelog format. Requires conventional commit messages for accurate categorization.
-required-skills: github-operations
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - github-operations
+  - git-pro
+  - readme-builder
+scripts-binding:
+  - .agent/scripts/lint_runner.js
 ---
 
 # /changelog — Git History to Changelog
@@ -9,14 +17,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE generating changelog:
-□ git log --oneline -20       → Verify commit message format
-□ package.json                → Identify current version
-□ CHANGELOG.md (if exists)    → Understand existing format/history
-```
+Before generating changelogs or parsing git history, you MUST inspect:
+1. Git Commit Trajectory (`git log --oneline -30`) → Verify presence of conventional commit tags (`feat:`, `fix:`, `chore:`, `BREAKING CHANGE:`)
+2. Package Manifest & Version (`package.json`) → Retrieve current release version and target release tag
+3. Keep a Changelog Formatting Standard → Enforce categories: Added, Changed, Deprecated, Removed, Fixed, Security
 
 ---
 

package/.agent/workflows/create.md

@@ -1,6 +1,16 @@
 ---
 description: Create new application command. Triggers full stack creation from requirements gathering → stack selection → scaffolding → Tribunal code generation. Everything through the pipeline before writing a single file.
-required-skills: app-builder, architecture
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - app-builder
+  - architecture
+  - project-planner
+scripts-binding:
+  - .agent/scripts/auto_preview.js
+  - .agent/scripts/verify_all.js
+  - .agent/scripts/lint_runner.js
 ---
 
 # /create — Full Application Builder
@@ -9,14 +19,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE scaffolding:
-□ Current directory listing → Ensure target directory is empty or confirm overwrite
-□ .env.example            → Know available environment variables
-□ Node/npm version         → Ensure compatibility with chosen stack
-```
+Before scaffolding a new application, you MUST inspect:
+1. Target Directory State → Confirm directory listing is empty or obtain explicit user confirmation before overwriting existing files
+2. Runtime & Environment Context → Check Node/npm version and inspect `.env.example` if available
+3. Human Gate Before Disk Modification → Enforce explicit approval of Socratic requirements, stack selection, and scaffolding plan before creating any files
 
 ---
 

package/.agent/workflows/debug.md

@@ -1,6 +1,15 @@
 ---
 description: Debugging command. Activates DEBUG mode for systematic problem investigation using the 4-phase methodology (Collect → Hypothesize → Test → Fix). No fix is suggested until the root cause is confirmed and tested. No random changes. No guessing.
-required-skills: systematic-debugging
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - systematic-debugging
+  - test-result-analyzer
+  - clean-code
+scripts-binding:
+  - .agent/scripts/test_runner.js
+  - .agent/scripts/lint_runner.js
 ---
 
 # /debug — Root Cause Investigation
@@ -9,16 +18,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE hypothesizing:
-□ Error output / stack trace  → Exact error text, not a paraphrase
-□ Target file                → The file referenced in the error
-□ git diff (recent changes)  → What changed since last working state
-□ .env / .env.example        → Check for missing/rotated secrets
-□ package.json               → Check for recent dependency changes
-```
+Before investigating or attempting any code modification during a bug report, you MUST inspect:
+1. Exact Error Traceback / Stack Log → Read raw error logs without paraphrasing; ban making diagnostic hypotheses without tracebacks
+2. Target File & Callers → Inspect file referenced in error trace along with its upstream callers
+3. Recent Changes (`git diff`) → Inspect recent edits to identify regressions before mutating code
 
 ---
 

package/.agent/workflows/deploy.md

@@ -1,6 +1,16 @@
 ---
 description: Production deployment command. Runs pre-flight safety checks (tests, type-check, lint, security, build), creates a rollback baseline, confirms Human Gate, then executes deployment. Requires explicit human approval before going live.
-required-skills: deployment-procedures, devops-engineer
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - deployment-procedures
+  - devops-engineer
+  - verify_all
+scripts-binding:
+  - .agent/scripts/verify_all.js
+  - .agent/scripts/security_scan.js
+  - .agent/scripts/bundle_analyzer.js
 ---
 
 # /deploy — Production Deployment
@@ -9,14 +19,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE deploying:
-□ package.json                → Identify build/test scripts
-□ CI/CD configs               → GitHub Actions, render.yaml, fly.toml
-□ Database schema             → Check if migrations are pending
-```
+Before triggering production deployment or executing deploy scripts, you MUST inspect:
+1. Full Pre-Flight Verification Suite (`verify_all.js`) → Verify tests, type-checking, lint, security scans, and production build output cleanly
+2. CI/CD Manifests (`.github/workflows`, `fly.toml`, `render.yaml`, etc.) → Check deployment targets and environment variable requirements
+3. Human Gate & Rollback Baseline → Confirm baseline git tag/commit and secure explicit human approval before publishing release
 
 ---
 

package/.agent/workflows/enhance.md

@@ -1,6 +1,15 @@
 ---
 description: Add or update features in existing applications. Performs impact analysis before any code change — identifies all dependents, detects breaking changes, generates Tribunal-reviewed modifications. No change is written to disk without Human Gate approval.
-required-skills: clean-code
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - clean-code
+  - codebase-design
+  - test-engineer
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/test_runner.js
 ---
 
 # /enhance — Feature Addition & Modification
@@ -9,16 +18,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE any modification:
-□ Target file              → Understand current implementation
-□ Target file's importers  → Map the impact zone (grep callers)
-□ package.json             → Verify dependencies exist
-□ tsconfig.json            → Understand path aliases and strictness
-□ Related test files        → Know what tests exist for this module
-```
+Before modifying existing features or appending functionality, you MUST inspect:
+1. Impact Zone Identification → Grep for all callers and importers of the target file to map blast radius
+2. Existing Contract & Unit Tests → Inspect existing tests and type signatures for the target module to prevent regression
+3. Breaking Change Detection → Ensure signature changes update all dependent call sites simultaneously before writing to disk
 
 ---
 

package/.agent/workflows/fix.md

@@ -1,6 +1,15 @@
 ---
 description: Auto-fix known issues with lint, formatting, imports, and TypeScript errors. Runs lint_runner.js and auto-fixers. Human approval required before applying any changes. Shows a diff of what will change before writing to disk.
-required-skills: lint-and-validate, clean-code
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - lint-and-validate
+  - clean-code
+  - typescript-advanced
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/verify_all.js
 ---
 
 # /fix — Automated Error Resolution
@@ -9,14 +18,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE fixing:
-□ package.json                → Identify lint/format tools and scripts
-□ tsconfig.json               → Understand strictness levels
-□ .eslintrc / prettierrc      → Understand code style rules
-```
+Before executing auto-fixers or modifying code files to resolve lint/type issues, you MUST inspect:
+1. Workspace Linter & Compiler Settings (`tsconfig.json`, `.eslintrc`, `biome.json`) → Confirm rule strictness and formatting standards
+2. Target File Lint Output → Execute `node .agent/scripts/lint_runner.js` to gather precise error line numbers and rule IDs
+3. Diff Verification Before Disk Write → Show explicit diff of proposed changes and confirm Human Gate approval before saving
 
 ---
 

package/.agent/workflows/generate.md

@@ -1,6 +1,16 @@
 ---
 description: Generate code using the full Tribunal Anti-Hallucination pipeline. Maker generates grounded in real project context at low temperature → domain-selected reviewers audit in parallel → Human Gate for final approval. Nothing is written to disk without explicit approval.
-required-skills: auto-detected from request keywords (see Reviewer Auto-Selection table)
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - clean-code
+  - codebase-design
+  - lint-and-validate
+scripts-binding:
+  - .agent/scripts/lint_runner.js
+  - .agent/scripts/security_scan.js
+  - .agent/scripts/verify_all.js
 ---
 
 # /generate — Hallucination-Free Code Generation
@@ -9,16 +19,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE generating any code (MANDATORY — never skip):
-□ package.json      → Verify all imports exist before using them
-□ tsconfig.json     → Understand strictness, paths aliases, target version
-□ context/*.acf     → Load explicit goals, rules, and boundaries
-□ .env.example      → Know available environment variables
-□ Referenced files   → Understand actual data shapes and types
-```
+Before generating code modules or invoking the Maker pipeline, you MUST inspect:
+1. Workspace Package Dependencies (`package.json`) → Confirm all imported libraries exist; ban unverified phantom imports
+2. Type Definitions & Path Aliases (`tsconfig.json`) → Verify module resolution paths and compiler strictness
+3. Parallel Tribunal Review Assignment → Select relevant domain reviewers (`logic`, `security`, `frontend`, `backend`, `database`, `mobile`) prior to Human Gate submission
 
 ---
 
@@ -128,7 +134,7 @@ complexity-reviewer→ Enforces the Dependency Ladder to prevent over-engineerin
 | `aria`, `wcag`, `a11y`, `accessibility`                     | `accessibility-reviewer` + `ui-ux-auditor`                     |
 | `import`, `package`, `npm`, `require`                       | `dependency-reviewer`                                          |
 
-> For maximum safety on critical code: use `/tribunal-full` for all 19 reviewers simultaneously.
+> For maximum safety on critical code: use `/tribunal-full` for all 21 reviewers simultaneously.
 
 ---
 

package/.agent/workflows/marathon.md

@@ -1,6 +1,15 @@
 ---
 description: Long-running agent harness for multi-session projects. Decomposes specs into atomic features tracked in JSON, ensures clean handoffs between sessions, and provides structured progress tracking. Based on Anthropic's long-running agent patterns.
-required-skills: harness-protocol, agent-organizer
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - harness-protocol
+  - agent-organizer
+  - project-planner
+scripts-binding:
+  - .agent/scripts/session_manager.js
+  - .agent/scripts/verify_all.js
 ---
 
 # /marathon — Long-Running Agent Harness
@@ -9,14 +18,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE marathon start/continue:
-□ progress.json               → See current marathon state
-□ feature_list.json           → View remaining tasks
-□ git log --oneline -5        → Check recent commits
-```
+Before initiating or resuming a multi-session marathon harness, you MUST inspect:
+1. Marathon State Ledger (`progress.json`, `feature_list.json`) → Verify current session index, completed features, and active task
+2. Session Continuity Manager (`.agent/scripts/session_manager.js`) → Verify state snapshot before context truncation
+3. Atomic Feature Handoff Protocol → Ensure each session completes exactly ONE atomic feature, runs `verify_all.js`, and commits state before handoff
 
 ---
 

package/.agent/workflows/migrate.md

@@ -1,6 +1,16 @@
 ---
 description: Migration workflow for framework upgrades, dependency bumps, and database migrations. Impact analysis first, expand-and-contract for DB, dependency compatibility matrix before upgrading, rollback tested before deploy.
-required-skills: plan-writing, architecture
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - plan-writing
+  - architecture
+  - database-design
+scripts-binding:
+  - .agent/scripts/dependency_analyzer.js
+  - .agent/scripts/schema_validator.js
+  - .agent/scripts/verify_all.js
 ---
 
 # /migrate — Safe Migration Execution
@@ -9,14 +19,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE migrating:
-□ package.json                → Identify current vs target dependency versions
-□ Target files/schemas         → Understand the exact structural changes needed
-□ Release notes/Changelogs     → Understand breaking changes in the target version
-```
+Before running framework upgrades, major dependency bumps, or database migrations, you MUST inspect:
+1. Dependency Compatibility Matrix (`dependency_analyzer.js`) → Verify target version peer dependencies and breaking changes
+2. Database Expand-and-Contract Plan (`schema_validator.js`) → Ensure database column changes add new fields before dropping old ones
+3. Rollback Protocol Verification → Test local rollback procedure (e.g. SQLite backup or DB transaction revert) before applying migration
 
 ---
 

package/.agent/workflows/minimal.md

@@ -0,0 +1,94 @@
+---
+description: Analyze requested implementation for minimal viable change. Enforces the 7-level Decision Order (NO_CHANGE to CREATE), Change Budget estimation, Minimality Score (0-100), Complexity Flags detection, and repository search.
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 6.0.0
+last-updated: 2026-07-30
+required-skills:
+  - clean-code
+  - codebase-design
+scripts-binding:
+  - .agent/scripts/minimal_change_engine.js
+  - .agent/scripts/case_law_manager.js
+---
+
+# /minimal — Minimal Change Governance Workflow
+
+$ARGUMENTS
+
+---
+
+## Mandatory Pre-Flight Context Inspection
+
+Before proposing any code change, you MUST evaluate the **10 Core Governance Questions**:
+1. Does anything need to change? (`NO_CHANGE`)
+2. Does the repository already solve this? (`REUSE`)
+3. Does an existing function, component, utility, service, or abstraction solve it? (`REUSE`)
+4. Does the language standard library solve it? (`REUSE`)
+5. Does the framework or platform solve it? (`REUSE`)
+6. Does an existing dependency solve it? (`REUSE`)
+7. Is configuration enough? (`CONFIGURE`)
+8. Is deletion or simplification better than addition? (`DELETE`)
+9. Is the proposed abstraction necessary for the current requirement? (`MODIFY`/`EXTEND`)
+10. What is the smallest implementation that satisfies the request? (`MODIFY`/`EXTEND` vs `CREATE`)
+
+---
+
+## Sub-Commands
+
+| Command | Description |
+| :--- | :--- |
+| `/minimal` | Analyze requested implementation and determine smallest viable change footprint |
+| `/minimal-review` | Review proposed change diff for unnecessary complexity and file proliferation |
+| `/change-budget` | Display estimated Change Budget (files added/modified, lines, deps, abstractions) |
+| `/complexity-audit` | Audit proposal for 14 standardized complexity flags and overengineering patterns |
+| `/reuse-check` | Search repository for existing functions, symbols, and utilities before creating code |
+
+---
+
+## Decision Order Hierarchy
+
+Evaluate solutions strictly in this order:
+```
+NO_CHANGE ➔ REUSE ➔ CONFIGURE ➔ DELETE ➔ MODIFY ➔ EXTEND ➔ CREATE
+```
+
+---
+
+## Output Schema
+
+```
+━━━ Minimal Change Governance Audit ━━━━━━━━━━━━━━━━━━━━━━
+
+Minimality Score:          88/100 (PASSED)
+Decision Classification:   MODIFY
+Strictness Mode:           balanced
+
+━━━ Change Budget ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+files_added:               0
+files_modified:            2
+dependencies_added:        0
+new_abstractions:          0
+estimated_lines_added:     14
+estimated_lines_removed:    4
+
+━━━ Complexity Flags ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ None detected
+
+━━━ Reuse Opportunities ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+- Extend src/utils/http.ts for retry policy rather than creating a new service file
+
+━━━ Recommendation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Proceed with MODIFY strategy on src/utils/http.ts
+```
+
+---
+
+## Usage Examples
+
+```
+/minimal add request retry handling to API calls
+/minimal-review src/services/retryQueue.ts
+/change-budget
+/complexity-audit
+/reuse-check fetchRetry
+```

package/.agent/workflows/orchestrate.md

@@ -1,6 +1,15 @@
 ---
 description: Coordinate multiple agents for complex tasks. Use for multi-perspective analysis, comprehensive reviews requiring different domain expertise, or tasks where a single agent would miss domain-specific failures. Fan-Out dispatch → parallel execution → Fan-In synthesis → Human Gate.
-required-skills: agent-organizer, parallel-agents
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - agent-organizer
+  - parallel-agents
+  - swarm-dispatcher
+scripts-binding:
+  - .agent/scripts/swarm_dispatcher.js
+  - .agent/scripts/verify_all.js
 ---
 
 # /orchestrate — Multi-Agent Coordination
@@ -9,14 +18,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE orchestrating:
-□ Target scope                → Identify the boundaries of the review/task
-□ Agent list                  → Determine which specialist agents are needed
-□ Context budget              → Determine how to split files among agents
-```
+Before dispatching multi-agent orchestrations or parallel sub-task workers, you MUST inspect:
+1. Orchestrator Payload Validator (`swarm_dispatcher.js`) → Validate subagent payload contracts and JSON schema before fan-out
+2. Context Window Budget Allocation → Provide scoped `context_summary` per worker; ban dumping full conversation history to workers
+3. Fan-In Synthesis & Human Gate → Collect all worker outputs via `Promise.allSettled()` pattern and present unified synthesis before writing disk changes
 
 ---
 

package/.agent/workflows/performance-benchmarker.md

@@ -1,6 +1,15 @@
 ---
 description: Run standardized performance benchmarks including Lighthouse CI, bundle analysis, and API latency checks. Records before/after metrics. No optimization claims without measured evidence.
-required-skills: performance-profiling, vitals-reviewer
+tools: Read, Grep, Glob, Bash, Edit, Write
+version: 3.0.0
+last-updated: 2026-07-30
+required-skills:
+  - performance-profiling
+  - vitals-reviewer
+  - 60fps-animation
+scripts-binding:
+  - .agent/scripts/bundle_analyzer.js
+  - .agent/scripts/verify_all.js
 ---
 
 # /performance-benchmarker — Evidence-Based Performance Measurement
@@ -9,14 +18,12 @@ $ARGUMENTS
 
 ---
 
-## $CONTEXT_REQUIRED
+## Mandatory Pre-Flight Context Inspection
 
-```
-Read BEFORE benchmarking:
-□ package.json                → Identify build/start scripts and profiling tools
-□ Application URL             → Verify the local URL and port
-□ Database connection          → Verify if DB profiling is supported
-```
+Before running performance benchmarks or capturing latency metrics, you MUST inspect:
+1. Target App Environment & Build Command (`package.json`) → Confirm production build output and dev/preview server URL
+2. Benchmark Scripts Availability (`.agent/scripts/bundle_analyzer.js`) → Verify automated bundle and latency measurement tooling
+3. Before/After Metric Recording Constraint → Require side-by-side metric tables (LCP, CLS, INP, TTFB, Bundle Size) for every benchmark pass
 
 ---