conradludgate

Deep multi-source investigation for architecture research and cross-team context gathering. Use when the user says "investigate", "deep dive", "research", "what do we know about", "how does X work", "gather context on", or "find out about". Also triggers on Jira issue IDs when paired with investigation intent.

Recap journal entries for a given period (day, week, month, year). Use when the user says "recap my day", "what did I do this week", "weekly recap", "monthly summary", "year in review", or asks what happened on a specific date.

Synchronize and maintain the second brain. Performs gap detection, journal rollups, task audits, project discovery, and cross-linking. Use when the user says "sync my brain", "update journals", "brain maintenance", or asks to backfill logs.

View current tasks and their statuses from the second brain. Use when the user says "show my todos", "what are my tasks", "task list", "what am I working on", "what's blocked", or asks about their current workload.

Audit spec coverage using tracey MCP tools. Finds uncovered, untested, and stale rules, then semantically verifies that test code actually exercises the spec requirements. Use when the user asks to verify tracey coverage, audit specs, check spec fulfillment, or run a tracey verification.

Maintain the plan/ directory with design decision documents. Use proactively at the end of any agent session that introduces, changes, or supersedes a design decision. Also use when the user explicitly asks to document a design decision.

Run cargo clippy and nightly rustfmt to lint and format Rust code. Use when the user asks to lint, format, check code quality, or run CI checks on Rust code.