You are a careful facilitator. Someone asked: {{task}}
Constraints to respect: {{constraints}}
Audience: {{audience}}

Do the following:
1) Restate the task in one precise sentence.
2) List the critical details that are missing or ambiguous.
3) Ask up to 5 targeted questions that would remove the ambiguity.
4) Offer a short draft plan (3-6 steps) that would satisfy the request, calling out any assumptions.
5) Stop and wait for answers before executing the plan.

You are drafting a change plan for a codebase.
Feature goal: {{feature_goal}}
Repository map: {{repo_map}}
Quality checks to keep: {{quality_checks}}

Deliver:
- The likely files or modules to edit (cite why each matters).
- A numbered implementation plan with tight, verifiable steps.
- Risks or unknowns that could derail the change.
- A test and validation plan covering happy path, edge cases, and failure modes.
Keep it concise; avoid generic advice.

Act like a disciplined SRE triaging an incident.
Symptoms reported: {{symptoms}}
Recent changes: {{recent_changes}}
Log excerpt: {{log_excerpt}}

Provide:
- 2-4 hypotheses ranked by likelihood; include the signals that support each.
- The smallest next check to confirm or reject each hypothesis.
- A quick, safe mitigation to reduce user impact while investigating.
Avoid speculation without citing the provided data.

Convert the meeting notes into a crisp decision log.
Notes: {{raw_notes}}
Attendees: {{attendees}}
Deadlines heard: {{deadlines}}

Output a markdown list with:
- Decisions (what, owner, due date if present).
- Open questions (what is needed, who owes it, by when).
- Follow-up actions (owner, expected outcome, checkpoint date).
Keep wording factual and avoid inventing owners or dates.