harness-initlisted

# Harness Init ## Core Rule Scaffold the `docs/` structure additively — never overwrite an existing file. Every directory and file is created only if missing. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/harness-init` when: - A project has outgrown a single CLAUDE.md and you want to switch to a `docs/` harness layout (per [OpenAI's harness engineering pattern](https://openai.com/index/harness-engineering/)) - You're starting a new project and want the harness scaffold from day one - You're migrating from a `.claude/`-only setup and want a more durable knowledge base alongside the agent rules Not for: - Fresh kit installs where you haven't decided yet — just run the default `install.sh`; the harness pattern is opt-in - Projects where `docs/` already exists with a different convention — manually merge instead of running this skill ## Scope Rules - **Idempotent**: every file/directory is created only if missing. Existing content is never touched. - Operates only on `docs/` and its children, plus an optional one-line section addition to `CLAUDE.md` (only if the project's CLAUDE.md doesn't already reference `docs/`) - Never modifies files un