agentsclimarketplace

Bmad edit prd

Skill mannnrachman/pi-bmad/skills/bmad-edit-prd

BMad Method v6.10.0 packaged for Pi Coding Agent. Global & project-local install, portable defaults, project-scoped outputs, /bmad-init initializer. Retains bmad-investigate.

Install
npx -y skills add mannnrachman/pi-bmad --skill bmad-edit-prd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

DEPRECATED — consolidated into bmad-prd update intent - this skill will be removed in v7 in favor of `bmad-prd`.

SKILL.md

3.0 KB, as published. Nobody here has run it

DEPRECATED — forwards to bmad-prd (update 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-edit-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: python3 {skill-root}/../../runtime/scripts/resolve_customization.py --skill {skill-root} --key workflow. This picks up any {project-root}/_bmad/custom/bmad-edit-prd.toml and bmad-edit-prd.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).

  2. Load the merged output of python3 {skill-root}/../../runtime/scripts/resolve_config.py --project-root {project-root} --key core --key modules.bmm (and config.user.yaml if present) to resolve {user_name} and {communication_language}.

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

    Notice: bmad-edit-prd is deprecated and will be removed in a future release. It now forwards to bmad-prd with update intent. To silence this notice and access the full new customization surface (prd_template, validation_checklist, doc_standards, external_sources, external_handoffs, output_dir, output_folder_name), migrate _bmad/custom/bmad-edit-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: update — 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, validation_report_template, doc_standards, output_dir, output_folder_name, 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, the change signal, etc.).

    bmad-prd takes the workflow from here. Do not execute any further steps in this shim.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.