add, remove, list

agileflow add

Copyagileflow add diagnosing-bugs            # official skill (@agileflow/diagnosing-bugs)
agileflow add diagnosing-bugs@^1         # with a version range
agileflow add @agileflow/github          # a pack: adds each skill in it
agileflow add git+https://github.com/example/skills.git#skills/release-notes
agileflow add ./skills/my-release-flow   # a local directory
agileflow add                            # interactive: pick from the registry catalog

Options:

Before installing, add shows what the skill contains: source, version, activation, reference files, executable scripts (listed by name), and requirements such as gh on PATH or network access. Third-party content is labeled "Installing external skill" with "Review source before installing untrusted skills." Scripts are never executed during installation.

Registry skills get a caret range on the installed version by default (for example ^1.0.1; ~0.3.2 for a 0.x version), so a new major version is never installed without you changing the range. Skills added from a pack use the pack's ranges (^1).

add creates agileflow.yaml if the project does not have one yet. A skill that is already installed is left as is (use agileflow update <skill> for a newer version). Without a TTY, add needs at least one target.

add refuses to overwrite a directory in .agents/skills that AgileFlow does not manage. See Skill sources for git and local skills.

agileflow remove

Copyagileflow remove babysitting-pr
agileflow remove babysitting-pr --force   # discard local modifications
agileflow remove --all                    # stop using AgileFlow here

remove deletes only what the lockfile says AgileFlow owns: .agents/skills/<skill> and the Claude Code link or mirror it created. Skills AgileFlow does not manage are never touched, whatever their name.

• A modified managed skill is not removed without --force (or agileflow fork first to keep your changes).
• A locally owned skill (a fork or a skill you registered from .agents/skills) is removed from agileflow.yaml and agileflow.lock, but its files are kept.

Removing AgileFlow from a project

agileflow remove --all (same as agileflow migrate --detach) removes agileflow.yaml and agileflow.lock. It asks whether to keep installed skills as standalone Agent Skills (without a TTY, or with --yes, it keeps them). The default is yes: the managed notice is removed, Claude Code links stay, and every provider keeps seeing the skills. --delete-skills deletes unmodified AgileFlow skills instead; modified and locally owned skills are kept.

agileflow list

Copyagileflow list           # project and personal skills, plus providers
agileflow list --global  # personal skills only
agileflow list --json

CopyProject skills
  NAME                       VERSION  MODE    SOURCE                              STATUS
  diagnosing-bugs            1.0.1    auto    official                            clean
  interviewing-requirements  1.0.1    manual  official                            clean
  filing-pr                  local    auto    fork of @agileflow/filing-pr@1.1.0  local
  release-notes              local    auto    local                               clean
  Not managed by AgileFlow (left untouched): my-team-release
 
Providers
  Codex     native .agents/skills
  Claude    linked .claude/skills
  Cursor    native .agents/skills (not detected)
  OpenCode  native .agents/skills (not detected)
  Gemini    native .agents/skills

Source is official (@agileflow/...), registry (another scope), git, local, or fork of <package>@<version>. Status is one of clean, modified, missing, local (locally owned), disabled, or not locked (in agileflow.yaml but not yet in the lockfile; run agileflow update). A provider turned off with agileflow configure provider <id> off shows as "disabled in config".