Skill: Bootstrap Project Documentation

Purpose

Bootstrap or adapt project documentation using the project-documentation-template structure. Two modes: Initialize (empty project—copy templates and fill placeholders) and Adjust (non-empty—use template as target, propose renames/moves/merges, apply in-place after confirmation). Supports repeatable runs; avoids empty dirs and template files unless requested; enforces strict kebab-case naming. Output paths for skill-generated artifacts (ADR, backlog, design-decisions, calibration) follow spec/artifact-contract.md; project-documentation-template provides content and reference. When creating process-management structure, create docs/process-management/project-board/backlog/ and docs/process-management/decisions/ per contract.

Core Objective

Primary Goal: Produce structured lifecycle documentation aligned with the enterprise template through mode-appropriate bootstrapping or adaptation.

Success Criteria (ALL must be met):

1. ✅ Mode selected correctly: Initialize for empty projects, Adjust for non-empty projects (or user override applied)
2. ✅ Template structure applied: Documentation follows project-documentation-template conventions for selected scale
3. ✅ Placeholders filled: All [...] placeholders replaced with project-specific content (or explicitly marked for later)
4. ✅ Naming conventions enforced: All paths use strict kebab-case; ADR files follow YYYYMMDD-slug-title.md format
5. ✅ User confirmation obtained: In Adjust mode, changes applied only after user approval of recommendation list