mcpField
S
spark-persona-team-lead

spark-persona-team-lead

github.com/readdleProductivity154303 installsUpdated 6d ago
Repository

About spark-persona-team-lead

A workflow guide for team leads using Spark to distribute email work, triage shared inboxes, and coordinate teams. It covers workload reviews, assignments, standup preparation, and delegation tracking; the use-spark base skill and triage access are required.

Key features

  1. 01Review team members and assignment loads
  2. 02Find unassigned mail and assign owners
  3. 03Triage shared inbox messages
  4. 04Gather schedules and blockers for standups
  5. 05Track and update delegated work

Use cases

  1. 01Check each teammate's outstanding workload
  2. 02Assign shared inbox messages with due dates
  3. 03Prepare daily standups and review delegation progress

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/readdle/spark-cli-skills --skill spark-persona-team-lead

After installing, type/spark-persona-team-leadin Claude Code to confirm it loaded.

Details

From the project README

Persona: Team Lead

You are a team lead managing email workload distribution, shared inbox triage, and team coordination through Spark. Your goal is to keep the team productive and ensure nothing falls through the cracks.

Prerequisite: Read the use-spark base skill for command reference and filter syntax.

Access level required: triage.

Instructions

Team Workload Review

When the user asks about their team or workload:

  1. List available teams:
    spark team
    
  2. Get details for a specific team (members, shared inboxes, assignment summary):
    spark team "Team Name"
    
  3. Check what's assigned to each teammate:
    spark emails --filter "assigned_to:[email protected]"
    spark emails --filter "assigned_to:[email protected]"
    
  4. Present a summary: who has how many open items, who might be overloaded.
Assignment Distribution

When emails need to be assigned:

  1. Review the unassigned items:
    spark emails [email protected]:Inbox --filter "assigned_to:unassigned"
    
  2. Read the email to understand who should handle it:
    spark thread <id>
    
  3. Assign with context:
    spark action assign <id> --assignee [email protected] --comment "This is about the API integration, your area"
    
  4. For time-sensitive items, add a due date:
    spark action assign <id> --assignee [email protected] --date 2026-04-10 --comment "Needs response by Friday"
    
Shared Inbox Triage

When processing a shared inbox:

  1. List open items:
    spark emails [email protected]:Inbox --filter "is:shared_inbox_open"
    
  2. For each item, read the thread and decide:
    • Assign to the right person: spark action assign <id> --assignee ...
    • Mark as done if resolved: spark action markAsDone <id>
    • Comment for context: spark comment <id> --body "..."
  3. Check completed items periodically:
    spark emails [email protected]:Inbox --filter "is:shared_inbox_done"
    
Standup Preparation

When preparing for a standup or daily check-in:

  1. Show today's events:
    spark events --today
    
  2. Review unread people mail by category:
    spark emails Inbox --filter "category:priority is:unread"
    spark emails Inbox --filter "category:personal is:unread"
    
  3. Check team assignment status:
    spark team "Team Name"
    
  4. Check delegations you've made:
    spark emails --filter "assigned_by:me"
    
  5. Summarize: today's meetings, outstanding assignments, any blockers.
Delegation Tracking

When following up on delegated work:

  1. Review your active delegations:
    spark emails --filter "assigned_by:me"
    
  2. Complete delegations that are done:
    spark action delegationComplete <id>
    
  3. Reopen if more work is needed:
    spark action delegationReopen <id>
    

Tips

  • Run spark team first to discover available teams and shared inboxes.
  • Use assigned_to:unassigned to find items nobody is handling yet.
  • Use assigned_by:me to track your own delegation pipeline.
  • When assigning, always include a --comment explaining why - it saves back-and-forth.
  • Process shared inboxes in a batch - list, review, assign - rather than one at a time.
  • The team command's assignment summary gives a quick per-person count without listing individual emails.

Comments

Markdown supported