Skip to content

Samples

The samples corpus contains 202 real PM artifacts produced by the pm-skills commands, organized by skill and by product thread. Use this section as a “what does the output actually look like?” reference when picking which skill to run, when tuning your prompt style, or when comparing how the same skill behaves across different product contexts.

CoverageCount
Total samples202
Skills with samples63
Product threads3 (Storevine, Brainshelf, Workbench)

Each sample includes the scenario context, the exact prompt that produced it, and the full artifact output. Fictional metrics are marked with [fictional]; competitor names are real.

ThreadProduct archetypeStagePrompt style
StorevineB2B ecommerce platform building Campaigns (native email marketing)Series A, ~70 employeesOrganized: structured context, references prior work, clear scope
BrainshelfConsumer PKM app building Resurface (contextual morning digest)Post-seed, ~20 employeesCasual: bullet points, shorthand, enough context to work
WorkbenchEnterprise collaboration building Blueprints (document templates with approval gates)Series B, ~200 employeesEnterprise: full stakeholder lists, quantified baselines, explicit metrics

Per-thread sample distribution: Storevine 73, Brainshelf 65, Workbench 64.

The threads exist so you can see how the same skill behaves under different product contexts. A define-hypothesis sample under Storevine reads differently than one under Workbench, because the scenario inputs (team, scale, prior artifacts, decision tempo) differ. Reading three threads of the same skill is the fastest way to internalize the variation surface of any skill.

  • By skill: expand the Samples group in the left sidebar. Each sampled skill has its own subgroup. Most carry 3 samples, one per thread; single-thread utility skills carry 1, and the foundation-persona and foundation-stakeholder-briefings families carry 12 and 18 respectively.
  • By thread (narrative): see the Showcase section, which threads samples together into a complete product lifecycle journey for each company.
  • By artifact type: cross-reference the Skills index to find skills by Triple Diamond phase, then jump to that skill’s samples.
  • File names use the pattern sample_{skill}_{thread}_{topic}.md.
  • Samples are emitted into this site by scripts/gen-site.mjs from library/skill-output-samples/ and read by Starlight’s stock docsLoader(). The library directory has authoring standards in README_SAMPLES.md, SAMPLE_CREATION.md, and THREAD_PROFILES.md for contributors adding new samples.

For a narrative-style tour through the threads, see the Showcase.