bmad-prd Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• Low GitHub adoption signal
• SKILL.md instructs running repository scripts via `uv run` and loading files via glob patterns, which assumes the skill is run within a trusted repository context. If the repository is untrusted, this could execute arbitrary code or read unintended files.
• Financial research output is not financial advice; require human review before any live investment decision
• The skill references an org-configured `external_sources` registry and headless `external_handoffs` with tools like Confluence upload. These are configurable injection/sensitive data exfiltration surfaces if not carefully guarded.