hiddink-harness:goal

Orchestrate goal-to-execution workflows with gap detection, codebase analysis, and verification stages.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-goal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiddink-harness:goal
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/goal
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-goal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates scope creep and execution ambiguity by enforcing a structured, multi-stage workflow for any user-provided task, ensuring that planning, verification, and reporting are handled consistently.

Core Features & Use Cases

  • Disciplined Orchestration: Automatically routes tasks through gap detection, codebase analysis, and verification stages.
  • Standardized Verification: Ensures all changes are validated against project conventions before completion.
  • Use Case: Use this when you need to perform a complex refactor or feature addition and want to ensure the agent follows a rigorous plan-execute-verify cycle rather than jumping straight into code.

Quick Start

Invoke the goal skill by typing /goal followed by the specific task description you want the agent to execute with full project discipline.

Frequently Asked Questions about hiddink-harness:goal

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

FAQPage Schema
How do I enforce a structured plan-execute-verify cycle for complex refactoring tasks?

A structured plan-execute-verify cycle enforces multi-stage workflow orchestration by routing tasks through gap detection, codebase analysis, and verification stages to eliminate scope creep and ensure rigorous completion checks.

What is disciplined goal-to-execution workflow in software development?

Disciplined goal-to-execution workflow is an orchestration process that integrates gap detection and codebase analysis to resolve execution ambiguity, ensuring planning, verification, and reporting are handled consistently for complex tasks.

Does automated workflow orchestration work for complex feature additions without scope creep?

Automated workflow orchestration works for complex feature additions by standardizing verification against project conventions and applying structured planning, which prevents scope creep and execution ambiguity.

What's the best way to automate rigorous completion checks and evidence-based reporting for code changes?

The best way to automate rigorous completion checks is through a unified entry point that validates changes against project conventions during the verification stage, producing evidence-based reporting upon task completion.

When should I use automated task orchestration over jumping straight into code?

You should use automated task orchestration when performing complex refactors or feature additions that require safety, parallel execution, and evidence-based reporting, rather than jumping straight into code unstructured.