followup
Skill0 starsChanged 40 days agoMITView on GitHub
Capture a follow-up into the project's follow-up ledger the moment it surfaces — a deferred item, an accepted limitation, a compromise, or a decision the user may want to revisit. Use when the user says /followup <note>, "note this down", "add a follow-up", "add a followup about that decision, I want to review it later", or when a deferred item / accepted limitation / compromise / surprising constraint is identified mid-task and must not be lost.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- eklavyagoyal/wingmantheir own version, first seen Sep 10, 2026
- Faaz17/Agents-and-Skillstheir own version, first seen Sep 8, 2026
- aksheyw/career-command-center-templatetheir own version, first seen Jul 16, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- aksheyw/career-command-center-template★ 1same name
- Faaz17/Agents-and-Skills★ 1same name
- eklavyagoyal/wingman★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- main-agent/CLAUDE.mdCLAUDE.md
- implementSkill
- impl-planSkill
- milestoneSkill
- sketchSkill
- walkthroughSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Never edit the index by hand: After every entry you create or update, regenerate it from the repo root: pwsh -NoProfile -File …
- Very specific: line 50
origin: when invoked from /impl-plan, /milestone, /implement or /walkthrough, name the plan section, milestone, work package or walkthrough …
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
/followup — capture a ledger entry
Record the note passed as arguments (or, if none, the follow-up just discussed in conversation) in the project's follow-up ledger.
Hard rules
- One file per entry. Entries live in the entry folder (default
docs/fu/) asFU-NNN.mdwith front matter. Agents find entries by grepping that folder — never read the generated index (defaultdocs/follow-ups.md); it exists for the user. - Never edit the index by hand. After every entry you create or update, regenerate it from the repo root:
pwsh -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/fu-index.ps1" -Dir <entry folder> -Out <index path>. - Entries are never deleted or renamed; ids are sequential and stable. Do not commit — the entry rides along with the session's next commit.
Resolve the ledger
- Paths the project CLAUDE.md's documentation workflow declares win.
- Otherwise
docs/fu/exists → that folder, indexdocs/follow-ups.md. - Otherwise
docs/follow-ups.mdexists and does not start with<!-- GENERATED by fu-index→ an unmigrated single-file ledger: stop without recording. Tell the user to runpwsh -NoProfile -File "${CLAUDE_SKILL_DIR}/scripts/fu-migrate.ps1"(one file per entry; the old path becomes the generated index, and its row anchors keep oldfollow-ups.md#fu-nnnlinks working), and repeat the note so it isn't lost. - Otherwise create
docs/fu/and write the first entry; the index appears when you regenerate it.
Steps
- Duplicate check — grep, don't read everything:
grep -il '<keyword>' docs/fu/*.mdfor the note's key terms andgrep -l '^files:.*<path>' docs/fu/*.mdfor the files involved; open only the hits. If the note re-defers or adds evidence to an existing entry, don't create one: append- **Update (YYYY-MM-DD, <source>):** …to its body — for a re-deferral writeRevisit when → <new> — <why>there, set front-matterrevisit:to<new>andstatus:toopen (re-deferred)— then go to step 4. - Next id: the highest
FU-NNNamongdocs/fu/FU-*.mdplus one, three digits (FU-001in an empty folder). Write
docs/fu/FU-NNN.md:--- id: FU-NNN title: <short title, one line> status: open kind: deferred | decision | compromise | limitation areas: [<area>, <area>] files: [<repo path>, <repo folder>] revisit: <milestone id or trigger> origin: <branch>, <YYYY-MM-DD> — <what surfaced it> --- - **What:** <1–3 sentences that stand alone months later, naming the concrete files/types> - **Why accepted:** <required for compromise and limitation> - **Impacts:** <what else it touches, in prose — docs, contracts, other entries>- Front matter is one
key: valueper line, lists as[a, b], no nesting, so it greps cleanly. Leave a field empty (files: [],revisit:) rather than inventing a value. - kind: infer it — "review that later" →
decision; "accept that cost for now" →compromise; "can't do X here" →limitation; "do it in M5" →deferred. Suffix(unconfirmed)when guessed, also on any guessed area. - files: repo paths or folders the entry is about (a folder covers everything under it). This is how a work package finds its entries from the files it owns — fill it whenever the note names code.
- revisit: required for
deferred. A bare milestone id (M5) blocks that milestone from landing until the entry is resolved or re-deferred. - origin: when invoked from
/impl-plan,/milestone,/implementor/walkthrough, name the plan section, milestone, work package or walkthrough point (— M3 refresh,— M4a WP4a.3 (swarm report),— walkthrough 2026-10-01-m2-design #4). - status:
open(optionallyopen (re-deferred),open (needs user),open (partially resolved — M4)) →done (<sha> or PR #N, YYYY-MM-DD)/dropped (<reason>). A resolved entry keeps its file and body as history. - Link other entries as sibling files (
[FU-012](FU-012.md)). Other docs link an entry by relative path to its file — fromdocs/milestones/:../fu/FU-012.md.
- Front matter is one
- Regenerate the index (hard rule above).
- Echo the entry back and ask nothing; if the note was too vague to fill What meaningfully, say what's missing instead of inventing details.
Queries other skills and agents use
grep -l '^status: open' docs/fu/*.md | xargs grep -lE '^files:.*src/Audio' # open entries touching a path
grep -l '^status: open' docs/fu/*.md | xargs grep -liE '^areas:.*\baudio\b' # by area
grep -lE '^revisit: M13\b' docs/fu/*.md # entries that block landing M13
grep -h '^title:' docs/fu/FU-08[0-3].md # titles of known idsDoes 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
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.

