agentleFS
Sign inStart free
legibetlegibet/agent-skills/skills/topic/SKILL.md

topic

Skill0 starsChanged 26 days agoMITView on GitHub

Document-driven workflow for deferred work: capture and explore an idea or issue, distill it into an implementation plan, then execute. Use when the user wants to record an idea or issue for later, resume a topic, write a plan.md, or implement an existing plan document.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. schuhmica05-sketch/topic★ 1same 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 repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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
  1. Very specific:

    Read the kickoff document's status and load the reference for that stage:

    line 27
  2. Very specific:

    Keep working documents out of git history.

    line 38
  3. Distinctive:

    Keep documents organized at all times.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Topic

This skill is a document-driven workflow for deferred work: things worth doing later. Capture them so they survive, shape them into plans, execute them when the time comes. Immediate fixes go straight to execution.

Routing

Start a topic

In a mature project, create a folder for the topic at .agents/topics/<topic>/. In a new project, put the documents directly in the project root, as the topic is the project itself. A user-specified path wins. Create the kickoff document, classified as one of:

  • idea: something new should exist (feature, project, direction)
  • issue: something is wrong (bug, UX, architecture)

Then read references/idea.md or references/issue.md accordingly. If a topic fits both, pick either; the lifecycle is the same.

Resume a topic

Read the kickoff document's status and load the reference for that stage:

  • idea or issue: references/idea.md or references/issue.md
  • plan: references/plan.md
  • implementing: references/implementation.md
  • dropped: the topic is closed

Documents

Each topic has a kickoff document (idea.md or issue.md), a plan.md when needed, and any supporting files (research notes, demo scripts). Reference supporting files from the kickoff document.

  • Keep working documents out of git history; promote lasting ones into docs/.

  • The kickoff document records the topic's stage and last update in its frontmatter:

    ---
status: idea
updated: 2026-08-09
---

    The stage moves forward: idea/issue → plan → implementing → done. Simple topics skip the plan and go straight from idea/issue to done. A topic given up on ends as dropped.

Working rules

  • Record facts and first thoughts directly. Bring judgments and decisions to the user first.
  • Keep documents organized at all times. Prefer precise edits over rewrites.
  • Documents are working notes, not permanent rules. When one is wrong or outgrown, fix it. Changing what a document says goes through the user: propose the change, then edit once approved.
  • The user decides when a stage ends; update the status when a new stage starts.
  • Simple tasks skip the plan: once the direction converges, go straight to execution.

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.

Check your setup, free