agentleFS
dgilforddgilford/ai-science-toolkit/skills/pickup/SKILL.md

pickup

Skill82 starsChanged 42 days agoMITView on GitHub

Pick up work from repo-local handoff state. Use when starting a new Claude Code session, switching agents, returning to a project, or asking an AI agent to reconstruct context from prior work. Named `pickup` rather than `resume` to avoid shadowing Claude Code's built-in `/resume` conversation picker.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use discover, adr and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    design

    Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.

    Also in 3 projects that use this

  • GoogleSkill

    diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

    Also in 3 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 5 projects that use this

  • +1 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 28 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for .ai/HANDOFF.md. Two paths:

    line 25

“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Resume this project from the repo-local handoff state.

Current repo state

git status --short 2>/dev/null || echo "(not a git repo)"
git log --oneline -12 2>/dev/null || echo "(no git log)"

Instructions

Check for .ai/HANDOFF.md. Two paths:

If found: Read it, along with CLAUDE.md and AGENTS.md if present. Then verify it against current repo state: confirm the branch matches, check that referenced files exist, and flag any commits more recent than the handoff that aren't reflected in it. If .ai/reviews/ exists, note the most recent review report and surface any of its unresolved findings that bear on the next action.

If not found: Tell the user explicitly that no handoff was found before doing anything else. Then reconstruct best-effort from the repo: scan recent git log, read recently modified files, and check for obvious entry points (scripts, notebooks, configs).

Report

State on the first line whether the handoff was loaded: Handoff loaded from .ai/HANDOFF.md or No handoff found — reconstructed from repo.

Then open with a 2–3 sentence conversational recap — what this project is, what was being worked on, and where things stand. Write it the way a colleague would catch someone up after they've been away, not as a bullet list.

Then follow with only the sections that have real content:

Key decisions — consequential choices already locked in.

Scientific context — datasets, baselines, reference periods, counterfactual definitions, known data quality issues.

Risks — load-bearing assumptions, things likely to go wrong.

Next action — the one concrete thing to do right now. If multiple paths are plausible, compare them in 2–3 lines each and recommend one.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.