Given a weekly note (a weekly/YYYY-WNN.md file or free-form weekly summary), produce exactly five labeled bullets in the format specified below. Output only the five bullets — no intro, no extra text, no explanation.
Focus Check
- One sentence: did the work this week align with the declared week priorities?
- Reference specific tasks or themes from the note. If no priorities are stated, infer from the work described.
- If more than half the work was unplanned or off-priority, append
[DRIFT] at the end.
Cross-team Quality
- One sentence: were there cross-team interactions, and did they produce a durable artifact or outcome?
- Name the other team(s) if mentioned in the note.
- Append exactly one tag inline:
[cross-team signal] if a high-impact interaction is evident; [no cross-team signal] if the week was primarily squad-internal.
Priority Shift
- One sentence: what, if anything, should change next week — stop, start, or continue — based on the week's evidence?
- Ground the shift in a specific signal from the note (e.g., a blocked dependency, a recurring theme, a missed outcome).
- If no shift is warranted, write: "Continue current trajectory — no adjustment needed."
Priority Judgment
- One sentence: given the planned items for this week, flag anything that appears out of scope or low-impact relative to the declared priorities.
- If an item from the Planned or Done section appears disconnected from stated priorities, name it explicitly.
- If Impact Items are listed in the note, assess whether any warrant moving to next week's Planned list.
- If all planned work appears on-scope, write: "All planned work aligns with stated priorities — no scope flag." Append
[no scope flag].
- Otherwise append
[scope flag: <item name>].
Mentorship Signal
- One sentence: did any mentorship or coaching activity occur this week — planned or incidental?
- Name the person(s) mentored if mentioned, and describe what was addressed (e.g., agenda-setting, scope clarification, technical approach, career growth).
- Append exactly one tag inline:
[mentorship signal] if a concrete interaction is evident; [no mentorship signal] if none is mentioned.
- If a durable artifact resulted (note, doc, changed approach), name it.
Output format (use this exact structure, no extra lines):
Focus Check: [DRIFT if applicable]
Cross-team Quality: [cross-team signal | no cross-team signal]
Priority Shift:
Priority Judgment: [scope flag: | no scope flag]
Mentorship Signal: [mentorship signal | no mentorship signal]
1---2name: weekly-review3description: Synthesize a weekly note into five structured bullets — Focus Check, Cross-team Quality, Priority Shift, Priority Judgment, and Mentorship Signal — for weekly self-reflection and 1:1 preparation.4---56Given a weekly note (a `weekly/YYYY-WNN.md` file or free-form weekly summary), produce exactly five labeled bullets in the format specified below. Output only the five bullets — no intro, no extra text, no explanation.78**Focus Check**9- One sentence: did the work this week align with the declared week priorities?10- Reference specific tasks or themes from the note. If no priorities are stated, infer from the work described.11- If more than half the work was unplanned or off-priority, append `[DRIFT]` at the end.1213**Cross-team Quality**14- One sentence: were there cross-team interactions, and did they produce a durable artifact or outcome?15- Name the other team(s) if mentioned in the note.16- Append exactly one tag inline: `[cross-team signal]` if a high-impact interaction is evident; `[no cross-team signal]` if the week was primarily squad-internal.1718**Priority Shift**19- One sentence: what, if anything, should change next week — stop, start, or continue — based on the week's evidence?20- Ground the shift in a specific signal from the note (e.g., a blocked dependency, a recurring theme, a missed outcome).21- If no shift is warranted, write: "Continue current trajectory — no adjustment needed."2223**Priority Judgment**24- One sentence: given the planned items for this week, flag anything that appears out of scope or low-impact relative to the declared priorities.25- If an item from the Planned or Done section appears disconnected from stated priorities, name it explicitly.26- If Impact Items are listed in the note, assess whether any warrant moving to next week's Planned list.27- If all planned work appears on-scope, write: "All planned work aligns with stated priorities — no scope flag." Append `[no scope flag]`.28- Otherwise append `[scope flag: <item name>]`.2930**Mentorship Signal**31- One sentence: did any mentorship or coaching activity occur this week — planned or incidental?32- Name the person(s) mentored if mentioned, and describe what was addressed (e.g., agenda-setting, scope clarification, technical approach, career growth).33- Append exactly one tag inline: `[mentorship signal]` if a concrete interaction is evident; `[no mentorship signal]` if none is mentioned.34- If a durable artifact resulted (note, doc, changed approach), name it.3536Output format (use this exact structure, no extra lines):3738**Focus Check:** <sentence> [DRIFT if applicable]39**Cross-team Quality:** <sentence> [cross-team signal | no cross-team signal]40**Priority Shift:** <sentence>41**Priority Judgment:** <sentence> [scope flag: <item name> | no scope flag]42**Mentorship Signal:** <sentence> [mentorship signal | no mentorship signal]