agentleFS
mategogmategog/dev-team/skills/status/SKILL.md

status

Skill2 starsChanged 7 days agoMITView on GitHub

Show what the dev-team is working on — briefs and their status, what's next, open owner checks, design verdicts, recent decisions, uncommitted changes, and what's waiting on the owner.

188 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

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

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 0

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

    Read, don't change anything.

    line 9
  2. Very specific:

    If company/ doesn't exist, say so and suggest /dev-team:setup.

    line 21

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

/dev-team:status

Read, don't change anything. All paths are relative to the current project's root (the folder this command was run in), never a parent project's company/:

  • company/briefs/*.md (files with no status: frontmatter are notes: skip them) — each brief's status:, next:, repos:, unticked - [ ] lines under Owner checks, and the last line of company/briefs/<slug>/log.md (older briefs: of their inline Progress log).
  • design/**/*-spec.md and *-critique.md — latest verdict per feature.
  • The last 10 lines of company/decisions.md.
  • For each repo in an unfinished brief's repos:: git -C <path> status --short, its branch, and the last 3 commits.

Answer in under 15 lines:

  • Waiting on the owner: waiting-owner and draft briefs (with next:), unanswered open questions, changes needed verdicts, and unticked owner checks — including on done briefs.
  • In progress: approved, building, testing — say they can be resumed with /dev-team:build.
  • Done, parked, stopped (with the reason); superseded briefs as one count.
  • A status outside these: list it as unknown and suggest fixing it.

If company/ doesn't exist, say so and suggest /dev-team:setup.

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.