onboard

Name: onboard
Author: kv0906

134stars33forks

How to install onboard?

kv0906/pm-kit/onboard

$npx -y skills add kv0906/pm-kit --skill onboard

Installs into the current project.

Summary

Interactive onboarding — sets up your first project, learns who you are, generates _core/identity.md profile, creates your first daily note, then loads vault context. For returning users, skips setup and loads context directly.

Files · 1

View on GitHub

SKILL.md

1	# /onboard — Interactive Onboarding & Context Loading
2
3	Set up your first project, run an interactive interview, generate a personalized `_core/identity.md`, create your first daily note, then load vault context. Returning users skip straight to context loading.
4
5	## Usage
6
7	```
8	/onboard # First time: project setup → interview → profile → daily → context. Returning: context only.
9	/onboard --reset # Re-run interview even if profile exists (skips project setup if already configured)
10	```
11
12	## Flow
13
14	```
15	/onboard
16	├── _core/identity.md populated + config has real projects + no --reset?
17	│ → Returning user → Load context → "Welcome back"
18	│
19	└── First time (no profile OR default projects OR --reset)?
20	│
21	├── Phase 1: Welcome message
22	├── Phase 2: Project Setup (if config still has default project-a)
23	│ ├── Read config.yaml
24	│ ├── Detect default project-a/project-b
25	│ ├── AskUserQuestion: project name
26	│ ├── Edit config.yaml (replace project-a, remove project-b)
27	│ ├── Create dirs: docs/{id}/, decisions/{id}/, blockers/{id}/
28	│ └── Create 01-index/{id}.md from template
29	│
30	├── Phase 3: Personal Interview (3 rounds, 7 questions)
31	│ └── Generate _core/identity.md
32	│
33	├── Phase 4: First Daily Note
34	│ └── Create daily/{today}.md with welcome content
35	│
36	├── Phase 5: Load Context
37	│
38	└── Phase 6: Handoff with "what to do next"
39	```
40
41	## Phase 1: Detect & Welcome
42
43	Check if `_core/identity.md` has been populated (not just the default template):
44
45	```
46	Read: _core/identity.md
47	```
48
49	Also read `_core/config.yaml` to check if projects are still defaults:
50
51	```
52	Read: _core/config.yaml
53	```
54
55	Detection logic:
56	- Returning user: `_core/identity.md` is populated (has a real role, not placeholder brackets) AND config does NOT contain `id: project-a` AND no `--reset` flag → Skip to Phase 5 (Load Context). Greet with:
57	> Welcome back! Loading your vault context...
58	- First time or --reset: Continue to Phase 2.
59
60	Display welcome message (for new users):
61
62	> Welcome to PM-Kit!
63	>
64	> I'm your AI-augmented knowledge partner for technical PM and engineering work. Let me get you set up — this takes about 3 minutes.
65	>
66	> We'll do three things:
67	> 1. Set up your first project
68	> 2. Learn how you work (7 quick questions)
69	> 3. Load your vault context
70	>
71	> Let's get started.
72
73	Create session tasks for progress tracking:
74
75	```
76	Task 1: "Set up first project" (activeForm: "Setting up first project...")
77	Task 2: "Complete onboarding interview" (activeForm: "Running onboarding interview...", blockedBy: Task 1)
78	Task 3: "Generate personal profile" (activeForm: "Generating personal profile...", blockedBy: Task 2)
79	Task 4: "Create first daily note" (activeForm: "Creating first daily note...", blockedBy: Task 3)
80	Task 5: "Load vault context" (activeForm: "Loading vault context...", blockedBy: Task 4)
81	```
82
83	## Phase 2: Project Setup
84
85	Mark Task 1 as in_progress.
86
87	Skip condition: If config.yaml does NOT contain `id: project-a`, projects are already configured. Mark Task 1 as completed and skip to Phase 3.
88
89	If config still has the default `project-a`, ask the user to name their project:
90
91	### AskUserQuestion
92
93	\| # \| Header \| Question \| Options \| multiSelect \|
94	\|---\|--------\|----------\|---------\|-------------\|
95	\| 1 \| Project \| "What's your main project called? (This becomes your folder name — lowercase, hyphens ok)" \| "my-product": "A product you're building" / "my-team": "Team-level tracking" / "my-company": "Company-wide knowledge" \| false \|
96
97	The user can pick a preset or type a custom name via "Other".
98
99	### After receiving the answer
100
101	1. Derive project ID: Use the answer directly as the ID (already lowercase with hyphens). If the user typed a display name with spaces/caps, slugify it (lowercase, replace spaces with hyphens, remove special characters).
102
103	2. Derive display name: Capitalize the ID (e.g., `my-product` → `My Product`, `acme-app` → `Acme App`).
104
105	3. Edit config.yaml: Use the `Edit` tool to:
106	- Replace `id: project-a` with `id: {project-id}`
107	- Replace `name: Project A` with `name: {Display Name}`
108	- Replace `description: Your first project` with `description: {Display Name} workspace`
109	- Remove the entire `project-b` block (the 4 lines: `- id: project-b`, `name: Project B`, `description: Your second project`, `active: true`)
110
111	4. Create project directories:
112	```
113	Write empty .gitkeep files to:
114	- docs/{project-id}/.gitkeep
115	- decisions/{project-id}/.gitkeep
116	- blockers/{project-id}/.gitkeep
117	```

People who liked this also viewed

6 picks

Type

onboard

134stars33forks

View on GitHub

How to install onboard?

kv0906/pm-kit/onboard

$npx -y skills add kv0906/pm-kit --skill onboard

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /onboard — Interactive Onboarding & Context Loading
2
3	Set up your first project, run an interactive interview, generate a personalized `_core/identity.md`, create your first daily note, then load vault context. Returning users skip straight to context loading.
4
5	## Usage
6
7	```
8	/onboard # First time: project setup → interview → profile → daily → context. Returning: context only.
9	/onboard --reset # Re-run interview even if profile exists (skips project setup if already configured)
10	```
11
12	## Flow
13
14	```
15	/onboard
16	├── _core/identity.md populated + config has real projects + no --reset?
17	│ → Returning user → Load context → "Welcome back"
18	│
19	└── First time (no profile OR default projects OR --reset)?
20	│
21	├── Phase 1: Welcome message
22	├── Phase 2: Project Setup (if config still has default project-a)
23	│ ├── Read config.yaml
24	│ ├── Detect default project-a/project-b
25	│ ├── AskUserQuestion: project name
26	│ ├── Edit config.yaml (replace project-a, remove project-b)
27	│ ├── Create dirs: docs/{id}/, decisions/{id}/, blockers/{id}/
28	│ └── Create 01-index/{id}.md from template
29	│
30	├── Phase 3: Personal Interview (3 rounds, 7 questions)
31	│ └── Generate _core/identity.md
32	│
33	├── Phase 4: First Daily Note
34	│ └── Create daily/{today}.md with welcome content
35	│
36	├── Phase 5: Load Context
37	│
38	└── Phase 6: Handoff with "what to do next"
39	```
40
41	## Phase 1: Detect & Welcome
42
43	Check if `_core/identity.md` has been populated (not just the default template):
44
45	```
46	Read: _core/identity.md
47	```
48
49	Also read `_core/config.yaml` to check if projects are still defaults:
50
51	```
52	Read: _core/config.yaml
53	```
54
55	Detection logic:
56	- Returning user: `_core/identity.md` is populated (has a real role, not placeholder brackets) AND config does NOT contain `id: project-a` AND no `--reset` flag → Skip to Phase 5 (Load Context). Greet with:
57	> Welcome back! Loading your vault context...
58	- First time or --reset: Continue to Phase 2.
59
60	Display welcome message (for new users):
61
62	> Welcome to PM-Kit!
63	>
64	> I'm your AI-augmented knowledge partner for technical PM and engineering work. Let me get you set up — this takes about 3 minutes.
65	>
66	> We'll do three things:
67	> 1. Set up your first project
68	> 2. Learn how you work (7 quick questions)
69	> 3. Load your vault context
70	>
71	> Let's get started.
72
73	Create session tasks for progress tracking:
74
75	```
76	Task 1: "Set up first project" (activeForm: "Setting up first project...")
77	Task 2: "Complete onboarding interview" (activeForm: "Running onboarding interview...", blockedBy: Task 1)
78	Task 3: "Generate personal profile" (activeForm: "Generating personal profile...", blockedBy: Task 2)
79	Task 4: "Create first daily note" (activeForm: "Creating first daily note...", blockedBy: Task 3)
80	Task 5: "Load vault context" (activeForm: "Loading vault context...", blockedBy: Task 4)
81	```
82
83	## Phase 2: Project Setup
84
85	Mark Task 1 as in_progress.
86
87	Skip condition: If config.yaml does NOT contain `id: project-a`, projects are already configured. Mark Task 1 as completed and skip to Phase 3.
88
89	If config still has the default `project-a`, ask the user to name their project:
90
91	### AskUserQuestion
92
93	\| # \| Header \| Question \| Options \| multiSelect \|
94	\|---\|--------\|----------\|---------\|-------------\|
95	\| 1 \| Project \| "What's your main project called? (This becomes your folder name — lowercase, hyphens ok)" \| "my-product": "A product you're building" / "my-team": "Team-level tracking" / "my-company": "Company-wide knowledge" \| false \|
96
97	The user can pick a preset or type a custom name via "Other".
98
99	### After receiving the answer
100
101	1. Derive project ID: Use the answer directly as the ID (already lowercase with hyphens). If the user typed a display name with spaces/caps, slugify it (lowercase, replace spaces with hyphens, remove special characters).
102
103	2. Derive display name: Capitalize the ID (e.g., `my-product` → `My Product`, `acme-app` → `Acme App`).
104
105	3. Edit config.yaml: Use the `Edit` tool to:
106	- Replace `id: project-a` with `id: {project-id}`
107	- Replace `name: Project A` with `name: {Display Name}`
108	- Replace `description: Your first project` with `description: {Display Name} workspace`
109	- Remove the entire `project-b` block (the 4 lines: `- id: project-b`, `name: Project B`, `description: Your second project`, `active: true`)
110
111	4. Create project directories:
112	```
113	Write empty .gitkeep files to:
114	- docs/{project-id}/.gitkeep
115	- decisions/{project-id}/.gitkeep
116	- blockers/{project-id}/.gitkeep
117	```

People who liked this also viewed

6 picks

Type