Skip to content
Skills Library
AI & agents · Building & coding

goal-execution

/goal-execution

Complete a bounded implementation goal in the current agent run, with explicit finish criteria and evidence-based verification. Use for requests that should continue through implementation and checks instead of stopping after a plan.

Repository
monofield ↗
Licence
Apache-2.0
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Complete a bounded implementation goal in the current agent run, with explicit finish criteria and evidence-based verification. Use for requests that should continue through implementation and checks instead of stopping after a plan.

Original author description

Complete a bounded implementation goal in the current agent run, with explicit finish criteria and evidence-based verification. Use for requests that should continue through implementation and checks instead of stopping after a plan.

How it works

  1. Establish the finish line
  2. Execution loop
  3. Safety boundary
  4. Completion report
Original SKILL.md headings · 62 lines, 402 words
SKILL.md preview
---
name: goal-execution
en_name: "Goal execution"
ko_name: "목표 실행"
description: |
  Complete a bounded implementation goal in the current agent run, with explicit finish criteria and evidence-based verification. Use for requests that should continue through implementation and checks instead of stopping after a plan.
en_description: |
  Complete a bounded implementation goal in the current agent run, with explicit finish criteria and evidence-based verification.
ko_description: |
  현재 Agent 실행 안에서 명확한 완료 조건을 세우고 구현과 검증까지 끝내는 목표 실행 워크플로입니다.
triggers:
  - "finish this goal"
  - "keep going until done"
  - "implement and verify"
  - "끝까지 구현"
  - "완료할 때까지"
od:
  mode: prototype
  surface: web
  platform: desktop
  scenario: engineering
  category: engineering
  preview:
    type: markdown
  design_system:
    requires: false
---

# Goal execution

Use this skill for one bounded goal that should end in a verified result, not
only a plan or progress update. It applies to the current agent run. It is not
a background scheduler and does not create a third chat mode.

## Establish the finish line

Before changing anything, derive a compact goal contract from the user's
request and the selected project context:

- **Objective:** the concrete outcome to deliver.
- **Completion criteria:** observable checks that prove the outcome is done.
- **Constraints:** scope, compatibility, quality, security, and performance
  requirements already stated by the user or repository instructions.
- **Verification:** the smallest reliable test, build, inspection, or runtime
  check that covers the changed behavior.

Do this internally when the request is already clear. Ask the user only when a
missing choice would materially change the result or when new authority is
required.

## Execution loop

1. Inspect only the relevant project evidence and current state.
2. Make a short plan tied directly to the completion criteria.
3. Implement the next useful change.
4. Run proportional verification and inspect its actual output.
5. Compare the result with every completion criterion.
6. If a criterion is unmet and a safe in-scope fix is available, iterate.
7. Finish only when all required criteria pass or a genuine blocker remains.

Keep the loop efficient: reuse already-read context, avoid broad rescans and
duplicate commands, and do not inflate the prompt with unrelated files or
resource catalogs.

## Safety boundary

Selecting this skill never expands authority. Continue to obey repository,
sandbox, approval, credential, and external-system policies. In particular:

- do not perform destructive, production, publishing, messaging, purchasing,
  or credential-changing actions unless the user already authorized them;
- stop for a required approval or material product decision instead of
  guessing;
- do not weaken tests, security controls, or acceptance criteria merely to
  claim completion;
- report an unavailable external dependency or exhausted safe retry path as a
  blocker, with the completed evidence preserved.

## Completion report

At the end, state the delivered outcome first, then the verification evidence
and any remaining limitation. Never report the goal as complete when a required
criterion was skipped, failed, or could not be observed.

For work that must run again later, on a schedule, or after the current app
session ends, create an Automation instead. Automations provide durable
scheduled execution; this skill provides completion discipline inside the
current run.

Versions

The database has no other skills named goal-execution.

Database snapshot: 13.11.2026 · package version c5f690b7a4ff (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100craft-goal
    Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: asked to craft or lint a goal (a /goal prompt); one change goes to Plan.
  • 90guided-goal
    Turn a rough objective into a bounded, verifiable completion contract, confirm it, then execute it with a finite attempt cap. Use when the user wants autonomous work but the outcome, proof, scope, or stopping point is still vague.
  • 100goal
    Use when the user says 'goal', 'set a goal', 'define the goal', 'plan this properly', or starts a task that needs a clear finish line and verification. Structures work into TASK / WHY / OUTCOME / CONSTRAINTS / VERIFICATION before execution begins.
  • 100goal
    Persistent project goal that survives across sessions and tools, with continuous-execution loop semantics. Use when someone asks to "set a goal", "what is my goal", "goal status", "keep working on X until done", "resume the goal", or wants work to continue across sessions until…
  • 100qiaomu-goal-meta-skill
    Turn vague or complex Codex tasks into strong `/goal` commands with outcome, verification, constraints, boundaries, iteration policy, completion evidence, and pause/block conditions. Use when the user asks for Codex goal instructions, Goal 指令, 目标指令, `/goal` prompts, 中文 Goal 模板,…
  • 100cds-create-goal
    Use when the user wants to turn a rough goal into a verifiable goal with an explicit definition of done - ready to run directly via /goal on Claude Code or Codex, or pasted as a prompt. Type /cds-create-goal to use.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.