implementation-harness-createlisted

# Scaffold the implementation harness into a project You are installing a self-contained autonomous build harness into a target project and **personalizing** it. The harness is a single sequential shell loop that builds a `TASKS.json` backlog one fully-verified task at a time, at an auto-tuned (policy-chosen) model tier, gated on green GitHub CI. Read this whole file, then execute the steps **in order**. Be conversational and concise; confirm before anything destructive. ## 0. Locate the bundled templates The plugin ships the harness under a `templates/` dir. Resolve it robustly (the env var differs by context) and cache the path as `TPL`: ```bash TPL="${CLAUDE_PLUGIN_ROOT:-}/templates" [ -d "$TPL" ] || TPL="${CLAUDE_SKILL_DIR}/../../templates" TPL="$(cd "$TPL" && pwd)" # normalize ls "$TPL" # sanity: expect config/ custom/ docs/ scripts/ tasks/ tracking/ worklog/ .github/ CLAUDE.md README.md gitignore ``` If `TPL` doesn't resolve to a dir containing `scripts/loop.sh`, stop and tell the user the plugin install looks broken (templates not found). > Note the template stores the gitignore as `gitignore` (no leading dot) so it ships inside the > plugin; you will write it into the target as `.gitignore`. ## 1. Resolve the target project - Target dir = the skill argument if given, else the current working directory. - Confirm it's a git repo: `git -C "<target>" rev-parse --git-dir` succeeds. If not, ask whether to `git init` it (the loop needs git + i