CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bmad-agent-po

Sofia, the Product Owner: turns any input (an idea, brief, PRD, transcript, notes) into a ticket's requirements, slices initiatives into epics and epics into stories, writes and refines tickets, runs the board, validates the tree, replans when a change lands, and sets up the ticket store. Use when the user asks for Sofia or the product owner, or says 'create a spec', 'distill this PRD', 'write the initiative from', 'slice this', 'split this epic', 'break this into stories', 'make a ticket', 'refine this ticket', 'what's ready', 'status of', 'publish', 'validate these tickets', 'this changed, what now', 'set up the ticket store'.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is bmad-retrospective in bmad-code-org/BMAD-METHOD

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary lean dispatcher: a single exact command with explicit placeholder resolution and complete, concrete handling of every outcome (success, HALT, missing setup, uv unavailable). Its only minor limitation is that the command is not literally copy-paste ready due to the two placeholders, though their resolution rules are deterministic. Progressive disclosure is handled well, with details correctly split into the bundle and surfaced by the render script.

DimensionReasoningScore

Conciseness

The 13-line body is lean and assumes Claude's competence: "Run the following command exactly once without changing the current working directory", two one-line placeholder rules, one command, and three bullet rules for outcomes. Every token earns its place with zero padding or explanation of concepts Claude already knows. It is not a 4 because there is nothing that could be trimmed without losing information.

5 / 5

Actionability

The guidance is concrete and near-fully executable — an exact command with explicit, deterministic substitution rules ("Replace `{project-root}` with the nearest folder containing `_bmad/`, from the working directory upward") and complete failure handling for every outcome branch. It is not a 5 because the command is not literally copy-paste ready: the two placeholders require resolution before execution, which constitutes a minor gap; it is well above a 3 because there is no missing step or pseudocode.

4 / 5

Workflow Clarity

For this single-action skill the action is unambiguous (run one command, exactly once, without changing directory) and every outcome has an explicit checkpoint: "`HALT: <reason>`: report the reason and stop", "If the script does not exist... Offer to set it up using `bmad` skill, then run the command again", and "On any other output or failure, including `uv` being unavailable, report the command output and stop". It is not a 4 because the validation/stop conditions and recovery loop are all explicitly present.

5 / 5

Progressive Disclosure

The body is a lean dispatcher while the detail is appropriately split into a real, well-organized bundle — 8 workflow references, 4 asset templates, and 2 scripts (verified to exist, references pointing only one level to scripts, no nested doc chains) — surfaced on demand via "The command prints the skill's workflow: follow it." It is not a 4 because navigation is unambiguous and the split is clean: no inline content that belongs in separate files, no buried or multi-level references.

5 / 5

Total

19

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: it states the skill's capabilities as concrete third-person actions and provides an explicit, comprehensive 'Use when' clause with natural trigger phrases covering the full spec-to-board lifecycle. The only weakness is a handful of overly generic trigger words ('status of', 'publish') that create minor overlap risk with unrelated skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete, distinct actions — "turns any input (an idea, brief, PRD, transcript, notes) into a ticket's requirements, slices initiatives into epics and epics into stories, writes and refines tickets, runs the board, validates the tree, replans when a change lands, and sets up the ticket store" — with comprehensive coverage of the skill's capabilities. It is not a 4 because there are no minor gaps; every core function of the product-owner role is named as a concrete verb phrase.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' is the full list of concrete actions, and the 'when' is an explicit "Use when the user asks for Sofia or the product owner, or says 'create a spec', ..." clause with concrete trigger phrases. It is not a 4 because the 'when' is fully explicit and specific rather than merely adequate.

5 / 5

Trigger Term Quality

Trigger phrases are comprehensive natural-language terms users would actually say: "'create a spec', 'distill this PRD', 'write the initiative from', 'slice this', 'split this epic', 'break this into stories', 'make a ticket', 'refine this ticket', 'what's ready', 'status of', 'publish', 'validate these tickets', 'this changed, what now', 'set up the ticket store", plus "asks for Sofia or the product owner". It is not a 4 because common variations and synonyms (spec/PRD/ticket/epic/story vocabulary, agent name, role name) are all covered.

5 / 5

Distinctiveness Conflict Risk

The skill has a clear niche (product ownership / ticket lifecycle) with distinct vocabulary and a named persona ("Sofia"), but a few triggers — "'status of'", "'publish'", "'this changed, what now'" — are generic enough to overlap with unrelated skills (e.g., deployment status, publishing content or websites). It is not a 5 because those broad phrases carry real conflict risk; it is not a 3 because the domain focus and remaining triggers are unmistakably specific to this skill.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bmad-code-org/BMAD-METHOD

Path

skills/bmad-agent-po/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.