onboard is agent-read markdown (skill) from swingerman/engineer: Use to bring a project into the DAE methodology, or to check an onboarded project for gaps. Triggers — "/engineer.onboard", "onboard this project", "set up DAE here", "adopt the methodology", or when a DAE skill fails because no manifest exists..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# onboard
Checkpoint 0 — the DAE adoption ceremony. Establishes the charter, manifest, storage layout, and tracker. Project-scope, run once. Every other DAE skill depends on what it produces.
**The goal.** Onboarding a project to DAE succeeds when there is a clear path to **full ATDD coverage of every feature — existing and new.** A new feature is born covered by going through the pipeline. An *existing* feature is covered retroactively.
**Onboarding is discovery and goal-setting — not the ATDD adoption itself.** It discovers what's there (documented *and* undocumented), triages it by importance, assigns each feature a status, and produces a **consolidation backlog**. Bringing any one feature to full ATDD coverage is a *follow-up task per feature* — bounded, automatable, and a good candidate for remote-agent dispatch. Onboarding sets the path; it does not walk it.
A feature is **fully ATDD-covered** when its folder has `feature.md`, `acs.md`, `spec.md` (+ `.build/spec.json` IR), and **generated acceptance tests that pass against the code**.
## When to use
- **No `.engineer/manifest.yml`** → full onboard (Steps 1–11)
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_c3tqnouk2dbl7v3y
GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/onboard
GET https://markdownregistry.com/api/v1/blob/b3553ea2636ace442785439ecea07445e295508a6d291849efef09298af40440
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
swingerman/engineer · crap-analyzer/skills/crap-analyzer/SKILL.md · Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP…
swingerman/engineer · engineer/skills/arch-check/SKILL.md · Use to check a feature's code against the charter's architecture rules — dependency layering, cycles, forbidden…
swingerman/engineer · engineer/skills/atdd/SKILL.md · Use to write a feature's acceptance specs and generate its test pipeline — Checkpoint 3 of the DAE pipeline. The…
swingerman/engineer · engineer/skills/clarify/SKILL.md · Use when a single DAE artifact has ambiguities to resolve. Triggers — "/engineer.clarify", "clarify this spec"…
swingerman/engineer · engineer/skills/consistency-check/SKILL.md · Use to validate DAE artifacts for schema correctness and cross-artifact consistency. Triggers —…
swingerman/engineer · engineer/skills/discover-acs/SKILL.md · Use when a Ready feature needs its acceptance criteria discovered before specs are written. Triggers —…
swingerman/engineer · engineer/skills/discuss/SKILL.md · Use when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss"…
swingerman/engineer · engineer/skills/express/SKILL.md · Use to build an XS (express-lane) feature in one pass — intake→implement→verify in a single context, no handoff chain…
swingerman/engineer · engineer/skills/feature-edit/SKILL.md · Use when an in-flight feature must change — scope shifts, an AC is refined, the plan evolves, a behavior is added or…
swingerman/engineer · engineer/skills/feature-init/SKILL.md · Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers —…
swingerman/engineer · engineer/skills/fix/SKILL.md · Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers —…
swingerman/engineer · engineer/skills/next/SKILL.md · Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project…
davepoon/buildwithclaude · plugins/ciagent/skills/onboard/SKILL.md · Set up CIAgent regression testing for the AI agent in this repo — write a runner, record golden baselines, generate a…
clacky-ai/openclacky · lib/clacky/default_skills/onboard/SKILL.md · Onboard a new user OR curate a single piece of the assistant's inner state. Without arguments, runs the full first-run…
athola/claude-night-market · plugins/gauntlet/skills/onboard/SKILL.md · Guides a new developer through five staged challenge sets covering architecture, domain, patterns, and hardening. Use…
jongwony/epistemic-protocols · epistemic-cooperative/skills/onboard/SKILL.md · Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz.
open-octo/octo-agent · internal/skills/defaults/onboard/SKILL.md · Onboard a new user OR curate a single piece of the assistant's inner state. Without arguments, runs the full first-run…
