repo-change-goal-skill

Revise repository Goal Charter files with draft-and-confirm workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you need to change the repository-level Goal Charter, it helps analyze the impact on existing work and safely rewrite the control reference signals without breaking the harness control loop.

Core Features & Use Cases

  • Impact analysis before changes: Evaluates target differences, change magnitude, affected worktracks, baseline validity, engineering node map updates, and threatened invariants.
  • Draft → confirm → execute workflow: Produces a structured change analysis report and a full goal-charter draft, then writes files only after explicit user confirmation.
  • Correct control-state synchronization: Updates .servo/goal-charter.md, .servo/repo/snapshot-status.md, and .servo/control-state.md together to ensure the system re-observes downstream state.

Quick Start

Ask the harness to run repo-change-goal-skill to modify your repository’s Goal Charter based on your updated target request, and confirm the proposed draft after review.

Frequently Asked Questions about repo-change-goal-skill

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

FAQPage Schema
How do I safely revise a repository Goal Charter without breaking the control loop?

To safely revise a Goal Charter, use a draft-and-confirm workflow that analyzes worktrack and baseline impacts before atomically updating goal-charter, snapshot-status, and control-state files together.

What is impact analysis for goal charter updates?

Impact analysis for goal charter updates evaluates target differences, change magnitude, affected worktracks, baseline validity, and engineering node map updates to identify threatened invariants before execution.

How do I update control-state and snapshot-status when changing repo targets?

Updating control-state and snapshot-status requires atomically writing these files alongside the goal-charter draft after explicit confirmation, ensuring the system correctly re-observes downstream state.

Can I apply minor or moderate goal updates to a RepoScope target without breaking baselines?

Yes, you can apply minor, moderate, or major goal updates to RepoScope targets by evaluating baseline validity and routing worktracks through structured impact analysis before executing changes.

Does the goal charter revision process support a draft and confirm workflow?

Yes, the goal charter revision process supports a draft and confirm workflow by generating a structured change analysis report and full draft, writing files only after explicit user confirmation.

When should I not use automated goal charter revisions?

You should not use automated goal charter revisions when invariants are threatened by the target change, as the impact analysis phase identifies control-loop inconsistencies that require manual intervention.