Stop explaining
from scratch
Organize project records, capture a successful conversation as a skill, refine it on fresh input, and coordinate a workflow.
Project records (Lecture 2.2)
01 / 04Three scopes keep background organized: Company → Department (Delivery Operations) → Project (Northstar Onboarding). Explicit retrieval and update confirm what the agent is reading.
Three records in Northstar Onboarding
- 1. Project instructions. Check delivery dependencies before drafting client updates; keep confirmed plans separate from items awaiting confirmation. (Reusable follow-up methods stay in skills.)
- 2. Current facts (Updated Oct 5). Jordan confirmed 18 of 22 client staff roles for Tuesday’s setup; the remaining 4 specialist roles wait until Thursday’s working session. Team: Priya leads delivery; Sam coordinates onboarding.
- 3. Decision record (Oct 5). Start Tuesday’s setup for the 18 confirmed staff members and hold the 4 specialist accounts until Thursday so onboarding proceeds without guessing security permissions.
Explicit retrieval & update check
- Retrieval confirmation. Agent reports reading
current-facts.mdanddecision-record-2026-10-05.mdbefore starting the next task. - Before update. “Jordan intends to send the role list by 3 p.m. Friday, subject to operations-manager confirmation.”
- After update. “18 of 22 client roles confirmed for Tuesday Oct 6 setup; 4 specialist roles held until Thursday Oct 8 pending operations-manager sign-off.”
Skill capture (Lecture 2.3)
02 / 04Paste the complete capture request into your successful conversation so the agent generates an adaptable prompt with zero blank placeholders, then test in Work and capture with @skill-creator.
Fresh-input refinement (Lecture 2.4)
03 / 04Testing @meeting-follow-up on Wednesday’s technical check-in exposes one recurring preference: naming a single confirmation owner when colleagues share a dependency.
When an action or preparation dependency involves more than one colleague, state who is assisting and name the single owner responsible for sending confirmation back to the leader.
Thursday’s security check and working session run at 2 p.m. on October 8; Sam will attach session links by 1 p.m. and confirm completion back to Alex by 1:30 p.m.
Adaptation & orchestration (Lectures 2.5–2.6)
04 / 04In 2.5, Maya corrects an unfamiliar RFP evaluation plan before execution. In 2.6, Meetings and follow-through coordinates focused skills with explicit handoffs.
Maya’s pre-execution correction on Meridian Manufacturing (2.5)
Flawed initial plan: Treated total engineering headcount (6 engineers) as interchangeable with senior integration specialist availability.
Corrected plan before execution: Check the 6-week migration timeline specifically against senior integration specialist availability in weeks 3 and 4, and include a phased-start option moving custom integration to week 5.
| Skill in sequence | Input received | Output passed forward / branch rule |
|---|---|---|
| 1. business-context | Northstar Onboarding project folder | Project instructions, current facts (18/22 roles), and Oct 5 decision record, so the agent knows who Priya, Sam and Jordan are |
| 2. meeting-summary | Permitted meeting transcript + project context | Promised actions, deadlines, and open items |
| 3. leader-interview | Context + summary + leader’s stated goal | Confirmed review purpose (pauses to ask Alex if purpose is missing) |
| 4. meeting-follow-up (+ personal-voice) | Transcript notes + project context + confirmed purpose | Recipient drafts with clear action, reason, and single confirmation owner |
| 5. leadership-artifact (+ calendar-reminder-actions) | Notes + drafts + reminder proposal | Navigable follow-through page (reminder stays Proposed only if calendar approval is absent) |