Roberdan

Comprehensive code review with security, patterns, and quality focus

Parallel execution using multiple Claude instances in Kitty terminal

Agile/Waterfall project planning, tracking, and delivery management

McKinsey-level strategic analysis with MECE frameworks and quantitative prioritization

Update project documentation (ADRs, CHANGELOG, running notes) in compact Claude-friendly format

Audit and harden any repository with standardized quality gates, hooks, and scripts

Optimize project instructions and agent setup for lower token usage and higher signal

Pre-PR review catching GitHub Copilot patterns

Lookup reference for executing a task already decided on — code style per language, test/mock boundaries, API conventions, the local CI sequence before push, merge discipline, how to resolve review comments, repo settings and git hooks. Read it when you are about to push, merge, review, or set up a repo; not before.

Evidence-first done-gate. Refuses to mark work complete without concrete artifacts (commit SHA, PR link, file path, test output) verified empirically. The cardinal principle.

Platform-agnostic ship workflow — local CI gate, commit per phase, push, PR with Summary + Test plan, watch CI, merge-commit only. Honors human gates on main.

Helps figure out WHICH problems are worth solving, not just how to solve them. Orchestrates: problem discovery/validation with users (focus-group) → prioritization (severity×frequency×reachability×fit) → solution stress-test (premortem). TRIGGER: 'is it worth solving X', 'vale la pena risolvere X', 'is this a real problem', 'è un problema vero', 'which problem should I attack', 'quale problema attacco', 'should I build this', 'dovrei costruire questo', 'validate before building', 'validiamo prima di costruire', 'prioritize these problems', 'prioritizza questi problemi', 'is this worth building'. YES upstream of any non-trivial build/investment.

Operate the way Roberto D'Angelo works — total autonomy scoped by evidence-first verification, artifact-per-phase discipline, human confirmation before irreversible actions, and his communication voice for drafting. Use whenever asked to operate "in roberto-mode", when starting a complex multi-step task, when drafting a document/email/reply in his voice, when reasoning through a real decision, or when asked "do you know who I am" / "are you in my context".

Portable "loop kit" — inject durable state, terminal-condition, auto-resume and auto-escalation into any session. Makes the loop reliable without a daemon.

Pre-landing code review — correctness, security, patterns, reuse/simplification. Severity-classified findings with file:line evidence. Read-only; the owner applies fixes.

Keep the 3 systems aligned — Obsidian vault (durable memory), Convergio twin plans, in-repo docs. Anti-drift. Read vault before asking; mechanized by post-task-sync hook.

Wrap spawned-worker briefs (subagent or background agent) with auto-register + heartbeat boilerplate so they stay visible in the Convergio daemon. Use this when invoking the Task tool for code-mutating work in this repo.

Register the current Claude Code session as a Convergio agent so the local daemon can see who is online, broadcast presence on the `system.session-events` bus, and coordinate with peer sessions in the same repo. Invoke once at session start; the heartbeat and detach flow are wired by the companion `.claude/settings.json` hooks (see PRD-001 Artefact 2).