Claude Skill

finish-work

Close a substantive task with the right checks for its kind of work, an honest outcome summary and a written receipt. Use when a task is about to be called done, at a meaningful checkpoint, when work stops partial or blocked, or when someone says finish this, close this out, wrap

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download lennoxsaint-skills-finish-work-aa32aee.zip · 12 KB

Install

skills CLI npx skills add https://github.com/lennoxsaint/Skills/tree/main/finish-work
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install lennoxsaint-skills@llmmart
Git git clone https://github.com/lennoxsaint/Skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole lennoxsaint/skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Finish Work

Finish the requested outcome, verify its proof, and record the actual result. Follow the project's own verification rules and required checks first. Reuse checks already completed in this task.

Read only the relevant closeout guidance:

  • Research, advice or document-only work: research.md.
  • Code or executable configuration changes: code.md.
  • User-visible interface changes: also ui.md.
  • An authorized release or external change: also release.md.
  • Every substantive closeout or checkpoint: receipt.md.

For overlapping work, use the relevant combination. Do not load every reference by default. A research task does not require code tests; a local code task does not imply deployment.

Proof

  • Match the evidence to the change: inspect the text for a copy-only edit; exercise the real workflow for a behavior change.
  • Keep proof states apart. Local, visible, staged, scheduled, published and delivered are different claims. For anything outside this machine, use the provider's or runtime's own readback.
  • Review the final diff or artifact for regressions and unmet requirements. Investigate relevant warnings and silent failures.
  • After two failed attempts at the same fix, stop patching. Write down what you learned, then retry from a clean brief or change approach from fresh evidence.

Continue through routine authorized fixes until the agreed outcome and relevant checks are complete. If essential access, intent or authority is missing, prepare everything independent of it and name the remaining step. Preserve source truth. A passing check, saved configuration or draft is evidence only for that step.

Close

Close with the outcome, material verification limits, remaining work if any, and the receipt's real state and path. Keep routine tool details in the receipt. Report complete only when the owned scope and its evidence are finished; name remaining work and unavailable verification honestly.

Files (skills)
  • agents
    • openai.yaml 315 B
      Loading…
  • references
    • code.md 1.2 KB
      Loading…
    • receipt.md 2.5 KB
      Loading…
    • release.md 1.1 KB
      Loading…
    • research.md 704 B
      Loading…
    • ui.md 694 B
      Loading…
  • scripts
    • log_receipt.py 8.3 KB
      Loading…
    • test_log_receipt.py 18.7 KB
      Loading…
  • SKILL.md 2.4 KB
    ---
    name: finish-work
    description: Close a substantive task with the right checks for its kind of work, an honest outcome summary and a written receipt. Use when a task is about to be called done, at a meaningful checkpoint, when work stops partial or blocked, or when someone says finish this, close this out, wrap this up, or asks whether it is really done.
    ---
    
    # Finish Work
    
    Finish the requested outcome, verify its proof, and record the actual result. Follow the project's own verification rules and required checks first. Reuse checks already completed in this task.
    
    Read only the relevant closeout guidance:
    
    - Research, advice or document-only work: [research.md](references/research.md).
    - Code or executable configuration changes: [code.md](references/code.md).
    - User-visible interface changes: also [ui.md](references/ui.md).
    - An authorized release or external change: also [release.md](references/release.md).
    - Every substantive closeout or checkpoint: [receipt.md](references/receipt.md).
    
    For overlapping work, use the relevant combination. Do not load every reference by default. A research task does not require code tests; a local code task does not imply deployment.
    
    ## Proof
    
    - Match the evidence to the change: inspect the text for a copy-only edit; exercise the real workflow for a behavior change.
    - Keep proof states apart. Local, visible, staged, scheduled, published and delivered are different claims. For anything outside this machine, use the provider's or runtime's own readback.
    - Review the final diff or artifact for regressions and unmet requirements. Investigate relevant warnings and silent failures.
    - After two failed attempts at the same fix, stop patching. Write down what you learned, then retry from a clean brief or change approach from fresh evidence.
    
    Continue through routine authorized fixes until the agreed outcome and relevant checks are complete. If essential access, intent or authority is missing, prepare everything independent of it and name the remaining step. Preserve source truth. A passing check, saved configuration or draft is evidence only for that step.
    
    ## Close
    
    Close with the outcome, material verification limits, remaining work if any, and the receipt's real state and path. Keep routine tool details in the receipt. Report complete only when the owned scope and its evidence are finished; name remaining work and unavailable verification honestly.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.