setup-context-driven

Files (1)

• SKILL.md

SKILL.md (first lines)

# Setup Context-Driven

Use the public `roundfix baseline` command family. The Roundfix binary is the
only runtime authority for Baseline Profiles, repository inspection, Decision
Plans, Change Plans, confirmation, apply, recovery, and Baseline verification.
This skill supplies recipes and interpretation only. It has no independent
setup engine or behavioral fallback.

Read the durable operating contract before the first adoption or a recovery:
`docs/user-guide/context-driven-development.md#adopt-or-update-the-context-driven-baseline`.

## Who starts this skill

An Agent may start this skill itself when its dispatch trigger matches; its
metadata does not turn off model invocation. Starting it authorizes no write.
Present the Plan and its Plan Digest first, and pass `--confirm-plan <digest>`
or `--yes` only after the person approves that Plan Digest or the
repository's own instructions already authorize it.

## Boundaries

Baseline owns declared root blocks, setup-owned guides, first-adoption
root-instruction backups, and `docs/agents/setup-context.json`. It preserves
repository-authored bytes outside managed boundaries.

Baseline never:

- installs application or Agent dependencies;
- connects to a database or live infrastructure;
- runs repository formatter, build, test, lint, migration, or Verification
  commands;
- follows unsafe links or mutates nested instruction carriers;
- infers repository policy from implementation evidence;
- lets ACP proposals authorize mutation;
- combines profiles or loads user-scoped or remote profiles.

Treat profile expectations, repository commands, and recommendations as
different facts. A profile expectation is portable policy, not implementation
proof. A repository command is executable only when the result says
`repositoryExecutable: true` and binds a local declaration. A recommendation
is a command for the maintainer to run; Baseline did not execute it.

## Interpret composed guidance

Read the generated root Instruction Hierarchy from universal instructions
through context and documentation, Spec workflow, enabled autonomous work,
stack guidance, surface guidance, and optional knowledge sources. A narrower
guide may add constraints for its concern but cannot weaken a universal
Normative Clause or confirmed project decision.

Greenfield composition emits only guides and pointers selected by the Baseline
Profile. It creates no generic repository guide and no residual carrier when
there are no Repository-Specific Normative Rules.

When Greenfield retains managed source that needs classification, Greenfield
refuses and names `preservation.mode=preservation` as the route to choose.

For update or Baseline Readoption, interpret the complete retention ledger
before approving it. Every existing rule must retain its exact source bytes in
one active semantic owner, a recognized typed repository document, or
`docs/agents/specific-repository.md`, or have an individual reasoned rejection
or non-governed classification. An empty residual removes the carrier and root
pointer; non-empty accepted residuals retain only their exact rules.

Generated `docs/agents/docs-layout.md` owns the copyable ADR and Findings
contracts. Only `accepted` is active for ADRs; legacy ADRs without lifecycle
frontmatter remain active unless their body marks them inactive. Findings use
`pending`, `partial`, `deferred`, and `done`, plus the terminal statuses
`deprecated`, `superseded`, `closed`, and `cancelled`, keep the original observation,
and append later evidence as dated addenda. Copy those generated templates;
this skill does not render or replace them.

## Refresh an adopted repository

When the repository has a compatible Setup Manifest, use the non-interactive
managed-refresh path:

```bash
roundfix baseline update --repo . --format json
```

Without confirmation, a changed Plan is presented and repository bytes remain
unchanged. For a fleet sweep, approve the Plan Digest computed in the same
invocation:

```bash
roundfix baseline update --repo . --yes --format json
```

The command derives the current Baseline Profile and compatible decisions from
the Setup Manifest. It asks no settled question and does not invoke semantic
classification. It changes only Baseline-managed regions and the Repository
Skill Set; every byte outside managed boundaries remains byte-identical.

Use `--confirm-plan <digest>` instead of `--yes` for a previously reviewed Plan
Digest. A decision absent from the manifest exits `3` without writing unless
the maintainer explicitly chooses `--adopt-suggested`. Use `--no-skills` only
to suppress the Repository Skill Set refresh, and `--skills-source-dir <path>`
only for a declared offline Git checkout or bare object store.

Repositories select their fast local command through
`verification.incremental`, separately from the complete
`verification.gate`. A single-gate Setup Manifest exits `3`, names the missing
incremental decision, and writes nothing. After the repository declares the
suggested `make verify-incremental` command locally, rerun update with
`--adopt-suggested`; later updates use the recorded decision without that flag.

## Human adoption or profile change

At an interactive terminal, run:

```bash
roundfix baseline --repo . --format text
```

The interactive workflow handles first adoption, a Baseline Profile change, or
a decision the Setup Manifest does not carry. It selects exactly one Baseline
Profile and shows one consolidated Change Plan with file changes first. With a
compatible Setup Manifest it skips settled decisions and semantic

From marcioaltoe/skills, MIT.

More from marcioaltoe/skills