hamlet

Use when assessing codebase architecture and you feel pressure to soften critique, lead with strengths, or frame problems diplomatically - provides evidence-based critical assessment resisting relationship and economic pressures

Use when cataloging technical debt under time pressure and tempted to explain choices instead of delivering document - enforces execution discipline with scoped delivery patterns for partial catalogs

Use when stakeholders pressure you to change technical priorities and you're tempted to compromise on security-first or call it synthesis - enforces risk-based prioritization over stakeholder preferences

Use when you have architecture documentation from system-archaeologist and need critical assessment, refactoring recommendations, or improvement prioritization - routes to appropriate architect specialist skills

Master A2C, A3C, SAC, TD3 - actor-critic methods for continuous control

Master ε-greedy, UCB, curiosity-driven, RND, intrinsic motivation exploration

Master Dyna-Q, MBPO, Dreamer - model-based RL with world models and planning

Master QMIX, MADDPG, CTDE - multi-agent learning with coordination and credit assignment

Master CQL, IQL, BCQ - offline RL from fixed datasets without environment interaction

Master REINFORCE, PPO, TRPO - direct policy optimization with trust regions

Master reward function design - potential-based shaping, hacking patterns, validation

Systematic RL debugging - diagnose learning failures, common bugs, diagnosis trees

Gym/gymnasium API - custom environments, spaces, wrappers, vectorization, debugging

Rigorous RL evaluation - statistical protocols, train/test discipline, metrics, generalization

Master RL theory - MDPs, value functions, Bellman equations, value/policy iteration, TD

Routes to appropriate deep-RL skills based on problem type and algorithm family

Master DQN, Double DQN, Dueling DQN, Rainbow - value-based methods for discrete actions

Analyze unfamiliar codebases systematically to produce subsystem catalog entries - emphasizes strict contract compliance and confidence marking

Synthesize subsystem catalogs and architecture diagrams into comprehensive, navigable architecture reports - codifies synthesis strategies and professional documentation patterns

Generate C4 architecture diagrams from subsystem catalogs - codifies abstraction strategies, notation conventions, and selection criteria

Use when analyzing existing codebases to generate architecture documentation - coordinates subagent-driven exploration with mandatory workspace structure, validation gates, and pressure-resistant workflows

Validate architecture artifacts against contracts and consistency requirements - codifies systematic validation practices with professional reporting