pavilio-bootstrap

Generate PROJECT.md, STATUS.md, and _index.json files from existing project meeting notes.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gmotyl/pavilio --skill pavilio-bootstrap-gmotyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pavilio-bootstrap
Source: https://github.com/gmotyl/pavilio/tree/main/skills/pavilio-bootstrap
Command: npx skills add https://github.com/gmotyl/pavilio --skill pavilio-bootstrap-gmotyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Projects accumulate meeting notes over time but lack a structured, searchable summary. This Skill rebuilds the project knowledge layer — a stable resume card, a volatile status file, and a JSON search index — directly from the note history, so nothing has to be reconstructed by hand. ## Core Features & Use Cases - Entity extraction from notes: Scans dated Markdown notes to extract people, decisions, technologies, action items, and topics. - Structured file generation: Produces PROJECT.md (stable facts, 60-line cap), STATUS.md (current focus, open questions, recent decisions, active team), DECISIONS.md, and _index.json with full search metadata. - Legacy migration: Splits an old all-in-one PROJECT.md into the card + STATUS.md split without losing pruned content. - Use Case: After months of ad-hoc meeting notes in a project folder, run the bootstrap to instantly get a dashboard-ready project card, a pruned status file, and a searchable index covering the full date range. ## Quick Start Ask the AI to bootstrap the project knowledge files for a named project, or say bootstrap all to process every project folder.

Frequently Asked Questions about pavilio-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a project summary from meeting notes?▼

Run the bootstrap with a project name or "all". It scans every dated Markdown note in the project folder, extracts people, decisions, technologies, and topics, then writes PROJECT.md, STATUS.md, and _index.json.

How to migrate a legacy PROJECT.md into separate files?▼

The bootstrap moves Team, Focus, Open Questions, and Key Decisions sections from an all-in-one PROJECT.md into STATUS.md, pruned to defined caps, then rewrites PROJECT.md as a stable resume card. Pruned rows remain in _index.json and the notes.

What files does the project bootstrap create?▼

It creates PROJECT.md (stable facts, 60-line cap), STATUS.md (current focus, open questions, recent decisions, active team), DECISIONS.md (full decision history), and _index.json (structured search index of all notes).

Can I bootstrap all projects at once?▼

Yes. Passing "all" iterates every folder in the projects directory, checks for existing Markdown notes, generates the knowledge files for each, and reports progress per project.

What counts as a decision when extracting from notes?▼

Notes with the current template contribute their Decisions section as-is. In older notes, only statements about what was decided, agreed, or chosen qualify; proposals and technology tradeoff observations are skipped unless explicitly decided.