feature-workflow

Designs API contracts and data flow for features. Specializes in GraphQL schema design, Lambda function specifications, database structures, and authorization patterns. Creates clear API contracts between frontend and backend with complete error handling specifications.

Use PROACTIVELY when inheriting legacy codebases or before making changes to undocumented systems. This agent specializes exclusively in reverse-engineering complex code - tracing data flows, uncovering hidden dependencies, mapping system architecture, and identifying technical debt. Automatically generates comprehensive system documentation from code analysis, reveals undocumented business logic, and creates dependency graphs for safe refactoring.

MUST BE USED whenever code is created or modified to maintain living documentation. This agent specializes exclusively in generating and maintaining technical documentation - creating API references, architecture diagrams, README files, and inline comments that stay synchronized with code. Automatically detects undocumented code, generates comprehensive documentation with working examples, and ensures all public APIs have complete docstrings with usage examples.

Designs React component architecture and state management for frontend features. Specializes in component hierarchy, props interfaces, state flow, and integration patterns. Creates clear component blueprints that are maintainable, testable, and performant.

Designs integration layer between frontend and backend. Specializes in GraphQL query usage, state synchronization, authorization flow, caching strategy, and error handling. Creates clear integration patterns that are secure, performant, and reliable.

Auto-load active audit context when working with audited code. Use when user is working on code that has an active audit session, discussing audit findings, or making changes related to a runtime audit. Silently loads audit session data to inform responses.

Check project backlog when discussing feature ideas or priorities. Use when user mentions adding features, asks what's planned, discusses priorities, or proposes new functionality. Silently reads DASHBOARD.md to show relevant items and suggest /feature-capture for untracked ideas.

Runtime behavior auditing through systematic log injection. Use when user wants to understand what code is doing at runtime, debug complex flows, or audit a process.

Interactive workflow for adding items to the backlog. Use when user wants to add a new feature, track an idea, capture requirements, or mentions something that should be in the backlog.

Execute a feature implementation plan from a clean context. Use when starting implementation after planning, or when resuming work on an in-progress feature. Reads plan.md and executes implementation steps.

4 hooks across 2 events