Claude Skill

teamwork-goal

Use when the user explicitly asks to persist until a verifiable result, fix until green, monitor through completion, or stay within a stated budget; do not infer persistence from difficulty.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download jinplu-teamwork-skills_teamwork-goal-8f23dcd.zip · 3 KB

Install

skills CLI npx skills add https://github.com/JinPLu/Teamwork/tree/main/skills/teamwork-goal
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install jinplu-teamwork@llmmart
Git git clone https://github.com/JinPLu/Teamwork.git

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

Skill manifest

Teamwork Goal

Goal adds persistence to the underlying task; it does not add a second workflow.

Method

  1. State the concrete objective, success signal, applicable scope, and any user budget. A success signal is the directly observable result that shows the requested outcome is achieved. Example: the authorized command or user-stated completion condition is observed on the real path.
  2. Perform the next useful action and observe the result.
  3. Continue until the success signal is directly observed, the user interrupts, or a genuine external blocker prevents further progress.
  4. Change approach when evidence invalidates the current one. Do not repeat a failed action without a new reason.
  5. Report success with the observed evidence, or report the exact blocker and what would unblock it.

Carry compact Invariants through every retry: the original objective, protected constraints, and stop or budget state. After each attempt, keep an Attempt Record with the previous result, the new reason to continue or stop, and the current stop or budget state. These records live in the working context and, when a checkpoint fires, in the report; they are not a workflow database.

Tests support the goal but do not replace the real success signal when that signal is available.

Persistence

When a listed checkpoint fires, write in the same response cycle. If separate stable identities each cross a checkpoint, write each to its own path.

Cross-chat memory lives in one Markdown document from references/report.md at docs/teamwork/reports/<slug>.md. Same identity means the same continuing objective; reuse that path and name the document you read. A different subject gets a new path.

Experiment checkpoints write from references/experiment-record.md at docs/teamwork/experiments/<slug>.md. Same identity means the same falsifiable claim; reuse that path and name the document you read. A different claim gets a new path. Probe declarations need only a claim draft, kill criterion, and budget. The full declaration is for main-table or appendix-hygiene eligibility, not a run gate. Slot criteria are in ../teamwork-collaborate/references/experiment.md. Post-run HARKing is the diff between the frozen declared claim and a post-hoc claim; Reviewer or Challenger is the right role for that adjudication, and it is not a mandatory ceremony.

Checkpoints: the success signal is directly observed; a genuine external blocker stops progress; or the user interrupts after material progress worth reusing. An experiment declaration, adjudication, result, or tombstone is also a checkpoint.

Files (teamwork)
  • agents
    • openai.yaml 216 B
      Loading…
  • references
    • experiment-record.md 2.5 KB
      Loading…
    • report.md 1.1 KB
      Loading…
  • SKILL.md 2.8 KB
    ---
    name: teamwork-goal
    description: Use when the user explicitly asks to persist until a verifiable result, fix until green, monitor through completion, or stay within a stated budget; do not infer persistence from difficulty.
    ---
    
    # Teamwork Goal
    
    Goal adds persistence to the underlying task; it does not add a second workflow.
    
    ## Method
    
    1. State the concrete objective, success signal, applicable scope, and any user
       budget. A success signal is the directly observable result that shows the
       requested outcome is achieved. Example: the authorized command or user-stated
       completion condition is observed on the real path.
    2. Perform the next useful action and observe the result.
    3. Continue until the success signal is directly observed, the user interrupts,
       or a genuine external blocker prevents further progress.
    4. Change approach when evidence invalidates the current one. Do not repeat a
       failed action without a new reason.
    5. Report success with the observed evidence, or report the exact blocker and
       what would unblock it.
    
    Carry compact Invariants through every retry: the original objective, protected
    constraints, and stop or budget state. After each attempt, keep an Attempt
    Record with the previous result, the new reason to continue or stop, and the
    current stop or budget state. These records live in the working context and,
    when a checkpoint fires, in the report; they are not a workflow database.
    
    Tests support the goal but do not replace the real success signal when that
    signal is available.
    
    ## Persistence
    
    When a listed checkpoint fires, write in the same response cycle. If separate
    stable identities each cross a checkpoint, write each to its own path.
    
    Cross-chat memory lives in one Markdown document from `references/report.md`
    at `docs/teamwork/reports/<slug>.md`. Same identity means the same
    continuing objective; reuse that path and name the document you read. A
    different subject gets a new path.
    
    Experiment checkpoints write from `references/experiment-record.md` at
    `docs/teamwork/experiments/<slug>.md`. Same identity means the same
    falsifiable claim; reuse that path and name the document you read. A
    different claim gets a new path. Probe declarations need only a claim draft,
    kill criterion, and budget. The full declaration is for main-table or
    appendix-hygiene eligibility, not a run gate. Slot criteria are in
    `../teamwork-collaborate/references/experiment.md`. Post-run HARKing is the
    diff between the frozen declared claim and a post-hoc claim; Reviewer or
    Challenger is the right role for that adjudication, and it is not a
    mandatory ceremony.
    
    Checkpoints: the success signal is directly observed; a genuine external
    blocker stops progress; or the user interrupts after material progress worth
    reusing. An experiment declaration, adjudication, result, or tombstone is
    also a checkpoint.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.