Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"
65
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./src/bmm-skills/4-implementation/bmad-sprint-planning/SKILL.mdSecurity
2 findings: 1 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
The workflow executes arbitrary activation steps and a configurable on_complete instruction from merged customization files and can load arbitrary files under the project root, creating a high-risk remote code execution/data-exfiltration vector if those configuration sources are untrusted.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill explicitly instructs the agent to load config and persistent files (including personal override files) and then write resolved config fields—such as project_key and other config values—into the generated sprint-status.yaml, which forces the LLM to emit any sensitive values verbatim if present.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Yes: the required workflow loads outsider-authored markdown epic files from `{planning_artifacts}/*epic*.md` (or sharded equivalents) as readable prose at runtime to “extract all work items,” which then becomes LLM context (indirect prompt-injection risk via arbitrary user content in epic files).
bb45db4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.