/update — Team State Sync
When this skill is triggered, perform ALL of the following steps:
Step 1: Review the conversation
Scan the current conversation for:
- Decisions made (technical, architectural, scope, business)
- New context learned (from documents, verbal context, or Q&A)
- Action items identified (including casual mentions like "we should also fix X", "don't forget to Y", "we'll need to Z eventually")
- User's knowledge growth (new concepts now understood)
- Open questions that still need answers
- Changes to project direction or priorities
- Completed work that may resolve existing action items
Step 2: Update memory files
For each relevant memory file in the memory directory:
- Read the current content
- Update with new information from this session
- If a new memory is needed (new topic not covered by existing files), create it
- Update MEMORY.md index if new files were created
Memory types to check:
user_[name]_profile.md — Did the user demonstrate new knowledge or preferences?
project_[name]_status.md — Did the project status, phase, or timeline change?
project_[stakeholder]_context.md — Did we learn anything new about a key stakeholder or their expectations?
project_technical_decisions_[phase].md — Were any technical decisions made or refined?
feedback_*.md — Did the user give any feedback on how the team should operate?
Step 3: Update ACTION-ITEMS.md
Read context/ACTION-ITEMS.md and perform ALL of the following:
3a: Capture new action items
Scan the conversation for anything that implies work to be done. This includes:
- Explicit requests ("we need to build X")
- Casual mentions ("we should also fix Y", "don't forget Z", "eventually we'll want W")
- Open questions that need follow-up ("need to check with [person] about X")
- Bugs discovered during the session
- Technical debt identified
- Follow-ups from code review or testing
For each new item, assign the next available ID from the next_id counter, increment the counter, and add it to the Open section using the standard format:
### [AI-NNN] Title
- **Status:** open
- **Priority:** critical | high | medium | low
- **Category:** feature | bug | debt | ops | research | docs
- **Source:** [Session date, inbox file name, verbal context, plan file, casual mention, etc.]
- **Created:** YYYY-MM-DD
- **Updated:** YYYY-MM-DD
- **Notes:** [Context about what this is and why it matters]
Priority guidelines:
- critical: Blocks other work or affects production
- high: Important for current phase, should be done soon
- medium: Should be done but not urgent
- low: Nice to have, do when convenient
3b: Update existing items
- Move items that were worked on this session to "In Progress" (or "Done" if completed)
- For completed items: set
Status: done, add Completed: YYYY-MM-DD, move to "Done (Recent)"
- Update the
Updated date on any item that was discussed or modified
- If an item is now blocked, move to "Blocked" and fill in
Blocked by
3c: Staleness check
- Flag any open items with
Updated date older than 30 days → move to "Stale Review Queue"
- Trim "Done (Recent)" — move items completed more than 3 sessions ago to "Archive"
- Prune Archive items older than 90 days (unless they have historical significance noted)
3d: Deduplication
- Check for duplicate or overlapping items. If found, merge them (keep the lower ID, note the merge)
Step 4: Update STATUS.md
Read context/STATUS.md and update:
- Last updated date
- Current Status section if phase or timeline changed
- App Build Status table if any development work was done
- Engineering Team Decisions section if new decisions were made
- What's Coming Next section if priorities shifted
- Add any new sections needed
Step 5: Process inbox (if applicable)
Check context/inbox/ for unprocessed files. If any exist:
- Read and analyze each file
- Brief on contents
- Move to appropriate folder (requirements/, communications/, archive/*, etc.)
- Update STATUS.md with new information
- Extract any action items and add to ACTION-ITEMS.md (per Step 3a)
Step 6: Log decisions
If significant decisions were made this session, create or update files in context/decisions/ with:
- The decision
- Why it was made
- Who was involved
- Date
- Impact on the build
Step 7: Confirm
After updating, provide a brief summary:
- What was saved/updated
- Action items: N new, N updated, N completed, N total open
- Any open items that need attention next session
- Current project state in one sentence
When to trigger automatically
This skill should also run automatically (without being asked) when:
- A significant decision point is reached
- New context from inbox has been processed
- A build phase or milestone is completed
- The session is clearly winding down
- User says anything like "save this", "remember this", "update yourselves", "don't forget"
1---2name: update-23description: Save all session decisions, conclusions, and context to memory and STATUS.md so the team stays current across instances. Use when you say /update, "save this", "update yourselves", or at the end of any significant session.4---56# /update — Team State Sync78When this skill is triggered, perform ALL of the following steps:910## Step 1: Review the conversation1112Scan the current conversation for:13- **Decisions made** (technical, architectural, scope, business)14- **New context learned** (from documents, verbal context, or Q&A)15- **Action items** identified (including casual mentions like "we should also fix X", "don't forget to Y", "we'll need to Z eventually")16- **User's knowledge growth** (new concepts now understood)17- **Open questions** that still need answers18- **Changes to project direction or priorities**19- **Completed work** that may resolve existing action items2021## Step 2: Update memory files2223For each relevant memory file in the memory directory:24- Read the current content25- Update with new information from this session26- If a new memory is needed (new topic not covered by existing files), create it27- Update MEMORY.md index if new files were created2829Memory types to check:30- `user_[name]_profile.md` — Did the user demonstrate new knowledge or preferences?31- `project_[name]_status.md` — Did the project status, phase, or timeline change?32- `project_[stakeholder]_context.md` — Did we learn anything new about a key stakeholder or their expectations?33- `project_technical_decisions_[phase].md` — Were any technical decisions made or refined?34- `feedback_*.md` — Did the user give any feedback on how the team should operate?3536## Step 3: Update ACTION-ITEMS.md3738Read `context/ACTION-ITEMS.md` and perform ALL of the following:3940### 3a: Capture new action items41Scan the conversation for anything that implies work to be done. This includes:42- Explicit requests ("we need to build X")43- Casual mentions ("we should also fix Y", "don't forget Z", "eventually we'll want W")44- Open questions that need follow-up ("need to check with [person] about X")45- Bugs discovered during the session46- Technical debt identified47- Follow-ups from code review or testing4849For each new item, assign the next available ID from the `next_id` counter, increment the counter, and add it to the **Open** section using the standard format:50```51### [AI-NNN] Title52- **Status:** open53- **Priority:** critical | high | medium | low54- **Category:** feature | bug | debt | ops | research | docs55- **Source:** [Session date, inbox file name, verbal context, plan file, casual mention, etc.]56- **Created:** YYYY-MM-DD57- **Updated:** YYYY-MM-DD58- **Notes:** [Context about what this is and why it matters]59```6061Priority guidelines:62- **critical:** Blocks other work or affects production63- **high:** Important for current phase, should be done soon64- **medium:** Should be done but not urgent65- **low:** Nice to have, do when convenient6667### 3b: Update existing items68- Move items that were **worked on this session** to "In Progress" (or "Done" if completed)69- For completed items: set `Status: done`, add `Completed: YYYY-MM-DD`, move to "Done (Recent)"70- Update the `Updated` date on any item that was discussed or modified71- If an item is now blocked, move to "Blocked" and fill in `Blocked by`7273### 3c: Staleness check74- Flag any open items with `Updated` date older than 30 days → move to "Stale Review Queue"75- Trim "Done (Recent)" — move items completed more than 3 sessions ago to "Archive"76- Prune Archive items older than 90 days (unless they have historical significance noted)7778### 3d: Deduplication79- Check for duplicate or overlapping items. If found, merge them (keep the lower ID, note the merge)8081## Step 4: Update STATUS.md8283Read `context/STATUS.md` and update:84- **Last updated** date85- **Current Status** section if phase or timeline changed86- **App Build Status** table if any development work was done87- **Engineering Team Decisions** section if new decisions were made88- **What's Coming Next** section if priorities shifted89- Add any new sections needed9091## Step 5: Process inbox (if applicable)9293Check `context/inbox/` for unprocessed files. If any exist:94- Read and analyze each file95- Brief on contents96- Move to appropriate folder (requirements/, communications/, archive/*, etc.)97- Update STATUS.md with new information98- Extract any action items and add to ACTION-ITEMS.md (per Step 3a)99100## Step 6: Log decisions101102If significant decisions were made this session, create or update files in `context/decisions/` with:103- The decision104- Why it was made105- Who was involved106- Date107- Impact on the build108109## Step 7: Confirm110111After updating, provide a brief summary:112- What was saved/updated113- **Action items:** N new, N updated, N completed, N total open114- Any open items that need attention next session115- Current project state in one sentence116117## When to trigger automatically118119This skill should also run automatically (without being asked) when:120- A significant decision point is reached121- New context from inbox has been processed122- A build phase or milestone is completed123- The session is clearly winding down124- User says anything like "save this", "remember this", "update yourselves", "don't forget"