Copy-paste answers to everyday technical work

# ADR: [decision title] **Status:** [status] · **Date:** [date] · **Author:** [author] ## Context [context] ## Options considered [options considered] ## Decision [decision] ## Consequences [consequences (including accepted downsides)] ## Revisit when [revisit when]

Assemble a project kickoff brief for [project name] from the rough notes below. Structure it under these headings: Scope (what this project will deliver), Non-goals (what it explicitly will not cover, to prevent scope creep), Roles (who owns what, using only names or teams mentioned in the notes), Risks (anything the notes suggest could go wrong), and Milestones (in order, with dates only where one was actually given). If the notes don't mention a non-goal, an owner for some piece of scope, or any dates, leave that item as "not yet defined" rather than guessing one. Raw notes: [rough planning notes]

Review the project plan below for [project name] and identify risks. For each risk give: a one-sentence description, likelihood (low/medium/high), impact (low/medium/high), an early-warning sign someone could actually notice before the risk becomes a problem, and a specific mitigation (not "monitor closely"). Sort the list with the highest likelihood-times-impact risks first. Base every risk on something in the plan — a dependency, a deadline, a resource gap — and if you're inferring a risk that isn't directly supported by the plan, label it as speculative rather than presenting it as certain. Project plan: [project plan or summary]

# Bug: [bug title] **Environment:** [environment] · **Severity:** [severity] ## Steps to reproduce [steps to reproduce] ## Expected behavior [expected behavior] ## Actual behavior [actual behavior] ## Why this severity [why this severity] ## Evidence [evidence]