goal_skill

This skill quickly creates a concise goal.md by a brief interview to plan technical tasks, ensuring a single actionable document.

Shell

31

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill steveclarke/dotfiles --skill goal

SKILL.md4.7 KB

Overview

This skill provides quick goal planning for technical tasks by compressing vision, requirements, spec, and plan into a single goal.md via a short conversational interview. It produces a compact, actionable document in 3–6 questions so you can move from idea to execution without full-feature overhead. Use it for anything larger than an ad-hoc change but smaller than a full product feature.

How this skill works

I interview you with focused, one-at-a-time questions across three phases: Discovery, Technical Approach, and Document Generation. I synthesize answers and project context into a single goal.md containing a goal statement, plain-language requirements, a brief technical approach, and an executable plan with checkboxes. Finally, I confirm a save location and mark the process phases complete so you can start work or iterate.

When to use it

Infrastructure work: deploy, configure, or set up a service
Small tools or scripts that need planning but not full specs
Migrations or technical configurations spanning multiple files/systems
Tasks larger than a one-off but not a full product feature
When you need a single, shareable document to align multiple machines or team members

Best practices

Start by creating a TODO list with three phases and mark Discovery as in_progress
Ask one question at a time and wait for answers before proceeding
Check the codebase and project docs before asking context questions
Be opinionated: propose a technical approach based on the stack and ask for confirmation
Keep the goal.md to 1–2 pages; if it grows, switch to the full feature process

Example use cases

Create a goal.md to standardize setup scripts across multiple computers
Plan a small migration of config files and services with clear steps and verification
Define requirements and plan for a new utility script that integrates with existing tools
Document a brief infra deploy (e.g., logging or backup service) with tech choices and checklist
Capture a compact plan for a multi-repo change that needs coordination

FAQ

Typically 3–6 questions across the three phases: 2–3 for discovery, 1–2 for technical approach, then confirmation for saving the document.

Where is the goal.md saved by default?

Default path is goals/YYYY-MM-DD-brief-name/goal.md relative to the project root. I will ask if that location doesn’t fit your project.

What if the document grows beyond 2 pages?

That’s a sign to use the full feature process. I’ll recommend splitting into vision, requirements, spec, and plan if more detail is needed.