agentleFS
teslanikateslanika/pm-second-brain/skills/pm-topic/SKILL.md

pm-topic

Skill0 starsChanged 33 days agoMITView on GitHub

Opens, tracks and closes a short-lived topic in topics/. Use when the user says "open a topic", "what's in work", "close the topic", "заведи тему", "что у нас в работе", "закрой тему", or runs /pm-topic.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask why the topic is being opened and how you will know it can be closed.

    line 18
  2. Very specific:

    Add a line to index.md, section "Current work".

    line 38
  3. Very specific:

    Read index.md and every file in topics/ with status: active.

    line 42
  4. Distinctive:

    Ask whether the condition under "What closes it" has been met.

    line 49
  5. Distinctive:

    Write the "How it ended" section and the final Log line.

    line 52
  6. Very specific:

    If anything was left out of scope, name it explicitly.

    line 53
  7. Distinctive:

    Never open a topic without a closing condition.

    line 59
  8. Distinctive:

    Never present a closed topic as current work.

    line 60
  9. Very specific:

    Don't write a long-lived fact into a topic.

    line 62

≈ “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

Topics

A topic is a short thread of work: a launch, an investigation, a disputed question. It has a beginning and an end. That is what separates it from the files in context/, which are never closed.

Open a topic

  1. Ask why the topic is being opened and how you will know it can be closed. Without the second answer, don't create it — otherwise it stays open forever.
  2. Create topics/YYYY-MM-DD-name.md:

    ---
    type: topic
    date: 2026-09-19
    source: calls/2026-09-19-sync.md
    status: active
    ---
  3. Fill in the sections:
    • Why it was opened — with a link to the source.
    • What closes it — a checkable condition.
    • Already decided — links to decisions/.
    • In progress — links to specs/.
    • Open questions — each with an owner.
    • Log — dates and what happened, oldest first.
  4. Add a line to index.md, section "Current work".

Show what is in work

  1. Read index.md and every file in topics/ with status: active.
  2. For each topic show: why it was opened, what closes it, what is still open.
  3. Name the topics whose last Log entry is older than a month. Ask whether they are still alive or ready to close.

Close a topic

  1. Ask whether the condition under "What closes it" has been met.
  2. Don't delete the file. Set status: done and update date to the closing date.
  3. Write the "How it ended" section and the final Log line.
  4. If anything was left out of scope, name it explicitly. Either open a new topic or mark it TBD.
  5. In index.md, move the line from "Current work" to "Closed topics".

Rules

  • Never open a topic without a closing condition.
  • Never present a closed topic as current work.
  • Whatever goes into a topic must cite a source.
  • Don't write a long-lived fact into a topic. It belongs in context/.

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.