Analyze

Investigate a task, idea, ticket, PR, or review-fix backlog and return an evidence-backed memo in chat. Never write to Linear or GitHub.

Read when

• Before researching, even when the ask looks like a single file: code-quality.md and code-structure.md, plus doctrine.md and the execution context.
• Before asking the user anything: Asking the user.

Contract

• Rediscover repository, ticket, PR, and diff facts from their live sources.
• Keep user decisions, rules, lanes, and promotion state visible in the execution context; never infer them from code.
• Return the analysis memo in chat. Do not create automatic runtime artifacts or hidden paths.
• Save a memo only when the user explicitly requests it and approves the destination.

Process