agentleFS
Sign inStart free
Slava-codeSlava-code/slava-stack/.claude/skills/kb-promote/SKILL.md

kb-promote

Skill0 starsChanged 29 days agoMITView on GitHub

Move content along questions → research-dispatches → decisions → synthesis with backlinks and supersede stamps. Use when the user says: promote this question, formalize as a decision, make this a dispatch.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read source file; determine current stage by its folder.

    line 11
  2. Very specific:

    No move. A decision becomes a citation in the next /kb-synthesize <product> run.

    line 31

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

/kb-promote <source-path>

Usage: /kb-promote questions/2026-04-17-example-slug.md.

  1. Acquire runs/.lock.
  2. Read source file; determine current stage by its folder.
  3. Dispatch per the promotion path:

question → research-dispatch

  • Copy source content into schema/templates/research-dispatch.md structure.
  • Carry the question text as the Hypothesis; bring context into "Prior constraints."
  • Target file: research-dispatches/YYYY-MM-DD-<slug>.md. Date = today.
  • Mark source question: status: incorporated, add supersedes: line pointing at the new dispatch (note: this is a reverse direction from the normal supersedes:; or alternatively, delete the question — user's preference; default to deletion since questions are lightweight).
  • Commit: question: promote <slug> → research-dispatches/<slug>.

research-dispatch → decision

  • Extract the Recommendation section into a new decisions/YYYY-MM-DD-<decision-slug>.md using schema/templates/decision.md.
  • Required sections: ## Why, ## What we're giving up.
  • Dispatch file stays (history is the point). Update its frontmatter: status: incorporated. Add a pointer to the resulting decision at the end of the dispatch.
  • Commit: research: promote <slug> → decisions/<slug>.

decision → synthesis

  • No move. A decision becomes a citation in the next /kb-synthesize <product> run. Suggest /kb-synthesize to user.
  1. Regenerate INDEXes: python3 scripts/rebuild-indexes.py. Source + destination folder INDEX.md files update automatically. Stage all modified INDEX.md files.
  2. Push. Release the lock.

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