home / skills / onewave-ai / claude-skills / cross-conversation-project-manager

cross-conversation-project-manager skill

/cross-conversation-project-manager

This skill maintains project state across multiple conversations, tracks tasks, blockers, decisions, and reminders, and generates proactive status reports.

npx playbooks add skill onewave-ai/claude-skills --skill cross-conversation-project-manager

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.9 KB
---
name: cross-conversation-project-manager
description: Maintain project state across MULTIPLE conversations over days/weeks. Track tasks, decisions, blockers, resources. Auto-update when project mentioned. Generate status reports and proactive reminders.
---

# Cross Conversation Project Manager
Maintain project state across MULTIPLE conversations over days/weeks. Track tasks, decisions, blockers, resources. Auto-update when project mentioned. Generate status reports and proactive reminders.

## Instructions

You are a master project manager with persistent memory. Create and maintain project files in /mnt/user-data/outputs/projects/. Track: project name, start date, conversations involved, tasks (completed/in-progress/pending), decisions made, blockers, resources, links to relevant conversations, and last updated timestamp. Auto-update when user mentions the project name. Generate status reports showing all work across multiple conversations. Proactively remind user of commitments and follow-ups. Maintain state across weeks/months.

### Output Format

```markdown
# Cross Conversation Project Manager Output

**Generated**: {timestamp}

---

## Results

[Your formatted output here]

---

## Recommendations

[Actionable next steps]

```

### Best Practices

1. **Be Specific**: Focus on concrete, actionable outputs
2. **Use Templates**: Provide copy-paste ready formats
3. **Include Examples**: Show real-world usage
4. **Add Context**: Explain why recommendations matter
5. **Stay Current**: Use latest best practices for meta

### Common Use Cases

**Trigger Phrases**:
- "Help me with [use case]"
- "Generate [output type]"
- "Create [deliverable]"

**Example Request**:
> "[Sample user request here]"

**Response Approach**:
1. Understand user's context and goals
2. Generate comprehensive output
3. Provide actionable recommendations
4. Include examples and templates
5. Suggest next steps

Remember: Focus on delivering value quickly and clearly!

Overview

This skill maintains project state across multiple conversations over days and weeks. It tracks tasks, decisions, blockers, resources, and links to related conversations, then generates status reports and proactive reminders. The goal is to keep a single, up-to-date project record so work continues smoothly between chats.

How this skill works

The skill listens for mentions of a project name and automatically updates the project record with new tasks, status changes, decisions, blockers, and resource links. It stores a canonical project file and timestamps changes, aggregates content from all related conversations, and can produce snapshot status reports and actionable next-step reminders. Scheduled or trigger-based reminders are issued for upcoming commitments and unresolved blockers.

When to use it

  • Coordinating multi-week or multi-party projects across many chat sessions
  • Keeping a running log of decisions and action items from recurring meetings
  • Tracking blockers and resource requests that span days or weeks
  • Producing consolidated status reports for stakeholders
  • Setting follow-up reminders for deadlines and commitments

Best practices

  • Always name projects consistently so automatic updates attach to the correct record
  • Summarize decisions and tasks in a single sentence when updating to reduce ambiguity
  • Include links or identifiers for conversations and artifacts to preserve traceability
  • Mark task states clearly: pending, in-progress, completed, blocked
  • Schedule periodic reviews to confirm the record reflects reality

Example use cases

  • Product launch spanning design, engineering, and marketing with updates across many chats
  • Client onboarding where requirements, meetings, and deliverables are recorded over weeks
  • Internal process change tracked through recurring check-ins and action item follow-ups
  • Remote team coordination with distributed decisions and resource requests
  • Research project that accumulates links, notes, and decisions across interviews and analyses

FAQ

How does the skill decide which conversation belongs to a project?

It matches explicit project names or identifiers you provide. Consistent naming and including a short project tag in messages improves accuracy.

Can it remind team members about their tasks?

Yes. It generates proactive reminders and suggested follow-ups. You can request individual or team-level reminders and set timing or recurrence.