¶ Project Hub - Project Management Plugin
¶ Table of Contents
- Overview
- What Makes Project Hub Different
- Key Features
- Project Types
- Skills Overview
- MCP Tools Overview
- System Requirements
- Installation
- Configuration
- Quick Start
- Data Storage
- Knowledge System
- Session Pattern
- Further Documentation
- Troubleshooting
- License
¶ Overview
Project Hub is a Claude Code plugin for structured project management directly in Claude. It replaces scattered notes, email threads, and spreadsheets with a central, searchable project registry — with contacts, meeting minutes, decisions, and communication drafts, all in the context of the active project.
What Project Hub is:
- Persistent "memory" per client project: stakeholders, phases, history
- Structured storage for meetings, emails, decisions, deliverables
- Drafting tool for communication (email, Slack, Teams) in project context
- Summary generator for meetings and emails
What Project Hub is not:
- Not a code repo manager (use mm-dev-toolkit for that)
- Not a book writing assistant (use StoryForge for that)
- Not a video production tool (use VidCraft for that)
¶ What Makes Project Hub Different
| Feature | Manual Notes | Project Hub |
|---|---|---|
| Contact overview | Scattered in emails, notes | Central contact registry per project |
| Meeting minutes | Word files, everywhere | Structured notes with type and date |
| Decisions | Somewhere in chat history | Documented with date and context |
| Communication | Written manually | Context-aware drafts with /compose |
| Search | Full-text search over files | /search across all notes and contacts |
| Handoffs | Requires re-briefing | /resume instantly loads full project context |
¶ Key Features
¶ Persistent Project Context
Each project is loaded once (/project-hub:resume) and Claude then knows:
- All stakeholders (internal and external) with roles
- Current phase and status
- Recent activities and decisions
- Project type-specific knowledge (governance, processes, roles)
¶ Contact Management
Internal and external contacts with:
- Role in the project (Sponsor, Technical Lead, Account Manager, ...)
- Company / team
- Communication history
- Tags (optional)
¶ Notes and Minutes
Typed notes:
- Meeting — Minutes with date, participants, action items
- Email — Incoming or outgoing emails in context
- Decision — Documented decisions with rationale
- Action Item — Open tasks with deadline and owner
- General — Free-text notes
¶ Communication Drafting
/project-hub:compose creates drafts for:
- Email (formal or informal, matching the contact context)
- Slack messages
- Teams messages
The draft automatically uses project context, known contact names, and current phase.
¶ Knowledge System
Per project type, there is a knowledge repository (~/.project-hub/knowledge/{type}/):
- Governance documents, process descriptions, role overviews
- Automatically loaded when
/resumeis called - User-customizable and extensible
¶ HTML Reports
/project-hub:report generates complete HTML reports:
- Full project report (full)
- Summary (summary)
- All projects overview (all-projects)
¶ Project Types
Project Hub comes with 6 built-in project types:
| Type | Use case |
|---|---|
merchant-onboarding |
Enterprise merchant onboarding (BNPL, Direct Debit, multi-market) |
it-project |
IT / software projects |
consulting |
Consulting engagements |
marketing |
Marketing campaigns |
event |
Event planning and coordination |
generic |
General purpose projects |
Custom types via /project-hub:type-creator — defines knowledge documents, status stages, and role patterns.
Details: Project Types
¶ Skills Overview
Project Hub has 18 skills, called via /project-hub:<skill-name>:
| Skill | Purpose |
|---|---|
new-project |
Create a new project |
resume |
Load / switch to a project |
dashboard |
Overview of all projects |
status |
Show and update project status |
add-contact |
Add a contact |
add-note |
Log a note, minutes, email, or decision |
edit-note |
Edit an existing note |
search |
Full-text search across all content |
summarize |
Create summary from email or meeting transcript |
compose |
Draft an email, Slack, or Teams message |
knowledge |
View and manage the knowledge repository |
session-start |
Initialize session, check setup |
next-step |
Recommend the next logical action |
configure |
Edit plugin settings |
setup |
Initial setup |
type-creator |
Create a custom project type |
report |
Generate HTML report |
help |
Show all skills |
Details: Skills Reference
¶ MCP Tools Overview
The Project Hub MCP server (project-hub-mcp) provides the following tools:
¶ Projects
tool_list_projects(status?)— all projects (filtered by status)tool_get_project(identifier)— load project with all metadatatool_create_project(...)— create a new projecttool_update_project(project_id, ...)— update project data
¶ Contacts
tool_list_contacts(project_id)— all contacts for a projecttool_add_contact(project_id, ...)— add a contacttool_update_contact(contact_id, ...)— edit a contacttool_delete_contact(contact_id)— delete a contacttool_search_contacts(project_id, query)— search contacts
¶ Notes
tool_list_notes(project_id, ...)— list notestool_get_note(note_id)— load a single notetool_add_note(project_id, ...)— add a new notetool_update_note(note_id, ...)— edit a notetool_delete_note(note_id)— delete a notetool_search_notes(project_id, query)— search notes
¶ Knowledge
tool_get_all_knowledge(project_type)— load all knowledge documents for a typetool_get_knowledge(project_type, doc_name)— load a single knowledge documenttool_save_knowledge(project_type, doc_name, content)— save a knowledge documenttool_delete_knowledge(project_type, doc_name)— delete a knowledge documenttool_list_knowledge(project_type)— list available knowledge documents
¶ Session
tool_get_session()— load active sessiontool_set_session(project_id?, ...)— set sessiontool_clear_session()— reset session
¶ Attachments
tool_list_attachments(project_id)— list file attachments for a projecttool_attach_file(project_id, file_path)— attach a file
¶ System Requirements
| Component | Version |
|---|---|
| Claude Code | Latest |
| Python | 3.11+ |
No API key needed — Project Hub uses Claude Code's built-in Claude access.
¶ Installation
# 1. Clone the plugin
git clone https://github.com/markus-michalski/project-hub \
~/.claude/plugins/project-hub
Add to ~/.claude/settings.json:
{
"enabledPlugins": {
"project-hub@project-hub": true
}
}
# 2. Initial setup
/project-hub:setup
¶ Configuration
Configuration file: ~/.project-hub/config.yaml
name: Your Name # Your name (for communication drafts)
language: en # Default language (de / en)
Interactive configuration via /project-hub:configure.
¶ Quick Start
1. /project-hub:setup # Initial setup
2. /project-hub:new-project # Create a new project
3. /project-hub:add-contact # Add stakeholders
4. /project-hub:add-note # Log the first meeting
5. /project-hub:next-step # What's next?
6. /project-hub:compose email # Draft an email
Second session:
/project-hub:resume [Project Name] # Pick up right where you left off
¶ Data Storage
~/.project-hub/
├── config.yaml # Plugin configuration
├── project-hub.db # SQLite database (projects, contacts, notes)
├── knowledge/
│ ├── merchant-onboarding/
│ │ ├── governance.md
│ │ ├── process.md
│ │ └── roles.md
│ ├── it-project/
│ │ ├── architecture.md
│ │ ├── charter.md
│ │ └── runbook.md
│ └── {custom-type}/
│ └── ...
└── projects/
└── {project-slug}/
└── docs/
├── emails/
├── meeting-notes/
└── misc/
¶ Knowledge System
The knowledge system stores project type-specific knowledge that is automatically available when a project is loaded.
Built-in knowledge documents:
| Project Type | Documents |
|---|---|
merchant-onboarding |
governance.md, process.md, roles.md |
it-project |
architecture.md, charter.md, runbook.md |
consulting |
engagement.md, governance.md, roles.md |
event |
logistics.md, runsheet.md, stakeholders.md |
marketing |
campaign-brief.md, stakeholders.md |
generic |
charter.md |
Custom documents: Simply place Markdown files under ~/.project-hub/knowledge/{type}/. They are automatically loaded on the next /resume.
Managing knowledge: /project-hub:knowledge shows all available documents and allows direct editing in context.
¶ Session Pattern
When /resume is called, Project Hub loads in 6 steps:
tool_get_session()— Check active session- If no project active:
tool_list_projects("active")— user selects project tool_get_project(identifier)— Load full project datatool_get_all_knowledge(project_type)— Load domain knowledgetool_list_notes(project_id, limit=5)— Recent activities- Display project summary
With a direct name (/project-hub:resume Acme), step 2 is skipped.
¶ Further Documentation
- Skills Reference — All 18 skills with purpose and use case
- Project Types — 6 built-in types + create your own
- Workflow Example — End-to-end: Merchant Onboarding
¶ Troubleshooting
¶ Problem: Plugin not found / skills not available
ls ~/.claude/plugins/project-hub/skills/
The plugin directory must be listed under enabledPlugins in ~/.claude/settings.json.
¶ Problem: venv missing / Python dependencies not installed
/project-hub:setup
¶ Problem: Database not found
ls ~/.project-hub/
If the directory is missing, run /project-hub:setup once.
¶ Problem: Knowledge documents not loading
Knowledge files must be located under ~/.project-hub/knowledge/{project-type}/. Check with /project-hub:knowledge.
¶ License
Project Hub is licensed under the PolyForm Noncommercial License 1.0.0. Personal, non-commercial use is free. Commercial use requires a separate license.
CLA for contributors: Contributor Agreement