Project Hub - Project Types

The six built-in Project Hub project types with fields, phases, contact roles, templates and knowledge documents, plus how to create custom types.

Project Hub - Project Types

Deutsche Version

← Back to overview

A project type determines which fields and phases a project typically has, which template get-template outputs and which knowledge documents flow in when the project is loaded. The type is a free name on the project. The plugin ships six types, and you can add your own.

Built-in types

Type	Use	Phases according to the type description
`merchant-onboarding`	Integrating a merchant into payment products (BNPL, direct debit, multiple markets)	Discovery, Contract, Tech Integration, UAT, Go-Live, Hypercare
`it-project`	IT and software projects	Discovery, Design, Development, Testing, Deployment, Support
`consulting`	Consulting engagements	Scoping, Analysis, Design, Delivery, Closed
`marketing`	Campaigns and brand initiatives	Briefing, Concept, Production, Review, Launch, Reporting
`event`	Events and conferences	Planning, Preparation, Promotion, Execution, Follow-up
`generic`	General projects	free text

The phases are a guideline. A project's phase field accepts any text, and the server does not enforce a phase sequence.

Project fields

Every project has the fields name, type, status, description, market, products, phase, go-live, budget and notes. Which of them a type uses is defined by its template:

Type	Template fields
`merchant-onboarding`	name, description, market, products, phase, go_live, budget, notes
`it-project`, `consulting`, `generic`	name, description, phase, go_live, budget, notes
`marketing`, `event`	name, description, market, phase, go_live, budget, notes

Status is a free-text field. The skills work with active, paused, completed and cancelled. The dashboard lists projects with any other status under "Sonstige" (other).

Templates

/project-hub:get-template <type> outputs the template as Markdown with a YAML header. You fill it in outside the chat and import it with /project-hub:new-project, either pasted or as a .md file. All values must be plain text, lists are not allowed, and name is required.

Knowledge documents

The plugin ships templates for knowledge documents. /project-hub:setup or /project-hub:knowledge sync copies them to ~/.project-hub/knowledge/<type>/.

Type	Documents
`merchant-onboarding`	`governance`, `process`, `roles`, `vacation-handover`
`it-project`	`architecture`, `charter`, `runbook`
`consulting`	`engagement`, `governance`, `roles`
`marketing`	`campaign-brief`, `stakeholders`
`event`	`logistics`, `runsheet`, `stakeholders`
`generic`	`charter`

resume and session-start load all documents of the type automatically, except for generic.
You add your own documents as .md files in the type folder. The first top-level heading in the file is its title.
The vacation-handover document is the basis of the vacation-handover skill.

Custom types

/project-hub:type-creator creates a type under ~/.project-hub/project-types/<name>/ (name as slug) with a README.md containing phases and contact roles and an empty knowledge/ folder. The type then appears in new-project, get-template and help.

A custom type with the name of a built-in type overrides it.
Built-in types cannot be deleted, custom types can (via /project-hub:configure, manage project types).
A template.md in the type folder is preferred by get-template. Without it, the generic template applies.
The knowledge documents of a custom type still live under ~/.project-hub/knowledge/<type>/, not in the type folder.
For unknown types, the tone in compose falls back to the rules for it-project, marketing and generic.