craft-harness

Purpose

Given a repo, decide where agent guidance belongs and make or propose the smallest useful harness change.

A harness is the repo-local guidance and supporting surfaces that help coding agents work well: root context, local context/rules, skills, commands, scripts, and approval-gated candidates such as hooks, subagents, MCP/integrations, plugins, or external assets worth adopting.

This skill is placement judgment, not a "build every surface" workflow: inspect what exists, decide what should stay small, name what should change, and gate anything executable or global.

Non-goals

• Not a global config manager, installer/plugin publisher, or runtime framework.
• Not a replacement for the user's agent settings UI or marketplace flow.
• Not a full implementation pass for every harness surface; default output is a repo-local plan, small markdown/skill edits, or reviewable asset recipes.

Use this when