Skip to content

Proposal: add bold-claim and claim-review skills to pm-marketing-growth #51

Description

@brainsparker

Hi Paweł — following the contributing guidelines ("new skills → open an issue first"), I'd like to propose adding two skills to pm-marketing-growth. Both are skills I built and use in my own work; source is in brainsparker/skills.

Proposed skills

bold-claim (positioning)

Finds the single contested sentence that drives a product's GTM motion — a claim a competitor would push back on, not a tagline. The skill researches the competitive landscape, generates 5–7 claim candidates across six archetypes (category, antagonist, reframe, etc.), scores them against a 25-point sharpness rubric, and produces a messaging doc anchored on the winning claim (the claim, the antagonist, proof points, timing, one-liners).

Source: skills/bold-claim/SKILL.md

claim-review (alignment review)

A PM-lens review of a PR, spec, or shipped feature: does what this actually does match what we claimed it does? Scores against five dimensions (claim-aligned, surface-honest, felt-value, scope-honest, voice-aligned) and names concrete gaps with quoted lines. It composes with bold-claim — if a bold-claim doc exists, it becomes the alignment yardstick — which is why I'm proposing both for the same plugin (keeping the reference intra-plugin per the design rules).

Source: skills/claim-review/SKILL.md

Why pm-marketing-growth

They sit next to the existing positioning-ideas and value-prop-statements skills: bold-claim goes one level deeper on positioning (a single contested claim with a scoring rubric), and claim-review closes the loop by checking shipped work against that positioning.

If you're open to it

I'd submit a PR that:

  • Rewrites both skills in neutral voice to match the repo's conventions (frontmatter with name + description incl. trigger phrases, name matching directory)
  • Updates the plugin README and description, skill/command counts in the root README and marketplace.json
  • Bumps versions across all manifests per the versioning policy
  • Passes python3 validate_plugins.py

Happy to adjust scope, naming, or plugin placement — whatever fits the marketplace best.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions