Compare assigned work from connected trackers with TASKS.md, review stale tasks, and fill gaps in stored context about people and projects. An optional comprehensive scan finds possible missed commitments in recent activity, with changes confirmed by the user.
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Review the instructions the agent will receive before you install.
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 MCP sources:
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 interactivelyNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review a design or web page against WCAG 2.1 AA, an accessibility standard. Organize findings on contrast, keyboard access, forms, and screen reader behavior, with severity levels and practical recommendations for fixes.
Build a single brief on an existing customer using available sales records, emails, documents, call notes, and internal chat. Understand the current situation, key contacts, recent discussions, and gaps that may need attention.
Build or refresh a strategic customer account plan from sales records, emails, and meeting transcripts. Organize goals, stakeholders, growth opportunities, risks, and dated actions into a document, then sync approved highlights to the customer relationship management system.
Research prospective companies and contacts, check existing customer records, and assess fit against your ideal customer profile. Receive a sourced brief covering recent developments, likely priorities, outreach talking points, and a suggested next step.
Research sales accounts using Common Room data to summarize company details, buying signals, ownership, and key contacts. Answer specific questions directly or prepare a broader briefing with evidence-based next steps, clearly identifying missing information.
Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.