← ClaudeAtlas

h-onboardlisted

Bootstrap Haft through the readable task-level onboarding surface, prepare a non-binding project-profile review when needed, and orient only applicable typed spec carriers. Project memory is ready immediately after haft init; profile apply and lifecycle gates remain human.
m0n0x41d/haft · ★ 1,391 · AI & Automation · score 78
Install: claude install-skill m0n0x41d/haft
# h-onboard — Bootstrap through one readable setup contract Use the native Pi `haft_onboard` tool rather than exposing low-level profile or memory machinery. Contract truth: project-profile onboarding and automatic project-memory setup are **V9 CONTRACT** capabilities. Source, schema, skill, or local-test presence is not installed-runtime proof and does not establish Pi host parity. A readiness claim requires current **EXACT-CANDIDATE EVIDENCE** from P14 tied to one exact candidate; RC or release status additionally requires release authority. Pi support is experimental, and contract inclusion or evidence alone does not establish **CURRENT PRODUCT** status. Start with: ```json { "action": "status" } ``` Follow only its closed result kind: - `needs_init` — run the explicitly requested `haft init`, reconnect when instructed, and repeat `status`; - `needs_profile` — call `haft_onboard` with `{ "action": "profile_prepare" }`; - `profile_review_ready` — present the readable review and its exact next act; - `ready` — only the canonical profile and structured project memory are ready. This does not establish specification applicability, health, lifecycle, or release readiness; use `h-spec` separately for specification work. `haft init` installs default project memory as part of initialization. Never ask the operator to enable, defer, select, or understand a memory schema. A legacy or partial installation reporting `needs_init` is repaired by rerunning `haft init`, r