agentleFS
Sign inStart free
MysterionRiseMysterionRise/forgetest/.agents/skills/bmad-quick-dev/SKILL.md

bmad-quick-dev

Skill4 starsChanged 31 days agoMITView on GitHub

Deprecated: forwards to bmad-build. Do not use unless invoked by name.

20 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use bmad-agent-tech-writer and bmad-agent-qa.

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.
  • DogaOztuzunSkill

    bmad-agent-tech-writer

    Technical documentation specialist and knowledge curator. Use when the user asks to talk to Paige or requests the tech writer.

    Also in 13 projects that use this

  • DogaOztuzunSkill

    bmad-agent-qa

    QA engineer for test automation and coverage. Use when the user asks to talk to Quinn or requests the QA engineer.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether either legacy customization file exists:

    line 10
  2. Very specific:

    If neither legacy file exists, output exactly bmad-quick-dev is deprecated.

    line 13
  3. Distinctive:

    After every detected legacy file has been migrated successfully and no legacy file remains, output exactly

    line 19

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

Deprecated Build Alias

On Activation

  1. Check whether either legacy customization file exists:
    • {project-root}/_bmad/custom/bmad-quick-dev.toml
    • {project-root}/_bmad/custom/bmad-quick-dev.user.toml
  2. If neither legacy file exists, output exactly bmad-quick-dev is deprecated. Redirecting to bmad-build. Please use bmad-build in the future., invoke bmad-build exactly once with the user's original input verbatim, then execute no further steps in this shim.
  3. For every legacy file that exists, use its matching new filename:
    • {project-root}/_bmad/custom/bmad-quick-dev.toml becomes {project-root}/_bmad/custom/bmad-build.toml.
    • {project-root}/_bmad/custom/bmad-quick-dev.user.toml becomes {project-root}/_bmad/custom/bmad-build.user.toml.
  4. If the matching new file does not exist, tell the user that the customization file uses the deprecated name and offer to rename it. Rename it only after explicit approval. If approval is declined or unavailable, or the rename fails, HALT and do not invoke any skill.
  5. If the matching new file already exists, do not overwrite it. Read both files, explain their differences, and propose the exact content for the new file. Resolve conflicting values with the user. Only after the user explicitly approves that content, save and verify the new file, then remove the legacy file. If approval is declined or unavailable, or any operation fails, HALT and do not invoke any skill.
  6. After every detected legacy file has been migrated successfully and no legacy file remains, output exactly bmad-quick-dev is deprecated. Redirecting to bmad-build. Please use bmad-build in the future., invoke bmad-build exactly once with the user's original input verbatim, then execute no further steps in this shim.

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