productivity/skills/update/SKILL.md
Sync tasks and refresh memory from your current activity
npx skillsauth add grailautomation/claude-plugins updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Keep your task list and memory current. Two modes:
--comprehensive: Deep scan chat, email, calendar, docs — flag missed todos and suggest new memories/productivity:update
/productivity:update --comprehensive
Read TASKS.md and memory/ directory. If they don't exist, suggest /productivity:start first.
Check for available task sources:
gh issue list --assignee=@meIf no sources are available, skip to Step 3.
Fetch tasks assigned to the user (open/in-progress). Compare against TASKS.md:
| External task | TASKS.md match? | Action | |---------------|-----------------|--------| | Found, not in TASKS.md | No match | Offer to add | | Found, already in TASKS.md | Match by title (fuzzy) | Skip | | In TASKS.md, not in external | No match | Flag as potentially stale | | Completed externally | In Active section | Offer to mark done |
Present diff and let user decide what to add/complete.
Review Active tasks in TASKS.md and flag:
Present each for triage: Mark done? Reschedule? Move to Someday?
For each task, attempt to decode all entities (people, projects, acronyms, tools, links):
Task: "Send PSR to Todd re: Phoenix blockers"
Decode:
- PSR → ✓ Pipeline Status Report (in glossary)
- Todd → ✓ Todd Martinez (in people/)
- Phoenix → ? Not in memory
Track what's fully decoded vs. what has gaps.
Present unknown terms grouped:
I found terms in your tasks I don't have context for:
1. "Phoenix" (from: "Send PSR to Todd re: Phoenix blockers")
→ What's Phoenix?
2. "Maya" (from: "sync with Maya on API design")
→ Who is Maya?
Add answers to the appropriate memory files (people/, projects/, glossary.md).
Tasks often contain richer context than memory. Extract and update:
Update complete:
- Tasks: +3 from project tracker (e.g. Asana), 1 completed, 2 triaged
- Memory: 2 gaps filled, 1 project enriched
- All tasks decoded ✓
--comprehensive)Everything in Default Mode, plus a deep scan of recent activity.
Gather data from available connected sources. Prefer a maintained CLI over MCP
when the CLI can safely perform the workflow; for Google Workspace, use the
gws CLI:
gws gmail instead of Gmail
MCP.gws drive and gws docs instead of Google Drive MCP.gws calendar instead of Google Calendar MCP.Compare activity against TASKS.md. Surface action items that aren't tracked:
## Possible Missing Tasks
From your activity, these look like todos you haven't captured:
1. From chat (Jan 18):
"I'll send the updated mockups by Friday"
→ Add to TASKS.md?
2. From meeting "Phoenix Standup" (Jan 17):
You have a recurring meeting but no Phoenix tasks active
→ Anything needed here?
3. From email (Jan 16):
"I'll review the API spec this week"
→ Add to TASKS.md?
Let user pick which to add.
Surface new entities not in memory:
## New People (not in memory)
| Name | Frequency | Context |
|------|-----------|---------|
| Maya Rodriguez | 12 mentions | design, UI reviews |
| Alex K | 8 mentions | DMs about API |
## New Projects/Topics
| Name | Frequency | Context |
|------|-----------|---------|
| Starlight | 15 mentions | planning docs, product |
## Suggested Cleanup
- **Horizon project** — No mentions in 30 days. Mark completed?
Present grouped by confidence. High-confidence items offered to add directly; low-confidence items asked about.
--comprehensive always runs interactivelydevelopment
Parse and analyze Workato recipe JSON exports. Use when the user asks about a Workato recipe's logic, data flow, field mappings, error handling, or control flow. Also use when the user references a .recipe.json file or asks to debug a Workato integration.
databases
Review implementation plans as a staff software engineer. Use when the user asks for staff engineer feedback, senior engineering review, plan review, architecture review, implementation-plan critique, approval before proceeding, risk review, or feedback on a proposed technical plan.
tools
Use when the user invokes $spec-kit:tasks or /spec-kit:tasks, or asks to generate dependency-ordered tasks from the plan and repo context.
testing
Use when the user invokes $spec-kit:specify or /spec-kit:specify, or asks to create a brownfield-aware feature specification from a natural language description.