custom-goals

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.

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.

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.

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.

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.

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.