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

• Investigating a touched user flow, visible action, or UX complaint? Open user-experience.md and inspect the current entry point, context, continuation, and existing design before recommending controls. Backend-only work skips this.
• About to research, even when the ask looks like a single file? Open code-quality.md, code-structure.md, doctrine.md, and the execution context. Skip them and the memo recommends a fix the rules reject.
• About to search widely or read large files? Open main-context.md. Skip it and raw search output buries the analysis.
• About to ask the user anything? Open Asking the user. Skip it and you ask what the repo already answers.
• About to post the memo? Open Plain language. Skip it and the memo reads like pack jargon.

Contract

• Rediscover repository, ticket, PR, and diff facts from their live sources.
• Keep user decisions, rules, areas, and promotion state (whether the user approved turning this analysis into a build or ticket, see Apply) visible in the execution context, and take them from the user, not from code.
• Return the analysis memo in chat only, and keep state in the execution context.
• Save a memo only when the user explicitly requests it and approves the destination.