agentleFS
Sign inStart free
PaulKnauerPaulKnauer/sonos-mcp-server/.agents/skills/bmad-validate-prd/SKILL.md

bmad-validate-prd

Skill1 starsChanged 15 days agoApache-2.0View on GitHub

Deprecated — forwards to bmad-prd (validate intent)

20 other projects use a version of this, 11 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 0

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

    Run uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} and resolve {user_name} and …

    line 16

“Common” is measured: kept by at least 6 in 10 of the 9 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 — forwards to bmad-prd (validate intent)

This skill was consolidated into bmad-prd. It is retained as a thin compatibility shim so existing invocations by name and _bmad/custom/bmad-validate-prd.toml override files keep working. New work should invoke bmad-prd directly — it detects create / update / validate intent from the conversation.

On Activation

  1. Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow. This picks up any {project-root}/_bmad/custom/bmad-validate-prd.toml and bmad-validate-prd.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).
  2. Run uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} and resolve {user_name} and {communication_language}.

  3. Emit a deprecation notice to the user in {communication_language}:

    Notice: bmad-validate-prd is deprecated and will be removed in a future release. It now forwards to bmad-prd with validate intent. To silence this notice and access the full new customization surface (prd_template, validation_checklist_template, validation_report_template, doc_standards, finalize_reviewers, external_sources, external_handoffs, prd_output_path, run_folder_pattern), migrate _bmad/custom/bmad-validate-prd.toml to _bmad/custom/bmad-prd.toml and invoke bmad-prd directly next time. Customization fields that were in this version still remain in the new version and will be respected if present in _bmad/custom/bmad-prd.toml, but the new version also supports additional fields that you can take advantage of by migrating.

  4. Invoke bmad-prd with the following context. Pass these as the activating context so bmad-prd honors them instead of resolving its own customization from scratch:

    • Intent: validate — skip bmad-prd's usual intent detection step.
    • Pre-resolved legacy customization — use these in place of resolving from bmad-prd's own customize.toml for the four legacy fields. For everything else (prd_template, validation_checklist_template, validation_report_template, doc_standards, finalize_reviewers, prd_output_path, run_folder_pattern, external_sources, external_handoffs), use bmad-prd's own defaults and overrides as normal:
      • activation_steps_prepend = the resolved value from step 1
      • activation_steps_append = the resolved value from step 1
      • persistent_facts = the resolved value from step 1
      • on_complete = the resolved value from step 1
    • Original user input: forward whatever the user said when invoking this skill verbatim (the target PRD path, etc.).

    bmad-prd takes the workflow from here. Do not execute any 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