harness-builderlisted

# Harness builder A harness here is a profile: `tack-<name>`, a repo under your `$HARNESS_ORG` holding a `manifest.json`, an `install.sh` and optional `skills/`, pinning tack as the `core` submodule. `tack use <name>` composes Claude and Codex from it. Most of the work is choosing less, not more: everything a profile enables costs context in every session. ## Phase 1: research (read, write nothing) 1. Ask what the work is, which agent runs it (Claude, Codex, both), whether client material is involved, and which machines need it. One round of questions, then proceed on defaults. 2. Read the closest manifest in the tack repo's `profiles/` and copy its shape. 3. Take stock of what every profile already gets, so you do not add it twice: - every skill in tack's `skills/` is installed in every profile. Never list one in `skills_link`. - `base-settings.json` sets the baseline plugins and owns the marketplaces. 4. Candidates, cheapest first: an existing core or profile skill, a plugin from a marketplace already in `base-settings.json` `extraKnownMarketplaces`, a public skill (`npx skills find <query>`), an MCP server. For each, write one line on what it is for and what it costs. ## Phase 2: design, then stop for approval Write the proposed `profiles/<name>/manifest.json` (schema v2, see `manifest.schema.json`) and show it with one line per entry saying why. Rules the engine enforces, so check them before proposing: | Want | Constraint | |---|---| | Plu