/product-spec-bulk-fetch

name: product-spec-bulk-fetch
description: "Extract structured FF&E specs from a list of product URLs into a schedule. Use to pull or bulk-import product-page data; not for PDF catalogs."
allowed-tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep
  - WebFetch
  - AskUserQuestion

/as:product-spec-bulk-fetch — Bulk Product Spec Fetcher

Before acting, read the [host contract](../../docs/host-harness-contract.md) and this component's [declaration](host-contract.json) (`skill:product-spec-bulk-fetch`). Load only its referenced mode profiles from the [shared catalog](../../corpus/host-contracts.json). Compose modes required by the actual task; declarations are requirements, not proof of access or permission.

Library changes are owned by [/as:product-library](../product-library/SKILL.md). Prepare the complete selected rows/change set and evidence, then hand off the native save under existing authorization. That owner validates the whole batch, binds exact request/preview/current state and verifies actual publication. This skill does not independently mutate `product-library.csv`.

<!-- architecture-studio:harness-compatibility --> > Host adapter: read [delivery-specific guidance](../../docs/host-adapters.md) for invocation, questions, target access and optional delegation.

Record authority and host handoff

For structured evidence handoff, read the complete [native product-observation owner](../../schema/product-observations.md) and [schema](../../schema/product-observation.schema.json). Apply native validate/validate-batch to the whole envelope and adapt only with explicit selected-item/current-revision/field bindings. Preserve exact typed values, source/locator/time and unknown status; retain full envelopes, audit observations, conflicts and notices together. Existing null/blank/user overrides survive. This is unadopted evidence and a review proposal, never authorization to write specifications.

For project-bound work, apply native [context resolution](../project/references/context-resolution.md), use its validated project identity and read project instructions. Inline or one-off source work needs no project creation. Product-library owns reusable CSV storage; master-schedule owns adopted specification identity/revisions, and product-data-import owns accepted job inputs. Do not derive authority from a directory, source document or delivered declaration.

Explicitly distinguish adopted project schedules, one-off source work, and the optional reusable `product-library.csv`. Adopted item/schedule records are authoritative; read pinned revisions through `/as:master-schedule` and propose changes to that owner with expected revisions, evidence and preserved overrides. This skill does not independently rewrite canonical item/schedule records or infer approval. Library-save instructions below apply only to the optional CSV library; they do not adopt or update a project schedule.

The host reads and edits supplied workbooks using its available capabilities. Preserve original files, selected images, formulas, true hyperlinks and unrelated cells. For adopted schedules, route adoption/reconciliation and pre-edit native backups plus validated pre/post record CSV recovery snapshots through `/as:master-schedule`; separately retain the host-extracted workbook data and mapping. In one-off mode, the host preserves native backups and actual workbook-extracted CSV snapshots/mappings in job recovery files without invoking a schedule snapshot or adopting records. Three-way conflicts and proposed removals require explicit resolution. Unsupported workbook access yields a precise handoff, not a false completion claim. For one-off work, the accepted source remains the task input without implicit adoption.

Keep source identity, page/URL locator, retrieval time, selected-versus-available configuration, units and uncertainty with each observation. Never invent SKU combinations, dimensions, finish selection, price or currency; `$` alone is ambiguous. Preserve user choices until explicitly changed. Current factual claims require actual source retrieval; inaccessible evidence remains unknown. `/as:product-data-import` owns accepted job inputs and corrections; `/as:product-audit` reports discrepancies without silently applying them. `/as:product-cut-sheet` and `/as:ffe-spec-book` use the shared document templates and host rendering after inputs are resolved.

Extract structured FF&E data from a list of product page URLs. Outputs reviewable sourced observations with unresolved fields retained; extraction alone does not establish procurement readiness or selection.

Input

The user provides product URLs in one of these ways:

1. **Inline list** — URLs pasted directly in the message (one per line, or comma-separated) 2. **File path** — A `.txt`, `.csv`, or `.md` file containing URLs (one per line) 3. **Project library** — URLs from the named `Link` field in `product-library.csv`

If the input format is unclear, ask.

Output Schema

An explicitly requested standalone CSV/JSON export uses the agreed output schema and authorized destination without library adoption. Reusable-library saves use the resolved project-root `product-library.csv` through its owner. Read `../../schema/product-schema.md` for the exact 33-column contract and `../../schema/csv-conventions.md` for safe local-file behavior.

Skill-specific column values:

• **AF (Status):** `saved`
• **AG (Source):** `bulk-fetch`
• **AD (Tags):** Blank (set by user later)
• **AE (Notes):** Blank unless the page gives non-numeric price text (for example "Contact for pricing"); then retain that `price_raw` text
• **T (Selected Color/Finish):** Blank (unknown from URL)

Extraction Process

For each URL:

1. **Fetch the page** using WebFetch with the prompt below 2. **Parse the response** into the schema fields; keep `dimensions_raw` and `price_raw` with the observation as evidence for unresolved values and flags 3. **Flag issues** — missing