Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

bootstrap-project

Bootstrap a new project at a chosen graduation tier (t0 minimum, t1 decision-tracked, t2 full pattern language) following AI-Assisted Project Orchestration best practices. Use when starting a new software project, promoting an existing project to a higher tier, or converting an existing project for AI-assisted development.

jrjsmrtn · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add jrjsmrtn/project-orchestration-skills --skill bootstrap-project

About this skill


name: bootstrap-project description: Bootstrap a new project at a chosen graduation tier (t0 minimum, t1 decision-tracked, t2 full pattern language) following AI-Assisted Project Orchestration best practices. Use when starting a new software project, promoting an existing project to a higher tier, or converting an existing project for AI-assisted development. metadata: author: "Georges Martin jrjsmrtn@gmail.com" version: "0.1.34" license: MIT

Project Bootstrap

Bootstrap a new project with foundational artifacts following AI-Assisted Project Orchestration best practices. Implements the Tiered Bootstrap pattern with three graduation tiers (t0/t1/t2) so that decision rationale is captured at decision-time and tier promotion is reformatting, not archaeology.

When to Use

  • Starting a new software project (pick a tier appropriate to scope)
  • Promoting an existing project from a lower tier to a higher one
  • Converting an existing project to follow best practices
  • Setting up a project for AI-assisted development

Pattern Reference: See TIERED-BOOTSTRAP for the underlying pattern, including knowledge-preservation argument and the comparison with spec-driven development tools.

Required Inputs

Before running this skill, gather from the user:

  1. Project name (kebab-case, e.g., my-awesome-project)
  2. Project description (1-2 sentences)
  3. Tier (graduation level — see Tier Selection below):
    • t0 — minimum viable foundation (CLAUDE.md + git + conventional-commits)
    • t1 — decision-tracked project (+ foundation ADRs + pre-commit + changelog)
    • t2 — full pattern language (+ Diátaxis + C4 + sprint cadence + roadmap) — default
  4. Project category:
    • Development: Software (applications, libraries, services)
    • Infrastructure: Operations (homelab, deployment, monitoring)
    • Hybrid: Both development and operations components
  5. Project type (library, web application, CLI tool, API service, infrastructure automation)
  6. Technology stack (e.g., "Elixir/Phoenix/Ash", "Python/FastAPI", "Ansible")
  7. License (MIT, Apache-2.0, proprietary) — required at t1+, optional at t0
  8. Git remotes (private origin only, or multi-remote with public GitHub/GitLab)
  9. Distribution profile (exposure — orthogonal to the tier): Private (default — internal/homelab/WIP) or Public (open-sourced on a public forge and properly licensed). Set the ships-artifacts marker if the maintainer will publish built packages/images to a registry (Hex/PyPI/GHCR/containers) or signed release binaries. The profile governs which compliance controls apply — see Distribution Profile below.

Why project category matters:

  • Development: ADR-0004 (Operations) is skipped
  • Infrastructure: ADR-0004 is created (backup, monitoring, change management)
  • Hybrid: ADR-0004 is created, covering both application and infrastructure operations

Tier Selection

This skill implements the Tiered Bootstrap pattern. Each tier is a strict superset of the previous one. Pick the lowest tier that fits the project's current state — promotion is mechanical (reformat / reorganize), not archaeological.

Project stateRecommended tier
Same-day exploration, weekend prototypet0
Multi-week solo project, expected to outlive prototypet1
Multi-contributor, professional, or upstream-OSS-boundt2 (default)
Existing prototype with chat-only historyt0 immediately, then promote

Promotion triggers:

  • t0 → t1: more than one contributor, project survives two weeks, first decision deserves a numbered record
  • t1 → t2: docs need structure beyond CLAUDE.md, architecture needs visual artifacts, work needs sprint-scale planning, project nears 1.0

Knowledge-preservation property: at every tier, decision rationale is captured at decision-time in durable, version-controlled artifacts (CLAUDE.md, conventional commits, ADRs). No tier requires recovering rationale from non-durable sources (chat logs, agent session memory).

Distribution Profile

Orthogonal to the tier. The tier measures process maturity; the distribution profile measures exposure — how far the software travels — which is what actually gates compliance controls. A mature internal tool has no external obligations; an early public library incurs them the moment it ships. Set the profile at inception (default Private), and graduate it like the tier.

Profile / markerTriggerControls it adds
Private (default)internal / homelab / WIPbaseline hygiene (secret scanning — already universal)
Publicopen-sourced on a public forge and licensedLICENSE/REUSE, SECURITY.md + coordinated disclosure (Phase 9), OpenSSF Scorecard aspirational
ships-artifacts (marker)publishes built packages/images to a registry, or signed release binaries+ SLSA provenance, SBOM, signing, trusted publishing (via harden-github-actions, wrapup-sprint)

Going Public is making the source redistributable (licensing is part of the gate), so there is no separate "distributed" level. ships-artifacts is a boolean, not a rung — set it when going public, later, or never. Controls attach to the profile, not the tier, so a project pays only for its actual exposure. Record the profile in CLAUDE.md ## Project Context; promotion to Public is the public-release graduation gate (project-maintenance-skills).

This axis maps to recognized frameworks: Public → EU CRA "open-source steward" duties + OpenSSF Best Practices; ships-artifacts → SLSA / EEF Ægis trusted publishing. Treat these as guidance, not legal advice. The commercial case (placing on the EU market for pay), which triggers ful

Read the complete source ↗