agentleFS
Sign inStart free
venus2099venus2099/codex-game-studios/.agents/skills/scope-check/SKILL.md

scope-check

Skill1 starsChanged 27 days agoMITView on GitHub

Scope creep check — current scope versus the original plan. Flags additions, quantifies bloat, recommends cuts. 'Any scope creep?'

26 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 0

    Distinctive

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

    If it comes back with a question for the user, ask it in chat, wait, and finish the skill yourself with the answer.

    line 19
  2. Very specific:

    Read .claude/skills/scope-check/SKILL.md in full before doing anything else.

    line 23
  3. Very specific:

    If it has lines starting with ` !

    line 24
  4. Very specific:

    Follow the skill exactly, translating Claude Code vocabulary with the "Codex compatibility" table in AGENTS.md.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 21 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
<!-- Generated by codex-port/convert_to_codex.py; edits here are overwritten. -->

scope-check

Arguments: [feature-name or sprint-N] (take them from the user's message).

This is the Codex entry point for the upstream skill .claude/skills/scope-check/SKILL.md, which stays the single source of truth.

Model tier: light (gpt-6-luna). Unless you are ccgs-light-runner yourself, or the user asked you to run it directly, delegate: spawn the custom agent ccgs-light-runner with the skill name scope-check, the user's arguments and any approvals the user has already given, then relay its result. If it comes back with a question for the user, ask it in chat, wait, and finish the skill yourself with the answer. ccgs-light-runner skips this paragraph and runs the steps below.

  1. Read .claude/skills/scope-check/SKILL.md in full before doing anything else.
  2. If it has lines starting with !`, they are startup commands. Run each one from the repository root with ${CLAUDE_SKILL_DIR} = .claude/skills/scope-check and treat the output as the config block the skill says is "resolved above".
  3. Follow the skill exactly, translating Claude Code vocabulary with the "Codex compatibility" table in AGENTS.md. In particular, every AskUserQuestion means: ask in chat with numbered options, then stop and wait for the user's reply.

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