auto-harness

Use when onboarding any existing project — codebase or documentation-only — into the development harness. Produces a governance inventory, repository inventory, module composition recommendation, artifact gap analysis, integration/translation guidance, validator runbook, and a copy-paste lite manifest. Activate with any Agent Skills-compatible client pointed at the target repository.

Trust tier enforcement, lifecycle controls, and companion rule requirements for projects using the development harness. Use when checking if an action requires human approval, creating or validating documentation artifacts, verifying lifecycle stage conditions, running validators, or making changes to governance entrypoints (HARNESS.md, AGENTS.md, CLAUDE.md, CI workflows).

Load the canonical auto-harness governance skill from platform/skills before changing harness governance, validators, trust tiers, companion rules, or repository operating doctrine.

Use for tasks involving digital twins, simulation, scenarios, world state, run logs, model/agent registries, data provenance, geospatial/city/infrastructure models, AI-datacenter or operational twins, or scenario manifests. Enforces maturity honesty, world/scenario/run separation, provenance, uncertainty disclosure, and publication boundaries for projects governed by the management/digital-twin overlay.

Use when a harness-governed project ships or designs an MCP (Model Context Protocol) server, or when an agent reasons about exposing harness governance to runtime harnesses via MCP. Covers the three MCP modes (consumer, producer, exposed-governance), per-tool consumer-tier mapping for exposed tools, prompt-injection defense surface, capability and transport posture, and the explicit boundary against the harness-tools skill (which governs consumed tools) and the harness-governance skill (which governs trust tiers and lifecycle).

Testing governance and practice guidance for projects using the development harness testing-standard module. Use when writing tests, analyzing coverage, choosing a testing strategy, configuring test frameworks, or evaluating whether a PR meets the project's declared coverage thresholds.

Use when invoking MCP developer tools (Linear, Slack, Google Calendar, Gmail, Canva, Ahrefs, Similarweb) in a harness-governed project. Covers trust tier requirements per tool, Linear as the artifact backing store for harness governance docs, Slack as the companion-rule notification surface, and analytics tools under read-only tier policy.

Governance rules for blockchain-integrated systems under the development harness — UNKNOWN state propagation policy, rate limit budget enforcement, evidence requirements for risk signals, irreversibility review gates for transaction-signing, and scoring rule discipline. Use when working on Web3 data access, smart contracts, token systems, scoring rules, chain configuration, or on-chain analytics.

Use when working in a harness-governed project that ships an in-product agentic interface — copilots (CopilotKit-style), generative UI (A2UI-style), or conversational-primary surfaces (MCP Apps, ChatGPT Apps). Covers the three-flavor map (Controlled / Declarative / Open-ended / Conversational-primary), tier discipline for agent-callable actions, prompt-injection and generative-UI threat model, renderer-contract decision guidance, CopilotKit vs A2UI vs MCP-Apps vs custom selection, and how human-in-the-loop checkpoints declared in the design doc are kept in sync with code.