bootstrap

name	bootstrap
version	0.11.0
description	Bootstrap a NEW or EXISTING project folder for the praxis development lifecycle (PDLC), OR update an already-bootstrapped one after a plugin upgrade. Use when the user wants to set up praxisflux in a project, says "bootstrap this project for praxis/PDLC", "init the praxis lifecycle here", "wire this repo for grounding-wiki/spec-bridge/codebase-to-course", or asks how to get a folder ready for the plugin suite. Plants the always-on PDLC grounding (CLAUDE.md block), gitignores the .handoff/ transport, and handles the officially supported peer utilities — Backlog.md and GitHub Spec Kit — recommending installation when absent and offering opt-in (running their inits) when present.

pdlc:bootstrap — stamp a project for the praxis development lifecycle

This skill turns any folder — brand-new and empty, or an existing codebase with history and its own CLAUDE.md — into a PDLC project: one whose always-on context knows the praxisflux loop, each plugin's role, the gates principle, and the .handoff/ transport. It is the suite-level answer to "a plugin has no always-on slot": instead of bundling always-on context, plant it.

Everything it plants rides inside <!-- pdlc:grounding BEGIN/END --> markers, so it composes with an existing CLAUDE.md (appended, never clobbered) and can be refreshed wholesale on update. The heavy lifting is deterministic — scripts/plant.mjs on the chassis (lib/installer.mjs + lib/template.mjs) — this skill's job is the judgment around it.

What it does NOT do

• It does not run sibling skills or create their outputs. No docs/wiki/ (that's ), no (codebase-to-course), no lessons (educate has its own ). Bootstrap sets the table and .