Project types define the context of a project: What knowledge is automatically loaded? What roles are typical? What knowledge documents are available?
Project Hub comes with 6 built-in project types. Custom types can be created via /project-hub:type-creator.
For: Enterprise merchant onboarding (BNPL, Direct Debit, Alternative Payments, multi-market rollouts)
Typical phases:
Built-in knowledge documents:
| Document | Content |
|---|---|
governance.md |
Decision framework, escalation paths, RACI matrix |
process.md |
Onboarding phases and milestones |
roles.md |
Typical roles: Technical Lead, Account Manager, Compliance Officer, ... |
Typical contacts:
When to choose this type:
For: IT and software projects, infrastructure initiatives, technical rollouts
Typical phases:
Built-in knowledge documents:
| Document | Content |
|---|---|
architecture.md |
System design patterns, architecture decisions |
charter.md |
Project charter template (scope, goals, deliverables, timeline) |
runbook.md |
Operational procedures, monitoring, incident handling |
Typical contacts:
For: Consulting mandates, analysis projects, strategy projects
Typical phases:
Built-in knowledge documents:
| Document | Content |
|---|---|
engagement.md |
Engagement phases and typical deliverables |
governance.md |
Decision rights, steering committee structure |
roles.md |
Consultant roles, client roles, and responsibilities |
Typical contacts:
For: Marketing campaigns, product launches, promotional activities
Typical phases:
Built-in knowledge documents:
| Document | Content |
|---|---|
campaign-brief.md |
Campaign briefing template (goal, target audience, budget, KPIs) |
stakeholders.md |
Typical roles: Brand Manager, Creative Lead, Media Planner, Legal |
Typical contacts:
For: Event planning and coordination (conferences, webinars, internal events)
Typical phases:
Built-in knowledge documents:
| Document | Content |
|---|---|
logistics.md |
Supply chain, vendor management, checklists |
runsheet.md |
Day-of timeline and run-of-show |
stakeholders.md |
Key contacts: organizers, venue, catering, speakers |
Typical contacts:
For: General projects that don't fit into any other type
Built-in knowledge document:
| Document | Content |
|---|---|
charter.md |
Basic project charter (scope, goals, stakeholders) |
This type works as a starting point when no specialized type fits. Custom knowledge documents can be added at any time.
Use /project-hub:type-creator to create custom project types:
/project-hub:type-creator
The skill asks interactively for:
bnpl-expansion)Output:
~/.project-hub/knowledge/{type}/ created with starter content/project-hub:new-projectExample:
Type name: bnpl-expansion
Display: BNPL Country Expansion
Knowledge: expansion-playbook.md, country-requirements.md, stakeholders.md
Roles: Country Manager (internal), Legal Counsel (internal), Local Partner (external)
All knowledge documents are simple Markdown files:
~/.project-hub/knowledge/{type}/{document}.md
Edit directly:
nano ~/.project-hub/knowledge/merchant-onboarding/governance.md
Edit via the plugin:
/project-hub:knowledge
→ Shows available documents, allows selection and editing in context
Add custom documents:
Simply place a new .md file in the type's knowledge directory — it is automatically loaded on the next /resume.
Tip: The more domain-specific knowledge is captured in knowledge documents (governance rules, typical bottlenecks, role responsibilities), the better Claude can communicate in context, summarize, and provide recommendations.