goal

Define outcome specifications with evidence-grounded success criteria and anti-goals.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/tannishmango/skills --skill goal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal
Source: https://github.com/tannishmango/skills/tree/main/goal
Command: npx skills add https://github.com/tannishmango/skills --skill goal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents the "Goodhart's Law problem" where a measure becomes a target and ceases to be a good measure, by enforcing rigorous outcome specifications with evidence-grounded success criteria and explicit anti-goals.

Core Features & Use Cases

  • Rigorous Goal Definition: Define complex tasks with clear, measurable success criteria and constraints.
  • Evidence Grounding: Ensures goals are based on specific data, not vague objectives.
  • Anti-Goal Enforcement: Explicitly defines what must NOT happen, preventing harmful side-effects.
  • Use Case: When launching a new feature, use this Skill to define success not just by user adoption numbers, but also by ensuring no negative impact on system performance or user satisfaction.

Quick Start

Use the goal skill to define a new goal for improving system performance with specific success criteria and anti-goals.

Frequently Asked Questions about goal

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

FAQPage Schema
How do I define success criteria for complex tasks without triggering Goodhart's Law?

To prevent Goodhart's Law during goal setting, separate desired outcomes from measurement methods by defining evidence-grounded success criteria and explicit anti-goals. This approach ensures metrics remain valid indicators rather than becoming corrupted targets.

What are anti-goals in project management and when should I use them?

Anti-goals in project management explicitly define what must NOT happen during a task, preventing harmful side-effects. Use them when launching features to ensure no negative impact occurs on system performance or user satisfaction while pursuing primary objectives.

How do I set up outcome verification protocols for AI agent orchestration?

Setting up outcome verification for AI agent orchestration involves defining multi-dimensional success criteria with specific evidence requirements. This enforces rigorous outcome specifications that validate agent task completion against predefined constraints and desired results.

Can I use evidence-grounded goal setting for multi-dimensional project success criteria?

Evidence-grounded goal setting supports multi-dimensional criteria by basing objectives on specific data rather than vague intentions. This method ensures complex tasks are measured across multiple verification protocols to confirm comprehensive success without metric manipulation.

What is the best way to prevent negative side-effects when launching a new feature?

The best way to prevent negative side-effects during feature launches is enforcing explicit anti-goals alongside standard success criteria. This practice ensures user adoption numbers do not overshadow critical constraints like system performance or user satisfaction.

Why does measuring a target make it a bad metric for project management?

Measuring a target makes it a bad metric because of Goodhart's Law, where a measure becomes a target and ceases to be a good measure. Mitigate this by separating desired outcomes from their measurement methods during goal definition.