agentleFS
mshadmanrahmanmshadmanrahman/claude-for-designers/.claude/skills/wrap-up/SKILL.md

wrap-up

Skill32 starsChanged 49 days agoMITView on GitHub

Saves today's work session as a four-line entry (did, decided, open, next) at the top of the project's log.md, after the student confirms it, so a fresh chat can continue tomorrow with /pick-up. Writes to projects/<client>/log.md or career-vault/log.md, one entry per project touched, never to _new-client. Use when the student says wrap up, done for the day, save my progress, end session, or is about to close the chat.

64 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use new-project, refine and 10 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.
  • zcagSkill

    new-project

    Guide users through creating a new software project from scratch — from raw idea to actionable tasks. Use this skill whenever someone says "new project", "start a project", "create a project", "scaffold a project", "I want to build X", "help me plan a project", "I have an idea for an app/tool/service", or mentions they're starting something new. Also trigger when someone asks for help with project planning, tech stack decisions, MVP scoping, feature planning, or figuring out what to build and how to break it down. When the user describes any project idea and wants to move forward on it, this skill should activate.

    Also in 3 projects that use this

  • AlexPEClubSkill

    refine

    Always use when the user wants to discuss an exsiting feature or specification. Open an existing feature spec to improve, extend, or fundamentally challenge it. Pass the feature ID as argument (e.g. /refine PROJ-2).

    Also in 3 projects that use this

  • MicrosoftSkill

    doctor

    Diagnose an Amplifier CLI environment through the CLI doctor agent. USE WHEN a user requests CLI runtime, settings or missing-capability inspection. DO NOT USE for project bugs or other hosts.

    Also in 4 projects that use this

  • austintgriffithSkill

    orchestration

    Use when a Scaffold-ETH 2 build leaves localhost: planning the launch order, deploying and verifying contracts on a live network, standing up a fork of a real chain to rehearse a deploy, or fixing a contract bug that is already onchain. Not for running the app or a demo against that fork (`/frontend-playbook`).

    Also in 3 projects that use this

  • MicrosoftSkill

    sync

    Sync the current session branch with its upstream branch, or publish the current session branch to a remote. Use when the user asks to sync a branch, pull latest changes, rebase onto upstream, push current branch, publish branch, or set upstream.

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 6 projects that use this

  • +1 more from microsoft

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 59 edited versions we read keep these.

  • 6

    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. Distinctive:

    If the session touched two projects, write one entry into each project's log, each holding only what happened in that project.

    line 19
  2. Very specific:

    If log.md does not exist yet, create it with the header shown in Step 3.

    line 21
  3. Distinctive:

    Do not write straight away.

    line 25
  4. Distinctive:

    If nothing was decided, write "nothing decided".

    line 40
  5. Distinctive:

    When they answer, apply their corrections.

    line 42
  6. Distinctive:

    Keep each line to one or two sentences.

    line 69
  7. Distinctive:

    Do not summarise the session a second time.

    line 79

“Common” is measured: kept by at least 6 in 10 of the 59 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

The student typed /wrap-up. They are done for the day and about to close this chat. Your job is to save what happened in this session so that tomorrow, in a fresh chat, /pick-up can carry on from exactly here.

A new chat remembers nothing from this one. The log is the only thing that carries over, so the four lines you write are all tomorrow's Claude will know.

Step 1. Work out where the entry goes

The log lives beside the work it describes. Never in one shared file at root.

  • Client work goes to projects/<client>/log.md. The client is the folder the session worked in: edubridge, or their own client folder.
  • Career work (Classes 7 and 8, anything in career-vault/) goes to career-vault/log.md.
  • Work on principles/claude-contract.md (Class 2) goes to the log of their project, because Class 2 also writes the project contract and that is where they will look for it.
  • Never write to projects/_new-client/log.md. That folder is an empty template.

If the session touched two projects, write one entry into each project's log, each holding only what happened in that project. One client's notes never land in another client's file.

If log.md does not exist yet, create it with the header shown in Step 3.

Step 2. Propose, then let them correct

Do not write straight away. Draft the entry from the session and show it:

Before I save, check this:

  Did:     ran /grill-me on the brief, finished brief-v3-interrogated.md
  Decided: bKash is its own flow, because the parent leaves the site
  Open:    the client has not said who handles refunds
  Next:    write scope-email.md

Anything wrong or missing?

The Decided line matters most. Write the decision and the reason, in their words where you can. If you are not sure something was a decision, ask rather than guess: the decisions are theirs, and a wrong one saved here gets repeated tomorrow as if it were settled.

If nothing was decided, write "nothing decided". Never invent one.

When they answer, apply their corrections. If they say it is fine, save it.

Step 3. Write the entry

Newest entry at the top, directly under the header, so /pick-up reads the first entry and stops. Never rewrite or delete older entries.

New file header:

# Log

One entry per work session, newest first. `/wrap-up` writes it, `/pick-up` reads it. You never edit this by hand.

Entry format, exactly four lines under a dated heading:

## 2026-10-02, Class 3

- **Did:** ...
- **Decided:** ... because ...
- **Open:** ...
- **Next:** ...

Get today's date from the system, never guess it. Take the class number from the class table in CLAUDE.md; if the work was outside any class, leave the class off the heading.

Keep each line to one or two sentences. This is a note to themselves, not a report. Name real files by path.

Step 4. Close

One line: which file you saved to, and that they can close the chat. Then stop.

Saved to projects/edubridge/log.md. Close this chat whenever you like. Tomorrow, open a new one and type /pick-up.

Do not summarise the session a second time. Do not suggest more work.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.