rails-specialist

Oleh-Rudko

Rails backend specialist for Acuity PPM. Use when working with rails_api/: controllers, models, services, migrations, blueprinters, specs. Knows real project patterns: ApiController + Secured, Blueprinter, Assignment-based roles, N+1 prevention, multi-tenant through Company → Organization → Portfolio/ProposalPortfolio.

quality-checklists

Oleh-Rudko

Quality checklists for each Acuity PPM layer. Used by the orchestrator after each Story and by the code-reviewer. Specific to real project patterns: ApiController auth, access_groups permissions, snake_case types, serverHooksForGraphqlTS.

task-workflow

Oleh-Rudko

MAIN ORCHESTRATOR. Use ALWAYS when starting a new task, feature, bug fix, or refactoring. Coordinates subagents for research, planning, and review. Each phase = separate subagent with file handoff to avoid compact. Results are written to docs/plans/[slug]/ as Epic → Stories → Tasks.

code-review

Oleh-Rudko

Code review process. Use when you need to check code quality after changes, before commit, or when asked "/review", "check code", "do a review". ALWAYS delegates to code-reviewer agent — never does self-check.

hasura-specialist

Oleh-Rudko

Hasura GraphQL specialist for Acuity PPM. Use when working with hasura/: metadata, permissions, relationships, actions, functions. Knows real permission chain through access_groups, two portfolio types (portfolio + proposal_portfolio), computed fields, PostgreSQL functions. MUST study context BEFORE changes.