agentleFS
Sign inStart free
iadr-deviadr-dev/greenlight/skills/status/SKILL.md

status

Skill2 starsChanged 5 days agoMITView on GitHub

Show where every greenlight feature stands, what each is waiting for, and anything that needs attention. Use when the user runs /greenlight:status or asks what is in progress, blocked, or waiting for approval.

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 1

    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
  1. Distinctive:

    Run, and show the output unchanged:

    line 11
  2. Very specific:

    If the arguments name a feature ($ARGUMENTS), also run bdd state show FEAT-n and bdd trace FEAT-n.

    line 17
  3. Very specific:

    Do not change anything. Offer /greenlight:feature FEAT-n to continue a feature, or /greenlight:change if an approved item has to change.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 146 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

greenlight status

Everything here is computed by the tool; do not infer state from the conversation.

  1. Run, and show the output unchanged:

    "${CLAUDE_PLUGIN_ROOT}/tools/bdd/bdd" status

    If the arguments name a feature ($ARGUMENTS), also run bdd state show FEAT-n and bdd trace FEAT-n.

  2. Then say in a few lines, in plain words:
    • which feature needs the person next, and the exact line to type if it is waiting for an approval (/greenlight:approve FEAT-n rules or examples);
    • anything blocked: a failed gate, an approval marked "not valid" (changed after approval or revoked by a change), an open integrity violation and which file it names;
    • anything unreviewed (autopilot) or soft (hooks were not active), and why.
  3. Do not change anything. Offer /greenlight:feature FEAT-n to continue a feature, or /greenlight:change if an approved item has to change.

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