custom-goals

Transform vague objectives into verified task plans with explicit completion criteria.

Updated Jun 30, 2026

Search Tags:#workflow #verification #task planning #checklists #goal tracking #completion criteria

Ready to run

npx skills add https://github.com/Festo-Wampamba/Claude-Features --skill custom-goals

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: custom-goals
Source: https://github.com/Festo-Wampamba/Claude-Features/tree/main/skills/custom-goals
Command: npx skills add https://github.com/Festo-Wampamba/Claude-Features --skill custom-goals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns vague goals into concrete, checkable work items so completion is defined before work starts instead of assumed afterward.

Core Features & Use Cases

Goal restatement: Reframes a fuzzy request into a single-sentence objective when scope is unclear.
Verification-first tasking: Creates tasks with explicit what and verify criteria so each item has a test, command, or observable result.
Reliable completion checks: Requires tasks to be verified before being closed, reducing false confidence on finished work.
Use case: Use it when you want to ship a feature, clean up a codebase, or confirm whether a project is actually done.

Quick Start

Ask the assistant to turn your goal into a verified task list with clear completion checks before any work begins.

Frequently Asked Questions about custom-goals

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

FAQPage Schema

How do I turn vague objectives into verifiable tasks with clear completion criteria?▼

To turn vague objectives into verifiable tasks, reframe the request into a single-sentence goal and require each task to define the exact change alongside a specific command, test, or observable behavior that proves completion before closure.

What is verification-first task planning and how does it work?▼

Verification-first task planning creates tasks with explicit what and verify criteria. Each work item requires a test, command, or observable result to be defined upfront, ensuring completion is confirmed by proof rather than assumed after work finishes.

How do I track task completion and prevent false confidence on finished work?▼

You track task completion by requiring each item to pass its predefined verification check before closure. This reliable completion check prevents false confidence by demanding an exact test or observable behavior is met before marking any task done.

Can I use goal tracking and checklists for codebase cleanup efforts?▼

Yes, you can use goal tracking and checklists for codebase cleanup efforts. The system applies to any session where progress must be tracked, transforming cleanup objectives into verified task plans with observable completion criteria.

What's the best way to define task completion criteria before starting feature work?▼

The best way to define task completion criteria is stating the exact change to make and the specific command, test, or observable behavior that proves it is done. This ensures each feature work item has a checkable finish status before work begins.

When do I need to restate a fuzzy request into a single-sentence objective?▼

You need to restate a fuzzy request into a single-sentence objective whenever scope is unclear. Goal restatement reframes vague requests into concrete objectives, enabling the creation of verified task plans with explicit completion criteria.