Skip to main content

Pm Build Vs Buy

Skill Verified Active

Build/buy/partner decision framework with scoring across time-to-value, TCO, strategic control, and integration complexity. Use when someone says "build or buy", "build vs buy", "should we build this", "vendor evaluation", "make or buy", "partnership evaluation", "third-party vs in-house", "buy vs partner".

Purpose

To guide product leadership and teams through complex build/buy/partner decisions, ensuring a strategic, cost-aware, and domain-informed outcome.

Features

  • Build/buy/partner decision framework
  • Scoring across time-to-value, TCO, strategic control, and integration complexity
  • Domain and personal context adaptation
  • Structured analysis and recommendation generation
  • Detailed scoring matrix and cost of ownership view

Use Cases

  • Evaluating whether to build a new feature in-house versus buying a SaaS solution.
  • Determining the best approach for acquiring a new technology capability (build, buy, or partner).
  • Assessing the strategic trade-offs of different vendor or partnership options.
  • Justifying strategic decisions to stakeholders with data-driven analysis.

Non-Goals

  • Performing the actual build, purchase, or partnership negotiation.
  • Deep technical evaluation of specific vendor APIs or implementation details beyond integration effort.
  • Providing a definitive "answer" without user input and contextual information.

Maintenance

  • info:Commit recencyThe last commit was on April 15, 2026, which is within the last 3 months but not recent enough to be considered highly active.

Code Execution

  • info:LoggingThe skill includes a 'Usage Logger' hook that records executions to `audit.jsonl`, providing a basic audit trail for skill usage.

Compliance

  • info:Telemetry opt-inThe 'Usage Logger' hook logs skill executions to `audit.jsonl`, which functions as telemetry. It's not explicitly opt-in/out but is a local audit log.

Practical Utility

  • info:Usage examplesWhile the skill describes its interaction model and phases, concrete end-to-end examples of input prompts and expected outputs are not provided directly in the documentation.
  • info:Edge casesThe skill mentions adapting to domain context and personal context, and prompts for clarification, but does not explicitly list failure modes or recovery steps for unexpected user input.

Installation

First, add the marketplace

/plugin marketplace add marfoerst/the-pragmatic-pm
/plugin install the-pragmatic-pm@the-pragmatic-pm

Quality Score

Verified
92 /100
Analyzed 1 day ago

Trust Signals

Last commit29 days ago
Stars6
LicenseMIT
Status
View Source

© 2025 SkillRepo · Find the right skill, skip the noise.