PromptWorks/flow-1on1/SKILL.md

---
name: "flow-1on1"
description: "Prep Daniel's biweekly 1:1 with his manager Ahmed Atya (ES365 FLOW team). Reviews activity since the last 1:1, co-authors Ahmed's four-question notebook-tracker template one section at a time, writes the dated entry into the Daniel-Ahmed.docx tracker, then builds a private talking-points and issues brief. Triggers: /flow-1on1, prep my Ahmed 1:1, 1:1 with Ahmed, notebook tracker, manager 1:1 prep, flow 1:1."
---

## FLOW 1:1 Prep (Daniel ↔ Ahmed Atya)

Prepares Daniel for his recurring 1:1 with **Ahmed Atya** (`ahmedatya@microsoft.com`, Member of
Technical Staff, ES365 US OPEX), his manager since the 2026-08-04 "agentic era" reorg placed
Daniel on the **FLOW** team (Fast, Lean Operations and Workflows). FLOW owns **Code Movement**
and **Operational Excellence**, two of Charles's top FY priorities.

Two outputs, and the distinction between them is the whole point of this skill:

1. **The tracker entry** — a dated entry written into the shared Word tracker. **Ahmed reads
   this.** Treat it as outbound.
2. **The private brief** — talking points, open issues, asks, and landmines. **Only Daniel sees
   this.** It never goes into the tracker.

> Relationship to other skills: `rise-15-5` is the weekly team-wide status post; this is the
> per-1:1 manager tracker. `oneonone-pokedex` is the private post-meeting self-reflection. This
> skill runs *before* the meeting and owns the tracker document.

### Cadence and context

- **Biweekly**, per Ahmed's 2026-08-26 "Flow Team: Updates and Meeting Rhythm" mail: *"These
  will initially be held biweekly for the next 90 days, and we'll adjust the cadence case by
  case."* Re-check the calendar each run rather than assuming; the cadence is explicitly
  provisional.
- Ahmed's expectation: *"Please spend about 10 minutes updating it before each meeting; if you
  aren't able to, we'll use the first 5–10 minutes of the meeting to do so together."* The
  tracker's purpose in his words: *"My goal is to help each of you capture your contributions
  and ensure I can represent your work and impact in the best possible way."* Write for that
  purpose — this is Connect/promo evidence, not a task log.
- Ahmed has an explicit **open-door policy** (Teams or email, any time). If something is urgent
  it does not have to wait for the 1:1; say so when it comes up.
- First 1:1 was **2026-08-12** (intro). First working 1:1 with the tracker: **2026-09-01**.

### Artifacts

| What | Where |
|---|---|
| Tracker (shared with Ahmed) | `D:\OneDrive - Microsoft\Documents\1to1\Daniel-Ahmed.docx` |
| Ahmed's rhythm mail | `D:\OneDrive - Microsoft\Documents\1to1\Flow Team_ Updates and Meeting Rhythm.msg` |
| Prior 1:1 notes | `D:\Repos\Obsidian\03 - Squads\C4 - SRE Core\Meetings\` |
| Daily squad status | `D:\Repos\Obsidian\03 - Squads\C4 - SRE Core\Status Updates\` |
| Write entry | `Add-TrackerEntry.ps1` (this skill folder) |
| Read entries | `Read-Tracker.ps1` (this skill folder) |

**The tracker is MIP-labeled.** Word re-applies the label on every save, which wraps the .docx
in an encrypted OLE container. After the first write it is **no longer readable by unzipping** —
always read it with `Read-Tracker.ps1`, never by extracting `word/document.xml`.

### The template (Ahmed's, do not restyle it)

Four questions, in this order, as list-level-1 italic headings with level-2 bullets underneath:

1. **What are my Achievements, Impact and Key Results?**
2. **What's next? / What am I working on?**
3. **Lessons Learned/Things to Improve**
4. **Topics to discuss/What I need help with**

Each entry is preceded by a bare `MM/DD/YYYY` date line. `Add-TrackerEntry.ps1` clones the
Example block's formatting, so never hand-type the structure into Word.

---

## Workflow

### 1. Establish the window

- Run `Read-Tracker.ps1 -Last 2` to see the previous entries and get the "since when" boundary.
  If it reports no entries, this is the first working 1:1 — use the last 1:1 date from the vault
  (`Meetings\*Ahmed*`), or fall back to 14 days.
- Confirm the meeting date/time from the calendar (`workiq_list_events`) and note any conflicts
  — the 1:1 has historically overlapped RISE Up.
- State the window in one line and get a nod before digging in.

### 2. Gather raw material

Pull from every source that is actually available. Do not skip one because it is slow.

- **Vault (primary):** `03 - Squads\C4 - SRE Core\` — `Status Updates\` for the window,
  `04 - Decisions.md`, `05 - Open Questions.md`, `Meetings\`. The daily status notes are the
  densest source; read every one in the window.
- **Prior 1:1s (required — the user asked for this explicitly):** the last Ahmed 1:1 note *and*
  the last Shaun 1:1 note. Commitments Daniel made in either are the first thing to check for
  closure. Example: on 2026-08-27 Daniel committed to Shaun that he would raise career direction
  with Ahmed.
- **ADO** (`azure_devops-*`): PRs authored/reviewed, work items moved. Note that generic searches
  miss repos you do not already know about; if the pass comes up thin, ask Daniel directly.
- **IcM** (`icm-*`): incidents Daniel was DRI/mitigator on. `assignedTo` searches miss incidents
  he mitigated but did not own — cross-check any IDs he names.
- **Calendar / Teams / mail** (`workiq_*`): meetings that produced decisions, threads where he
  posted something substantive.
- **Ask Daniel** for anything invisible to tooling: hallway conversations, verbal agreements,
  how he actually feels about the work.

### 3. Co-author, one section at a time

**Do not draft all four sections and dump them for approval.** For each section in order:

- Silently draft 2–5 candidate bullets from the gathered material.
- Show Daniel only that section.
- Ask what to keep, cut, edit, or add. Genuinely co-author; do not rubber-stamp your own draft.
- Move on only once he confirms.

Section-specific guidance:

- **Achievements / Impact / Key Results** — outcomes, not activity. What shipped, what got
  fixed, what moved closer to done, what changed for a customer or a service. This is the
  section Ahmed will quote in calibration; make it defensible.
- **What's next** — in-flight initiatives and the next concrete step for each. Honest about
  status; "prototype undeployed, first target service unresolved" beats "in progress."
- **Lessons Learned / Things to Improve** — real ones. This section is where a manager learns
  whether someone is self-aware. A hollow lesson is worse than none. If Daniel has nothing
  genuine, say so rather than manufacturing humility.
- **Topics to discuss / What I need help with** — the asks Daniel is willing to put in writing.
  Anything sensitive that he would rather raise verbally goes in the **private brief instead**,
  not here. Ask him which side of that line each item falls on when it is not obvious.

### 4. Write the entry

Build a UTF-8 JSON file (use `D:\Repos\Scratchpad\` for it) shaped like:

```json
{
  "achievements": ["...", "..."],
  "next":         ["..."],
  "lessons":      ["..."],
  "topics":       ["..."]
}
```

Preview, then write:

```powershell
$s = "C:\Users\dkucinski\.scout\m-skills\flow-1on1"
$doc = "D:\OneDrive - Microsoft\Documents\1to1\Daniel-Ahmed.docx"

# dry run
powershell -NoProfile -ExecutionPolicy Bypass -File "$s\Add-TrackerEntry.ps1" `
  -DocPath $doc -JsonPath "D:\Repos\Scratchpad\1on1-entry.json" -Preview

# write (newest entry goes to the top, under the Example block)
powershell -NoProfile -ExecutionPolicy Bypass -File "$s\Add-TrackerEntry.ps1" `
  -DocPath $doc -JsonPath "D:\Repos\Scratchpad\1on1-entry.json"
```

`-Position Bottom` appends chronologically instead; `-EntryDate MM/DD/yyyy` overrides today.

**Before running the write:** show Daniel the complete entry verbatim and get an explicit
go-ahead. This document is read by his manager. Never write on an assumed yes.

**After running:** re-read with `Read-Tracker.ps1 -Last 1` and confirm the entry landed with the
right formatting. Close Word if the script opened it. If Daniel has the tracker open in Word,
the script edits the live document — tell him to review and let OneDrive sync.

### 5. Build the private brief

Not written to the tracker. Render it in chat (and to the vault note in step 6):

- **Open commitments** — Daniel's and Ahmed's, from prior 1:1s and status notes, with age. Flag
  anything stale.
- **Talking points** — ranked, with the one-line "why now" for each. Lead with whatever is
  genuinely most consequential, not whatever is easiest.
- **Issues / risks to surface** — blockers, things rotting quietly, decisions with no owner.
- **Asks** — what Daniel wants Ahmed to actually *do*: a decision, air cover, a headcount, an
  introduction, a priority call.
- **Career thread** — the standing item. Keep it on every agenda until it is resolved; status
  will crowd it out otherwise.
- **Questions for Ahmed** — 2–4 sharp ones. Org context, priorities, feedback.
- **Landmines** — anything unsettled between Ahmed and Shaun (e.g. the RISE-artifact kill list
  vs. Ahmed's "Ops and RISE standups will remain") that Daniel should raise carefully rather
  than walk into.

### 6. Save a vault note

Write to `D:\Repos\Obsidian\03 - Squads\C4 - SRE Core\Meetings\YYYY-MM-DD - Daniel - Ahmed 1-1 (prep).md`
with frontmatter `type: meeting`, `attendees: [Ahmed Atya, Daniel Kucinski]`, tags
`meeting`, `squad/c4-sre-core`, and wikilinks to the sources used. This is what the *next* run
reads for "our most recent 1:1s," and it makes the content first-class `connect` evidence.

After the meeting, `oneonone-pokedex` handles the reflection; do not duplicate it here.

---

## Voice & formatting

Standing corrections from real editing passes with Daniel. Apply them in the **first** draft,
not after he flags them again.

- **No receipts unless asked.** No IcM numbers, PR numbers, work-item IDs, or ticket links in
  bullets. Describe the substance: "resolved a CloudBuild false-positive security alert," not
  "resolved IcM 835355363." Ahmed's template shows `[Feature Link]` placeholders — offer links
  only if Daniel wants them.
- **No em dashes.** Use a colon or semicolon.
- **Real output first, housekeeping second.** Lead with delivered work. Do not pad with "updated
  a wiki page" or "captured a transcript." But do not overcorrect: a squad's first planning
  kickoff or a mission-defining decision is genuine content. Substance vs. busywork is the line,
  not "code only." When unsure, ask.
- **One idea per bullet, plain language.** No jargon stacking.
- **Write in first person**, matching Ahmed's example ("I delivered project XYZ").

If Daniel gives a correction during a run that generalizes, fold it into this section via
`m_update_skill` afterward so it applies from the first draft next time.

## Guardrails

- Never write to the tracker without the explicit final-review confirmation in step 4.
- Never put private career deliberation, peer comparisons, or anything about other people's
  performance into the tracker. Those are verbal, or they go in the private brief only.
- The tracker is MIP-labeled. Do not copy its content into unlabeled destinations outside the
  vault, and never read it by unzipping.
- If source-gathering surfaces something sensitive (HR matters, another person's private
  situation), leave it out of the drafts entirely rather than asking whether to include it.
- Never invent an accomplishment, a lesson, or a commitment. If a section has nothing real in
  it, write "None." and tell Daniel why it came up empty.
- If Word COM fails or the file is locked by OneDrive sync, stop and report it. Do not retry
  blindly or fall back to rewriting the .docx by hand — that would strip the sensitivity label.