outfitter-stack

Adopt Outfitter Stack patterns in a codebase through a phased workflow

Quick audit of current file or directory for Outfitter Stack compliance

Use this agent when working with @outfitter/* packages, including Result types, Handler contracts, error taxonomy, or any Stack-based architecture patterns. This agent routes to the appropriate skill based on task type and executes that skill's workflow completely.\n\n**Examples:**\n\n<example>\nContext: User wants to review existing code for Stack compliance.\nuser: "Review my auth handler for Stack compliance"\nassistant: "I'll use the stack-specialist agent to perform a comprehensive Stack compliance audit."\n<Task tool invocation with stack-specialist agent>\n</example>\n\n<example>\nContext: User is designing a new feature that needs handlers.\nuser: "I need to design a payment processing system with handlers"\nassistant: "Let me delegate this to the stack-specialist agent to run the architecture workflow."\n<Task tool invocation with stack-specialist agent>\n</example>\n\n<example>\nContext: User is implementing a new handler.\nuser: "Implement a createUser handler with validation"\nassistant: "I'll launch the stack-specialist agent to implement this using the TDD workflow with proper Result types."\n<Task tool invocation with stack-specialist agent>\n</example>\n\n<example>\nContext: User encounters an error with Result types.\nuser: "My handler is returning errors incorrectly, the error category doesn't match"\nassistant: "I'll use the stack-specialist agent to debug this Stack error taxonomy issue."\n<Task tool invocation with stack-specialist agent>\n</example>\n\n<example>\nContext: User wants to migrate existing code to Stack patterns.\nuser: "Convert my existing Express routes to Stack handlers"\nassistant: "I'll delegate this to the stack-specialist agent to run the adoption workflow for migrating to Stack patterns."\n<Task tool invocation with stack-specialist agent>\n</example>\n\n**Trigger keywords:** review, audit, check, compliance, validate, design, plan, structure, architecture, handlers, implement, build, create, add, fix, debug, troubleshoot, error, issue, adopt, convert, migrate, upgrade, Result, Handler, @outfitter/*, Stack.

Design stack-based systems using @outfitter/* packages. Use when planning new projects, choosing packages, designing handler architecture, or when "architecture", "design", "structure", "plan handlers", or "error taxonomy" are mentioned.

Scan codebase for Outfitter Stack adoption candidates. Identifies throw statements, console usage, hardcoded paths, and custom errors. Use when assessing adoption scope or checking readiness.

Troubleshoots Outfitter Stack issues including Result handling, MCP problems, CLI output, exit codes, and logging. Use when debugging stack-specific issues, unexpected errors, wrong output modes, or when "debug Result", "MCP not working", "wrong exit code", or "logging issue" are mentioned.

Creates GitHub issues for problems discovered while using @outfitter/* packages. Use when finding bugs, missing features, unclear documentation, or improvement opportunities.

Reference for Outfitter Stack patterns including Result types, Handler contract, Error taxonomy, and @outfitter/* package conventions. Use when learning the stack, looking up patterns, understanding packages, or when "Result", "Handler", "error taxonomy", "OutfitterError", "CLI output", "pagination", "MCP server", "MCP tool", "structured logging", "redaction", "test handler", "daemon", "IPC", or "@outfitter/*" are mentioned.

Audits code for Outfitter Stack compliance including Result types, error handling, logging patterns, and path safety. Use for pre-commit reviews, code quality checks, migration validation, or when "audit", "check compliance", "review stack", or "stack patterns" are mentioned.

Templates for creating handlers, CLI commands, MCP tools, and daemon services following Outfitter Stack conventions. Use when scaffolding new components, creating handlers, adding commands, or when "create handler", "new command", "add tool", "scaffold", "template", or "daemon service" are mentioned.