Bootstrap Agentic OS

This skill sets up the scaffolding that makes Claude Code useful across many sessions on one project: a session lifecycle, a clean separation between stable reference and running state, and a sensible permission scheme. It interviews you about the project, then writes real files from your answers — not empty templates.

What it creates

• CLAUDE.md — the project’s reference manual: what you are building, the stack, the conventions that hold across sessions.
• CONTEXT.md — the running log: where the build is right now, what is done, what is left. Read at session start, updated at session end.
• .claude/start-session.md and .claude/wrap-session.md — the session lifecycle. Start by orienting and checking state before acting; wrap by updating the docs, reviewing the diff for anything sensitive, and committing cleanly.
• .claude/settings.json — a permission allowlist scoped to the safe, common operations.

Why the split

CLAUDE.md is stable; CONTEXT.md moves. Keeping them apart stops the reference manual from filling with stale state and stops the running log from burying the durable facts. The lifecycle docs make every session begin the same way — orient, report, wait for direction — so a project stays coherent across many separate sessions instead of drifting each time it is picked up.