set-harness-goal-skill

Generate Harness goal charter and control state artifacts under .servo/.

29|2|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/OceanEyeFF/servo --skill set-harness-goal-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: set-harness-goal-skill
Source: https://github.com/OceanEyeFF/servo/tree/main/product/harness/skills/set-harness-goal-skill
Command: npx skills add https://github.com/OceanEyeFF/servo --skill set-harness-goal-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, git, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

When a repository has not been initialized for Harness (or the goal charter is missing), this Skill turns a user's natural-language intent into the structured control-plane artifacts required to start a safe, closed-loop coding workflow.

Core Features & Use Cases

  • Goal Charter & Control State Generation: Creates .servo/goal-charter.md, .servo/control-state.md, and supporting RepoScope artifacts that bootstrap Harness reference signals.
  • Two Initialization Modes: Supports new goal creation and existing-code project adoption (with read-only discovery inputs).
  • Strict Safety & Routing Guardrails: Blocks contradictory actions (e.g., modifying an existing goal charter), prevents guessing, and routes to the correct downstream Skills when preconditions change.

Quick Start

Ask an AI operator to initialize Harness for the current repository by running set-harness-goal-skill with your goal description so it can generate a goal charter draft for your confirmation.

Frequently Asked Questions about set-harness-goal-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize a goal charter for an existing code repository?

Harness initialization uses read-only discovery to collect project context, then generates goal charter and control state artifacts under .servo/ for user confirmation before bootstrapping the closed-loop workflow.

What are control-plane artifacts and when do I need them for repo workflow safety?

Control-plane artifacts like goal-charter.md and control-state.md bootstrap deterministic reference signals. You need them when Harness is uninitialized to enforce workflow safety constraints and prevent ambiguous assumptions.

Does the goal charter generation process overwrite existing files?

No, the goal charter generation process enforces strict safety guardrails that block overwrites. It routes to downstream skills and blocks contradictory actions rather than modifying an existing goal charter.

Can I use natural language intent to generate a repo-scoped engineering node map?

Yes, you can provide natural-language intent to generate a repo-scoped engineering node map. The skill converts your input into structured templates-based artifacts that satisfy deterministic initialization requirements.

Do I need git and node installed to bootstrap a repo's control state?

Yes, you need git and node installed because they are required dependencies for executing the scripts that create the control state and supporting RepoScope artifacts safely.

Why does harness initialization block actions when preconditions change?

Harness initialization blocks actions when preconditions change to prevent guessing and enforce deterministic safety. It applies routing guardrails to ensure correct downstream skills handle modified initialization states.