¶ Project Hub - Project Management Plugin
This documentation always describes the latest published version. For older versions, see the CHANGELOG.
¶ Table of Contents
- Overview
- What Project Hub Does Differently
- Main Features
- Project Links
- 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 — contacts, meeting logs, decisions, and communication drafts, all in the context of the active project.
What Project Hub is:
- A persistent "memory" per client project: stakeholders, phases, history
- Structured storage for meetings, emails, decisions, deliverables
- A drafting tool for communication (email, Slack, Teams) in project context
- A 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 Project Hub Does Differently
| Feature | Manual Notes | Project Hub |
|---|---|---|
| Contact overview | Scattered across emails, notes | Central contact registry per project |
| Meeting minutes | Word files, everywhere | Structured notes with type and date |
| Decisions | Somewhere in the chat history | Documented with date and context |
| Communication | Manually written | Context-aware drafting via /compose |
| Search | Full-text search across all files | /search across all notes and contacts |
| Handoffs | Re-briefing required | /resume loads the full project context instantly |
| Related projects | No linking, kept in your head | Projects can be linked, visible in dashboard and report |
¶ Main Features
¶ Typical Flow
¶ Persistent Project Context
Every 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)
¶ Shared Contacts
Internal contacts can be marked as shared — they then become automatically available in every project, without duplicates:
- Add your own colleagues once, visible across all projects
/resumeloads shared contacts under "Shared Contacts" automatically- External contacts always stay project-specific (cannot be shared)
- When adding an internal contact,
/add-contactasks whether the person should be shared across projects - Duplicate protection: if a shared contact with the same name or email already exists, any further entry with that data is blocked — regardless of whether it's itself meant to be shared
¶ Notes and Logs
Typed notes:
- Meeting — minutes with date, attendees, 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
¶ File Attachments
Notes and projects can attach files (tool_attach_file). For PDFs, Word, and Excel documents, an .md sibling file is generated automatically on attach (via MarkItDown conversion) — Claude can then read the content directly, without parsing the original format. Images are skipped (no real text recognition).
Conversion is best-effort: if it fails, or a file with that
.mdname already exists, the original attachment is still kept.
¶ Communication Drafting
/project-hub:compose creates drafts for:
- Email (formal or informal, matching the contact's profile)
- Slack messages
- Teams messages
The draft automatically uses project context, known contact names, and the current phase.
¶ Knowledge System
Each project type has a knowledge repository (~/.project-hub/knowledge/{type}/):
- Governance documents, process descriptions, role overviews
- Loaded automatically on
/resume - User-editable and extensible
¶ HTML Reports
/project-hub:report generates full HTML reports:
- Full project report (full)
- Summary (summary)
- All projects (all-projects)
Linked projects (see Project Links) are automatically shown in both the dashboard and reports.
¶ Vacation Handover
/project-hub:vacation-handover generates a complete handover document for all open projects of the active project type — based on a knowledge template (~/.project-hub/knowledge/{type}/vacation-handover.md). A built-in template already ships for merchant-onboarding.
- Automatically pulls project status, open ToDos, upcoming meetings, risks, and contacts from notes and contact data
- Without a configured template, the skill stops and shows how to create one (
/knowledge update vacation-handover) - On request: export as a copy-ready Confluence block, or save as a note in the active project
If no template exists for the active project type, the skill generates no document — templates must be created first via
/project-hub:knowledge.
¶ Project Links
Two projects can be linked together — for example to represent a follow-up engagement or a multi-market rollout, without keeping the history in your head.
| Relation | Meaning |
|---|---|
successor |
Project A is the successor of Project B (e.g. "Joybuy 2" after "Joybuy") |
predecessor |
The reverse of successor |
related |
Symmetric link with no direction (e.g. two markets of the same rollout) |
Behavior:
- A project pair can only have one active link at a time — unlink first to change it
- Linked projects appear automatically in the dashboard and in HTML reports
- Links are preserved on export/import
Links are currently set only via the MCP tools
tool_link_project/tool_unlink_project— there is no dedicated skill for this yet.
¶ Project Types
Project Hub ships 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 projects |
Create custom types via /project-hub:type-creator — define knowledge documents, status levels, and role patterns.
Detailed documentation: Project Types
¶ Skills Overview
Project Hub has 20 skills, invoked via /project-hub:<skill-name>:
| Skill | Purpose |
|---|---|
new-project |
Create a new project |
get-template |
Get a fillable project template to prepare outside the chat |
resume |
Load / switch 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 |
Summarize an email or meeting transcript |
compose |
Draft an email, Slack, or Teams message |
knowledge |
View and manage the knowledge repository |
session-start |
Initialize a session, check setup |
next-step |
Recommend the next sensible step |
configure |
Edit plugin settings |
setup |
First-time setup |
type-creator |
Create a custom project type |
report |
Generate an HTML report |
vacation-handover |
Generate a vacation handover document for all open projects |
help |
Show all available skills |
In addition to these 20 user-facing skills, there are internal, machine-invoked test skills for automated rollout testing — not part of this reference.
Detailed documentation: Skills in Detail
¶ 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 a project with all metadatatool_create_project(...)— create a new projecttool_update_project(project_id, ...)— update project data
¶ Project Links
tool_link_project(identifier, related_identifier, relation_type)— link two projects (successor/predecessor/related)tool_unlink_project(identifier, related_identifier)— remove a link, regardless of direction or type
¶ Contacts
tool_list_contacts(project_id)— all contacts of a projecttool_list_shared_contacts()— all shared contacts (cross-project)tool_add_contact(project_id, ..., is_shared?)— add a contact (is_shared=truefor shared ones)tool_update_contact(contact_id, ..., is_shared?)— edit a contact (sharing changeable later)tool_delete_contact(contact_id)— delete a contacttool_search_contacts(query, project_id?)— search contacts (including shared)
¶ Notes
tool_list_notes(project_id, ...)— list notestool_get_note(note_id)— load a single notetool_add_note(project_id, ...)— log 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 of 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 the active sessiontool_set_session(project_id?, ...)— set the sessiontool_clear_session()— clear the session
¶ Attachments
tool_list_attachments(project_id)— list a project's file attachmentstool_attach_file(project_id, file_path)— attach a file (auto-generates a readable.mdsibling for supported formats)tool_list_docs(project_id)— list documents in a project's docs folder
¶ System Requirements
| Component | Version |
|---|---|
| Claude Code | Latest |
| Python | 3.11+ |
| Operating System | Windows, macOS, Linux |
No API key needed — Project Hub uses Claude Code's built-in Claude access.
Project Hub runs natively on Windows — no WSL required.
/project-hub:setupresolves the Python interpreter automatically viapy -3, including on devices where thepython/python3alias is blocked by the Microsoft Store.
# 1. Add the marketplace
claude plugin marketplace add markus-michalski/project-hub
# 2. Install the plugin
claude plugin install project-hub@project-hub
# 3. First-time setup
/project-hub:setup
Marketplace installation is the preferred path: future updates run via
claude plugin update project-hub, no manualgit pullneeded.
# 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. First-time setup
/project-hub:setup
¶ Configuration
Configuration file: ~/.project-hub/config.yaml
name: My Name # Your name (for communication drafts)
language: en # Default language (de / en)
Interactive configuration via /project-hub:configure.
¶ Quick Start
1. /project-hub:setup # First-time setup
2. /project-hub:new-project # Create a new project
3. /project-hub:add-contact # Add a stakeholder
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
│ │ └── vacation-handover.md
│ ├── it-project/
│ │ ├── architecture.md
│ │ ├── charter.md
│ │ └── runbook.md
│ └── {custom-type}/
│ └── ...
└── projects/
└── {project-slug}/
└── docs/
├── emails/
├── meeting-notes/
└── misc/
On Windows, the same directory lives under %USERPROFILE%\.project-hub\.
¶ Knowledge System
The knowledge system stores project-type-specific knowledge that becomes automatically available when a project is loaded.
Built-in knowledge documents:
| Project Type | Documents |
|---|---|
merchant-onboarding |
governance.md, process.md, roles.md, vacation-handover.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 drop Markdown files under ~/.project-hub/knowledge/{type}/. They're loaded automatically on the next /resume.
Managing knowledge: /project-hub:knowledge shows all available documents and allows direct editing in context.
¶ Session Pattern
On /resume, Project Hub loads in 8 steps:
tool_get_session()— check the active session- If no project is active:
tool_list_projects("active")— user picks a project tool_get_project(identifier)— load full project datatool_list_contacts(project_id)— load project-specific contactstool_list_shared_contacts()— load shared contacts (cross-project)tool_get_all_knowledge(project_type)— load domain knowledgetool_list_notes(project_id)— load notes and activities- Display project summary
If a project is specified directly (/project-hub:resume Acme), step 2 is skipped.
¶ Further Documentation
- Skills in Detail — All 20 skills with purpose and use case
- Project Types — 6 built-in types + creating your own
- Workflow Example — End-to-end: merchant onboarding
¶ Troubleshooting
¶ Issue: Plugin not found / skills not available
ls ~/.claude/plugins/project-hub/skills/
The plugin directory must be registered in ~/.claude/settings.json under enabledPlugins.
¶ Issue: venv missing / Python dependencies not installed
/project-hub:setup
¶ Issue: Database not found
ls ~/.project-hub/
If the directory is missing: run /project-hub:setup once.
¶ Issue: Knowledge documents not loading
Knowledge files must live under ~/.project-hub/knowledge/{project-type}/. Check with /project-hub:knowledge.
¶ Issue: Setup fails on Windows with exit code 49
On some Windows devices, the python/python3 alias is blocked by the Microsoft Store. /project-hub:setup detects this automatically and falls back to py -3. If that also fails: install Python 3.11+ directly from python.org.
¶ 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