ai-skills-bootstrap-project

Files (2)

• SKILL.md
• bootstrap-surface-status.md · references/

SKILL.md (first lines)

<!-- markdownlint-disable MD025 -->

# Purpose

Run a clean project bootstrap sequence so the new project starts with a
repository home, downstream instruction wiring, framework baseline, CI, and
documentation that fit together.

# When to Use

- use when a new project must be bootstrapped end to end rather than through a
  single setup concern
- use when repository, ai-instructions, framework, CI, and documentation work
  must be sequenced safely
- use when later setup choices depend on earlier bootstrap outputs
- use `references/bootstrap-surface-status.md` when the composed bootstrap
  result must distinguish full completion from partial completion with named
  gaps

# Inputs

- the project goal, team, hosting constraints, and delivery expectations
- repository, framework, runtime, CI, and documentation preferences or
  constraints
- whether version-selection decisions for dependencies or support policy are
  already explicit
- which bootstrap surfaces are in or out of scope for the current project
- known blockers or partial-delivery expectations for any bootstrap surface
- `references/bootstrap-surface-status.md`

# Workflow

## Composed Skills

This is a composite skill. It orchestrates these children in dependency order:

- skill `ai-skills-bootstrap-repository`
- skill `ai-skills-bootstrap-ai-instructions`
- skill `ai-skills-bootstrap-framework-setup`
- skill `ai-skills-bootstrap-ci-pipeline`
- skill `ai-skills-bootstrap-documentation`

## Bootstrap Sequence

1. Confirm the project really needs a multi-surface bootstrap rather than a
   single leaf setup task.
2. Before running child skills, classify each bootstrap surface as in scope or
   `out-of-scope`. Use `out-of-scope` only for intentionally excluded
   surfaces. If an in-scope surface is intentionally not run, its final status
   must be `skipped` with an explicit reason. Then track final child results
   using only `completed`, `blocked`, `skipped`, or `out-of-scope` according
   to `references/bootstrap-surface-status.md`.
3. If `repository` is in scope and should run, apply skill `ai-skills-bootstrap-repository`
   to establish the hosted project home and repository-level policy decisions.
   If it is in scope but intentionally not run, do not run the child and
   record the surface in the next step with status `skipped`. Otherwise, do
   not run the child and record the surface in the next step with status
   `out-of-scope`.
4. Record the repository child result using the required per-surface fields
   from `references/bootstrap-surface-status.md`, including the final status,
   the child skill used, the handoff output or explicit `none`, and the
   blocker, skip reason, out-of-scope rationale, or named gap when the status
   is not `completed`.
5. If `ai-instructions` is in scope and should run, apply skill `ai-skills-bootstrap-ai-instructions`
   so the downstream instruction layer is wired before project-specific
   implementation patterns spread. If it is in scope but intentionally not
   run, do not run the child and record the surface in the next step with
   status `skipped`. Otherwise, do not run the child and record the surface in
   the next step with status `out-of-scope`.
6. Record the ai-instructions child result using the same required
   per-surface fields, including the handoff output or explicit `none`, plus
   the blocker, skip reason, out-of-scope rationale, or named gap when the
   status is not `completed`.
7. If `framework` is in scope and should run, apply skill `ai-skills-bootstrap-framework-setup`
   to establish the working framework, runtime, and toolchain baseline. If it
   is in scope but intentionally not run, do not run the child and record the
   surface in the next step with status `skipped`. Otherwise, do not run the
   child and record the surface in the next step with status `out-of-scope`.
8. Record the framework child result using the same required per-surface
   fields, including the handoff output or explicit `none`, plus the blocker,
   skip reason, out-of-scope rationale, or named gap when the status is not
   `completed`.
9. If `ci` is in scope and should run, apply skill `ai-skills-bootstrap-ci-pipeline`
   so the project baseline is checked continuously. If it is in scope but
   intentionally not run, do not run the child and record the surface in the
   next step with status `skipped`. Otherwise, do not run the child and record
   the surface in the next step with status `out-of-scope`.
10. Record the CI child result using the same required per-surface fields,
    including the handoff output or explicit `none`, plus the blocker, skip
    reason, out-of-scope rationale, or named gap when the status is not
    `completed`.
11. If `documentation` is in scope and should run, apply skill `ai-skills-bootstrap-documentation`
    last so the initial docs reflect the actual repository, framework, and CI
    decisions already made. If it is in scope but intentionally not run, do
    not run the child and record the surface in the next step with status
    `skipped`. Otherwise, do not run the child and record the surface in the
    next step with status `out-of-scope`.
12. Record the documentation child result using the same required
    per-surface fields, including the handoff output or explicit `none`, plus
    the blocker, skip reason, out-of-scope rationale, or named gap when the
    status is not `completed`.
13. Distinguish a full bootstrap from a partial bootstrap. Full bootstrap
    means every in-scope child finished as `completed` and every excluded
    surface is explicitly `out-of-scope`; partial bootstrap means one or more
    in-scope children are `blocked` or `skipped`, and each gap must be named
    explicitly.

# Outputs

- an ordered project-bootstrap decision record
- all in-scope bootstrap surfaces delegated to the correct child skills
- a per-surface status record using only `completed`, `blocked`, `skipped`, or
  `out-of-scope`
- explicit surface handoff outputs and named remaining gaps when the bootstrap is
  partial
- a coherent starting project baseline across repository, instructions,
  framework, CI, and documentation

# Guardrails

From fabian-barney/ai-skills, Apache-2.0.

More from fabian-barney/ai-skills