Procurement Tools

Plugin procurement-tools from marketplace danielrosehill in danielrosehill/Claude-Code-Plugins. Commands read from the repo's manifest — today.

Skills (14)

• bom-build

  Build a bill of materials — a shopping list written as requirements rather than as products, with stable line ids, quantities, substitution rules and optional references to a spec. Use when a purchase is several items rather than one, when kitting out a space or a job, when a list needs to go to sup

• evaluation-matrix

  Generate the evaluation-criteria brief from a spec, judge candidates against it one requirement at a time, and render the conformance matrix. Use when candidates have to be checked against a defined requirement set rather than ranked, when several candidates need evaluating in parallel by subagents,

• market-evaluator

  Rank the candidates that survived conformance evaluation and produce a purchase recommendation — a top three in order, each with product, price and where to actually buy it, followed by category picks such as best budget, best overall and best for features. Use once conformance records exist and the

• marketplace-handoff

  Decide when a purchasing question has stopped being about the product and become a question about a specific marketplace, and hand it to that marketplace's dedicated plugin instead of answering it here. Use mid-workflow when a comparison, price check or delivery question narrows to one named marketp

• new-workspace

  Provision a new purchasing workspace as a standalone repo — scaffold, personalised CLAUDE.md, workspace manifest with a stable id, and a private GitHub repo by default.

• part-number-equivalence

  Work out which part numbers name the same product across regions, brands and channels — and which look identical but are not. Use when a product found in one market has to be sourced in another, when a manufacturer's model numbers differ between the US and Europe, when the same object is sold under

• price-scan

  Scan a shortlist of products for current price, stock, shipping and landed cost across the user's configured marketplaces, from the user's own machine with the VPN exit set to the country each shop requires. Use when comparing live prices across shops, re-checking whether a shortlisted item has move

• procurement-report

  Render a dated, never-overwritten report (markdown + PDF) from whichever spec, conformance and pricing artefacts a workspace holds.

• rfq-package

  Assemble a request for quotation from a bill of materials — line descriptions a supplier can actually quote, substitution rules, delivery and terms, and the questions worth asking. Use when a shopping list is ready to go out to suppliers, when comparing quotes from several suppliers on the same basi

• spec-as-code

  Turn a purchase requirement into a versioned, machine-readable spec.yaml with stable requirement ids, so that evaluation, BOM lines and RFQs all reference the same requirements instead of restating them in prose. Use when a purchase has enough requirements that a paragraph stops being enough, when r

• spec-sheet-retrieval

  Find the manufacturer's own documentation for a specific product — datasheet, technical data, operating manual, declaration of conformity — and extract the published values with the document and revision they came from. Use when a spec claim has to be settled rather than repeated, when retailer list

• spec-variants

  Run several parallel either/or versions of one spec — a budget bar and a premium bar for the same purchase — each independently versioned, and diff what actually differs between them. Use when the answer is "it depends how much we want to spend", when a requirement could reasonably be set at two lev

• technical-sourcing

  Run a technical purchasing investigation end to end — spec as code, manufacturer documentation, part-number equivalence across regions, conformance evaluation, bill of materials, RFQ. Use when a purchase turns on specifications rather than on price or reviews, when requirements are specific enough t

• workspace-folder

  Add a purchase-decision folder inside an existing procurement repo instead of a standalone repo — same scaffold and manifest, never a nested git. The repo sibling is new-workspace.

Slash commands (34)

• /procurement-tools:apply-profile
• /procurement-tools:compare
• /procurement-tools:define-spec
• /procurement-tools:evaluate

  Quick one-off evaluation of a single product against the current spec

• /procurement-tools:extract
• /procurement-tools:intake
• /procurement-tools:load-preferences
• /procurement-tools:market-check

  Compare local market prices against international RRP with import-cost realism

• /procurement-tools:mkt-gaps

  Identify unmet and over-served requirements, the compromise axes, and where the market is thin — the payload of a landscape survey

• /procurement-tools:mkt-matrix

  Build the spec-conformance matrix across the whole field — every requirement against every live option, unknowns marked as unknown

• /procurement-tools:mkt-refresh

  Re-sweep a previously surveyed market and report what changed since the last survey

• /procurement-tools:mkt-report

  Write the landscape report — the state of the market against the spec, as markdown and PDF

• /procurement-tools:mkt-segment

  Derive how the market divides — segments and the axes it actually varies along — from the enumerated field

• /procurement-tools:mkt-spec

  Define the requirement envelope and survey scope for a market landscape survey — capability-framed, no candidates

• /procurement-tools:mkt-survey

  Sweep the market and enumerate the full field against the survey spec — breadth first, everything logged and dated

• /procurement-tools:rec-list

  List recent recommendations from the recommendations/ folder with their feedback status (liked, disliked, no-response, queued).

• /procurement-tools:rec-log-feedback

  Record like/dislike/nuanced feedback against a past recommendation and update the preference profile so future suggestions improve.

• /procurement-tools:rec-more-like-this

  User provides something they enjoyed (a film, book, podcast, video, course, etc.); the recommender suggests similar items they might also enjoy, grounded in the preference profile.

• /procurement-tools:rec-onboard

  First-run setup for the recommendation workspace — picks format, captures initial preferences, builds the folder structure, and suggests MCPs.

• /procurement-tools:rec-opml-ingest

  Parse an OPML file (typically a podcast subscription export) from ingest/opml/ and use it to seed/update the preference profile.

• /procurement-tools:rec-reading-list-ingest

  Parse a reading list export (Goodreads, StoryGraph, Pocket, Instapaper, Readwise, etc.) from ingest/reading-list/ and use it to seed/update the preference profile.

• /procurement-tools:rec-watch-history-ingest

  Parse a watch history export (Netflix, Trakt, Letterboxd, JustWatch, etc.) from ingest/watch-history/ and use it to seed/update the preference profile.

• /procurement-tools:recommend
• /procurement-tools:recompare

  Re-run the shortlist against the current spec and write a new dated recommendations file

• /procurement-tools:research
• /procurement-tools:rig-analyze
• /procurement-tools:rig-compare
• /procurement-tools:rig-estimate
• /procurement-tools:rig-profile
• /procurement-tools:rig-recommend
• /procurement-tools:rig-setup
• /procurement-tools:save-preferences
• /procurement-tools:shop-setup

  Create or update the private marketplace, VPN and delivery-address config the price scanner reads

• /procurement-tools:update-spec

  Update spec.md with an addition, edit, or removal — diff-only response

Subagents (7)

• manufacturer-research

  Researches manufacturer reputation, history, support quality, and regional presence. Use before recommending any product from an unfamiliar brand.

• preference-curator

  Interviews the user about their tastes, parses ingested history (OPML, watch history, reading lists), and maintains memory/preferences.md as the canonical preference profile.

• price-comparison

  Compares prices across vendors and markets, calculates markups, and factors in import costs (shipping, VAT, customs). Use when evaluating value across multiple sources or when deciding buy-local vs. import.

• product-extraction

  Extracts structured product data (name, brand, price, SKU, vendor) from screenshots, PDFs, and catalog images. Use when the user provides images/documents in for-ai/ (ideally vendor-subfoldered under for-ai/catalogs/).

• recommender

  Generates targeted content recommendations grounded in the user's preference profile and feedback history. Writes one markdown file per recommendation under recommendations/ with reasoning and metadata.

• review-aggregation

  Gathers and synthesizes reviews from multiple platforms into a weighted score and a short honest summary. Use during research for each serious candidate.

• spec-verification

  Verifies claimed product specs against authoritative manufacturer sources. Use when a claimed spec is load-bearing for the recommendation (e.g., "has USB-C charging", "supports Wi-Fi 6E").

Similar plugins