@pareto4/pp-core 1.7.0 → 1.8.0

package/pareto-skills/pp-obsidian-notes/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: pp-obsidian-notes
+description: >
+  Create and manage Obsidian vault structure, client context files, meeting notes, and
+  proposals for The Pareto Project. Use this skill whenever the user wants to set up
+  the Pareto Obsidian vault from scratch, create a new client folder and context file,
+  add a meeting note for a client, create or update a proposal, or scaffold any part
+  of the Pareto knowledge structure. Triggers on requests like "set up the vault",
+  "create a client folder for X", "add a meeting note for X", "new meeting with X",
+  "create a proposal for X", "set up obsidian", "new client X", "log a call with X",
+  or any mention of creating or updating Pareto client knowledge files. Always use
+  this skill — do not improvise the structure from scratch.
+---
+
+# Pareto Obsidian Notes Skill
+
+Creates and manages the Pareto Obsidian knowledge vault structure: initial scaffold,
+client context files, meeting notes, proposals, and internal Pareto context. Operates
+directly on the filesystem via Claude Code's file tools.
+
+---
+
+## Vault location
+
+Default vault root: `~/pareto-vault`
+
+If the user has specified a different path, use that instead. Always confirm or infer
+the vault path before writing files.
+
+---
+
+## Workflow by task type
+
+### 1. Initial vault scaffold
+Triggered by: "set up the vault", "create the obsidian structure", "initialise vault"
+
+1. Create the full directory structure (see **Vault structure** below)
+2. Write `CLAUDE.md` at the vault root using `templates/CLAUDE.md`
+3. Write `internal/_pareto-context.md` using `templates/pareto-context.md`
+4. Write `clients/README.md` with one-line instructions
+5. Print all created paths and confirm to the user
+
+### 2. New client
+Triggered by: "new client X", "create a client folder for X", "onboard client X"
+
+1. Confirm the client name — convert to lowercase-hyphenated slug (e.g. `acme-corp`)
+2. Ask for or infer: full client name, industry, primary contact name, engagement type
+3. Create `clients/{slug}/` directory
+4. Write `clients/{slug}/_context.md` using `templates/client-context.md`
+5. Print the created path and remind the user to fill in any `[PLACEHOLDER]` fields
+
+### 3. New meeting note
+Triggered by: "log a meeting with X", "add meeting notes for X", "new call with X", "meeting with X"
+
+1. Confirm client slug and meeting date (default: today in YYYY-MM-DD)
+2. Ask for or infer: attendees, meeting type (kickoff / check-in / review / discovery / demo)
+3. Write `clients/{slug}/YYYY-MM-DD-{type}.md` using `templates/meeting-note.md`
+4. Print the created file path
+
+### 4. New proposal
+Triggered by: "create a proposal for X", "draft a proposal for X", "new proposal X"
+
+1. Confirm client slug and version (default: v1)
+2. Check if a previous version exists — if so, bump to v2, v3, etc.
+3. Write `proposals/{slug}-proposal-v{N}-{YYYY-MM-DD}.md` using `templates/proposal.md`
+4. Print the created file path
+
+### 5. Update existing note
+Triggered by: "update the context for X", "edit the meeting note from DATE", "add to X"
+
+1. Read the existing file first
+2. Make the requested changes
+3. Confirm what changed and print the file path
+
+---
+
+## Vault structure
+
+```
+{vault-root}/
+├── CLAUDE.md
+├── internal/
+│   └── _pareto-context.md
+├── clients/
+│   └── {client-slug}/
+│       ├── _context.md
+│       └── YYYY-MM-DD-{type}.md
+├── proposals/
+│   └── {slug}-proposal-v{N}-{date}.md
+└── projects/
+    └── {project-slug}/
+        ├── _brief.md
+        └── _decisions.md
+```
+
+---
+
+## File naming conventions
+
+- Client slugs: lowercase, hyphen-separated (`acme-corp`, `ing-bank`)
+- Meeting notes: `YYYY-MM-DD-{type}.md` — type is `kickoff`, `check-in`, `review`, `discovery`, `demo`
+- Proposals: `{client-slug}-proposal-v{N}-{YYYY-MM-DD}.md`
+- Files prefixed `_` are source-of-truth — never auto-delete or overwrite without confirmation
+
+---
+
+## Templates
+
+Read the relevant template before writing any file:
+
+| Task | Template |
+|---|---|
+| Vault root map | `templates/CLAUDE.md` |
+| Pareto internal context | `templates/pareto-context.md` |
+| Client context | `templates/client-context.md` |
+| Meeting note | `templates/meeting-note.md` |
+| Proposal | `templates/proposal.md` |
+
+---
+
+## Conventions
+
+- Use `[PLACEHOLDER]` for fields the user must fill in manually
+- Never overwrite `_context.md` without reading it first and confirming
+- Meeting notes are append-only — never edit past notes, always create new
+- Proposals are versioned — if v1 exists, create v2
+- Always print full file paths after creation so the user can verify in Obsidian

package/pareto-skills/pp-obsidian-notes/templates/CLAUDE.md

@@ -0,0 +1,29 @@
+# Pareto knowledge vault
+
+This is the Pareto Project Obsidian knowledge vault. All client context,
+meeting notes, proposals, and internal Pareto knowledge lives here.
+
+## Structure
+
+- `internal/_pareto-context.md` — Pareto's identity, positioning, principles, tone
+- `clients/{slug}/_context.md` — stable client profile (source of truth)
+- `clients/{slug}/YYYY-MM-DD-{type}.md` — meeting notes, chronological
+- `proposals/{slug}-proposal-v{N}-{date}.md` — versioned proposals
+- `projects/{slug}/_brief.md` — project brief
+- `projects/{slug}/_decisions.md` — key decisions log
+
+## Conventions
+
+- Files prefixed with `_` are source-of-truth documents
+- Meeting note types: kickoff, check-in, review, discovery, demo
+- Client slugs are lowercase-hyphenated (e.g. acme-corp)
+- Always read `_context.md` before working on any client task
+- For proposals, read the most recent meeting notes first
+
+## How to use this vault in Claude Code
+
+When working on a client task:
+1. Read `internal/_pareto-context.md` for Pareto's positioning and tone
+2. Read `clients/{slug}/_context.md` for the client profile
+3. Read the last 2–3 meeting notes for recent context
+4. Then proceed with the task

package/pareto-skills/pp-obsidian-notes/templates/client-context.md

@@ -0,0 +1,116 @@
+---
+type: client-context
+client: [PLACEHOLDER: Full Client Name]
+slug: [PLACEHOLDER: client-slug]
+industry: [PLACEHOLDER]
+status: active
+contract-start: [PLACEHOLDER: YYYY-MM-DD]
+contract-end: [PLACEHOLDER: YYYY-MM-DD or ongoing]
+last-updated: [PLACEHOLDER: YYYY-MM-DD]
+---
+
+# [PLACEHOLDER: Full Client Name] — client context
+
+This is the source-of-truth profile for this client.
+Read this before any client work. Update when material things change.
+
+---
+
+## Who they are
+
+**[PLACEHOLDER: Full Client Name]** is [PLACEHOLDER: one sentence describing the company —
+what they do, their size, their market position].
+
+- **Industry:** [PLACEHOLDER]
+- **HQ:** [PLACEHOLDER: city, country]
+- **Size:** [PLACEHOLDER: headcount or revenue range]
+- **Website:** [PLACEHOLDER: URL]
+
+---
+
+## Key contacts
+
+| Name | Role | Email | Notes |
+|---|---|---|---|
+| [PLACEHOLDER] | [PLACEHOLDER: e.g. CEO] | [PLACEHOLDER] | Primary contact |
+| [PLACEHOLDER] | [PLACEHOLDER] | [PLACEHOLDER] | |
+
+---
+
+## Why they hired Pareto
+
+[PLACEHOLDER: 2–3 sentences on the problem or opportunity that brought them to us.
+What were they trying to achieve? What was the trigger?]
+
+---
+
+## Engagement summary
+
+- **Type:** [PLACEHOLDER: retainer / project / advisory]
+- **Scope:** [PLACEHOLDER: brief description of what we're doing]
+- **Start:** [PLACEHOLDER: YYYY-MM-DD]
+- **Status:** [PLACEHOLDER: active / on hold / complete]
+- **Linear project:** [PLACEHOLDER: link or project name]
+- **Google Drive folder:** [PLACEHOLDER: link]
+
+---
+
+## Goals and success metrics
+
+What does success look like for this client?
+
+1. [PLACEHOLDER]
+2. [PLACEHOLDER]
+3. [PLACEHOLDER]
+
+---
+
+## Their context and constraints
+
+[PLACEHOLDER: anything material about their situation — tech stack, org structure,
+internal politics, budget constraints, timelines, regulatory context, past initiatives
+that succeeded or failed. This is the nuance that makes advice actually useful.]
+
+---
+
+## Their AI maturity
+
+[PLACEHOLDER: where are they on the AI adoption curve?
+e.g. "just starting, no AI tools in production yet" or "have GitHub Copilot, exploring agents"]
+
+---
+
+## Communication preferences
+
+- **Preferred channel:** [PLACEHOLDER: email / Slack / WhatsApp]
+- **Meeting cadence:** [PLACEHOLDER: e.g. weekly 45-min check-in, Thursdays]
+- **Style:** [PLACEHOLDER: e.g. prefers short written updates over long decks]
+- **Decision-maker:** [PLACEHOLDER: who ultimately approves things]
+
+---
+
+## Key decisions made
+
+| Date | Decision | Context |
+|---|---|---|
+| [PLACEHOLDER] | [PLACEHOLDER] | [PLACEHOLDER] |
+
+---
+
+## Open questions
+
+- [PLACEHOLDER]
+
+---
+
+## Risks and watch-outs
+
+- [PLACEHOLDER: e.g. budget approval pending for phase 2]
+- [PLACEHOLDER: e.g. key sponsor leaving in Q3]
+
+---
+
+## Related files
+
+- `[[proposals/{slug}-proposal-v1-{date}]]`
+- Meeting notes: see other files in this folder

package/pareto-skills/pp-obsidian-notes/templates/meeting-note.md

@@ -0,0 +1,66 @@
+---
+type: meeting-note
+client: [PLACEHOLDER: Full Client Name]
+date: [PLACEHOLDER: YYYY-MM-DD]
+meeting-type: [PLACEHOLDER: kickoff / check-in / review / discovery / demo]
+attendees-pareto: [PLACEHOLDER: Pareto team members present]
+attendees-client: [PLACEHOLDER: Client contacts present]
+---
+
+# [PLACEHOLDER: Full Client Name] — [PLACEHOLDER: meeting type] — [PLACEHOLDER: YYYY-MM-DD]
+
+---
+
+## Context recap
+
+[PLACEHOLDER: 2–3 sentences on where things stood going into this meeting.
+"Previously on..." — what were we working on, what was the outstanding question?
+This is the most important field for future AI context. Write it as if briefing
+someone who hasn't spoken to this client in 3 weeks.]
+
+---
+
+## Discussed
+
+[PLACEHOLDER: bullet points of the main topics covered, in order.
+Not exhaustive notes — the key substance of what was talked about.]
+
+- 
+- 
+- 
+
+---
+
+## Decisions made
+
+[PLACEHOLDER: things that were agreed, confirmed, or resolved.
+Be specific — vague decisions create future confusion.]
+
+- 
+- 
+
+---
+
+## Actions
+
+| Owner | Action | Due |
+|---|---|---|
+| [PLACEHOLDER] | [PLACEHOLDER] | [PLACEHOLDER: YYYY-MM-DD or "next call"] |
+| [PLACEHOLDER] | [PLACEHOLDER] | [PLACEHOLDER] |
+
+---
+
+## Open questions
+
+[PLACEHOLDER: things that came up but weren't resolved.
+These should either be answered before the next meeting or explicitly carried forward.]
+
+- 
+- 
+
+---
+
+## Next meeting
+
+- **Date:** [PLACEHOLDER: YYYY-MM-DD or TBC]
+- **Agenda:** [PLACEHOLDER: what needs to be covered next time]

package/pareto-skills/pp-obsidian-notes/templates/pareto-context.md

@@ -0,0 +1,102 @@
+---
+type: internal
+last-updated: [PLACEHOLDER: YYYY-MM-DD]
+---
+
+# Pareto — internal context
+
+This file is the standing context for all Claude-assisted work at Pareto.
+Paste this at the top of any Claude conversation involving client work.
+
+---
+
+## Who we are
+
+**Pareto** is [PLACEHOLDER: one sentence description of what Pareto does].
+
+Founded: [PLACEHOLDER: year], based in the Netherlands (Dutch BV).
+
+---
+
+## What we do
+
+[PLACEHOLDER: 2–3 sentences describing Pareto's core service or product.
+What problem do you solve? For whom? How?]
+
+---
+
+## Who we work with
+
+**Ideal client profile:**
+- [PLACEHOLDER: industry or sector]
+- [PLACEHOLDER: company size]
+- [PLACEHOLDER: key characteristic — e.g. "companies undergoing AI transformation"]
+
+---
+
+## Engagement model
+
+[PLACEHOLDER: describe how Pareto typically works with clients.
+e.g. retainer / project-based / productised service / advisory]
+
+Typical engagement length: [PLACEHOLDER]
+Typical team size per engagement: [PLACEHOLDER]
+
+---
+
+## Pricing principles
+
+[PLACEHOLDER: brief description of how Pareto prices work.
+e.g. day rate, fixed-price projects, retainer tiers]
+
+---
+
+## Our positioning
+
+**We are not:**
+- [PLACEHOLDER: e.g. a traditional consulting firm]
+- [PLACEHOLDER: e.g. a software agency]
+
+**We are:**
+- [PLACEHOLDER: e.g. an AI-first transformation partner]
+
+---
+
+## Tone and communication style
+
+- [PLACEHOLDER: e.g. direct, no jargon, evidence-led]
+- [PLACEHOLDER: e.g. collaborative — we work with clients, not at them]
+- [PLACEHOLDER: e.g. pragmatic — we focus on what moves the needle]
+
+When writing on behalf of Pareto:
+- Use "we" for Pareto
+- Avoid buzzwords like "synergy", "leverage" (as a verb), "ecosystem"
+- [PLACEHOLDER: any other style preferences]
+
+---
+
+## Key people
+
+| Name | Role |
+|---|---|
+| [PLACEHOLDER] | Founder |
+| [PLACEHOLDER] | [PLACEHOLDER] |
+
+---
+
+## Constraints and principles
+
+- We are a Dutch BV — all contracts governed by Dutch law
+- GDPR compliance is non-negotiable for all client work
+- [PLACEHOLDER: any other hard constraints]
+
+---
+
+## Tools and stack
+
+- Knowledge: Obsidian (this vault)
+- Project tracking: Linear
+- Deliverables: Google Drive
+- Communication: Slack, Gmail (Google Workspace)
+- Development: Claude Code, GitHub, Docker, AWS/GCP
+- Finance: Moneybird

package/pareto-skills/pp-obsidian-notes/templates/proposal.md

@@ -0,0 +1,117 @@
+---
+type: proposal
+client: [PLACEHOLDER: Full Client Name]
+version: [PLACEHOLDER: v1]
+date: [PLACEHOLDER: YYYY-MM-DD]
+status: draft
+---
+
+# Proposal — [PLACEHOLDER: Engagement Title]
+**Prepared for:** [PLACEHOLDER: Full Client Name]
+**Prepared by:** The Pareto Project
+**Date:** [PLACEHOLDER: YYYY-MM-DD]
+**Version:** [PLACEHOLDER: v1]
+
+---
+
+## The situation
+
+[PLACEHOLDER: 2–3 sentences on the client's current situation and the problem or
+opportunity this proposal addresses. Written from their perspective — what is
+happening in their world that makes this work important right now?]
+
+---
+
+## What we propose
+
+[PLACEHOLDER: clear description of what Pareto will do. Avoid jargon.
+Write it so the client could describe it accurately to a colleague.]
+
+---
+
+## Scope of work
+
+### Phase 1 — [PLACEHOLDER: phase name]
+[PLACEHOLDER: description of what this phase covers]
+
+**Deliverables:**
+- [PLACEHOLDER]
+- [PLACEHOLDER]
+
+**Duration:** [PLACEHOLDER: e.g. 3 weeks]
+
+---
+
+### Phase 2 — [PLACEHOLDER: phase name]
+[PLACEHOLDER: description]
+
+**Deliverables:**
+- [PLACEHOLDER]
+
+**Duration:** [PLACEHOLDER]
+
+---
+
+## What's not in scope
+
+[PLACEHOLDER: explicit list of things this engagement does NOT cover.
+This protects both parties and sets clear expectations.]
+
+- 
+- 
+
+---
+
+## How we'll work together
+
+[PLACEHOLDER: brief description of the working model.
+e.g. weekly check-ins, async updates via Slack, deliverables reviewed in shared Drive]
+
+**Your time commitment:** [PLACEHOLDER: e.g. ~2 hours/week for reviews and input]
+
+---
+
+## Investment
+
+| Item | Amount |
+|---|---|
+| [PLACEHOLDER: Phase 1] | €[PLACEHOLDER] |
+| [PLACEHOLDER: Phase 2] | €[PLACEHOLDER] |
+| **Total** | **€[PLACEHOLDER]** |
+
+**Payment terms:** [PLACEHOLDER: e.g. 50% upfront, 50% on completion]
+**Invoicing:** Via Moneybird, 30-day payment terms
+
+---
+
+## Timeline
+
+| Milestone | Date |
+|---|---|
+| Kick-off | [PLACEHOLDER: YYYY-MM-DD] |
+| [PLACEHOLDER: Phase 1 complete] | [PLACEHOLDER] |
+| [PLACEHOLDER: Final delivery] | [PLACEHOLDER] |
+
+---
+
+## Why Pareto
+
+[PLACEHOLDER: 2–3 sentences on why Pareto is the right partner for this.
+Specific to this client and engagement — not generic credentials.]
+
+---
+
+## Next steps
+
+To proceed:
+1. Review this proposal and share any questions or changes
+2. Sign the accompanying engagement letter
+3. Pay the initial invoice
+4. We schedule kick-off for [PLACEHOLDER: date]
+
+Questions? Reach us at [PLACEHOLDER: email or Slack]
+
+---
+
+*This proposal is valid until [PLACEHOLDER: YYYY-MM-DD].*
+*Governed by Dutch law. VAT number: [PLACEHOLDER].*