bootstrap-project

bootstrap-project

Overview

Bootstrap a project from available design and requirements inputs with review-first output. This skill turns a blank or partially documented project into a fully initialized workspace with minimal effort.

When to Use

• Use when initializing a project baseline or reconciling missing setup artifacts.
• Use when you have design documents, PRDs, ADRs, or requirements and want the agent to infer tech stack, quality commands, and initial task list.
• Use when bringing an existing project into alignment with governance requirements (missing docs/, ROADMAP.md, File-Structure-Reference.md, etc.).
• Don't use for incremental changes — this is for initial project setup or major re-initialization.

Existing project mode

When the project already has work (design docs, tools, skills, state reports):

1. Read ALL existing artifacts before generating anything — design docs, state reports, existing governance files, profile configs, tools, skills, templates.
2. Infer constraints from actual code — not just design docs. Check tool I/O patterns, skill specs, and config values to determine what actually exists vs. what was planned.
3. Cross-reference state reports — if a Phase_N_State_Report.md exists, use its gap analysis as the primary input for ROADMAP.md checkpoints.
4. Do NOT treat design docs as ground truth — design docs describe intent; actual implementation may differ. Verify against existing files.
5. Generate docs that reflect reality — File-Structure-Reference.md must match actual tree; Project-Constraints.md must be sourced from actual config files, not just design doc assertions.
6. Flag stale artifacts — note duplicate directories, outdated line counts, broken path references in the review summary.
7. Update ROADMAP.md with both completed AND remaining work — use the state report's completion percentage and gap analysis as the foundation.

Inputs

• requirements.md and/or design docs if present
• Existing repository structure and configuration files