agentleFS
Sign inStart free
tikocitikoci/rosetta/.github/skills/promote-idea/SKILL.md

promote-idea

Skill54 starsChanged 4 months agoMITView on GitHub

Promote an Inbox bullet from BACKLOG.md to either a GitHub issue (work commitment) or a briefing (briefings/B-NNNN-*.md, research/decision support). Asks which based on whether the work is committed or still needs thinking. Removes the original bullet.

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. bitwize-music-studio/claude-ai-music-skills★ 589same 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 repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a discussion that resolves what an idea actually means.

    line 15
  2. Very specific:

    List Inbox bullets: if no argument supplied. Read BACKLOG.md, find the ## Inbox section, present the bullets numbered.

    line 25
  3. Distinctive:

    Decide: issue or briefing?: Ask the user explicitly:

    line 30
  4. Very specific:

    If issue: create it with gh issue create, using the work-item template's sections (context/grounding, acceptance sketch, V-* validation …

    line 39
  5. Very specific:

    Create tasks/T-*.md files — that queue is a frozen archive (see tasks/README.md).

    line 66

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

Promote Idea

Move a one-line Inbox bullet from BACKLOG.md to a real, structured location: a GitHub issue (codebase work) or a briefing (research/decision support).

When to use

  • An Inbox bullet has gained enough shape to either commit to or think through systematically.
  • After a discussion that resolves what an idea actually means.

When NOT to use

  • The bullet is still vague — leave it in Inbox until it has shape.
  • The bullet is one-shot ("merge this dependabot PR") — just do it; don't promote.
  • It's a wait-on-trigger item — move it to the BACKLOG.md Triggers section instead.

Procedure

  1. List Inbox bullets if no argument supplied. Read BACKLOG.md, find the ## Inbox section, present the bullets numbered.
  2. Pick the bullet. Match the substring argument, or ask the user which number.
  3. Decide: issue or briefing? Ask the user explicitly:
    • issue — "This is codebase work we intend to do." Discussion can continue on the issue; it only gets the agent-ready label once acceptance criteria are settled.
    • briefing — "I want to think this through, ground claims with code/data, possibly arrive at a decision. The conclusion might be 'no work needed' and that's fine."
    • delete — "This doesn't survive a re-read. Remove it."
    • trigger — "This is waiting on a specific external event." → move to the Triggers table instead.
  4. If issue: create it with gh issue create, using the work-item template's sections (context/grounding, acceptance sketch, V-* validation rows from VALIDATION.md, related briefings/issues). Only add the agent-ready label if the spec is genuinely settled — the default is an unlabeled discussion issue. If it belongs to an umbrella theme, mention the umbrella in the body and add it to the umbrella's child checklist.
  5. If briefing: find the next free B-NNNN ID across briefings/B-*.md, generate a kebab-case slug, ask for topic (one line) and an opening question for the body, and write briefings/B-NNNN-<slug>.md with status: open, last_revisited = today. Add it to the Briefings index in BACKLOG.md.
  6. Remove the bullet from BACKLOG.md Inbox.

Output format

Confirm to the user:

Promoted "<bullet>" → issue #34 (discussion; not yet agent-ready)
Removed from BACKLOG.md Inbox.

What this skill does NOT do

  • Pick or work on the issue — that's pick-next-task and human/agent effort.
  • Promote a Triggers row — Triggers stay until their condition fires; then the same flow opens an issue.
  • Create tasks/T-*.md files — that queue is a frozen archive (see tasks/README.md).

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