/product-cut-sheet

name: product-cut-sheet
description: "Create a source-faithful single-product FF&E cut sheet or spec book entry from a supplied PDF or product URL. Preserve selected identity and source limits; use ffe-spec-book for a complete FF&E book and spec-writer for Project Manual requirements."
allowed-tools:
  - Read
  - Write
  - Bash
  - Glob
  - Grep

/as:product-cut-sheet — Produce a Product Sheet

Before acting, read the [host contract](../../docs/host-harness-contract.md) and this component's [declaration](host-contract.json) (`skill:product-cut-sheet`). 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.

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

Produce one selected product sheet, or an explicitly agreed product/finish grouping. Input: pinned item revision(s) or a one-off source snapshot, accepted template, exact tag, audience and image evidence. Output: an actual requested-format artifact and hash-bound receipt. This skill owns derived individual-sheet preparation manifests and artifact receipts; `/as:product-data-import` owns the accepted job input manifest; `/as:ffe-spec-book` owns package receipts. Neither owns item specifications or project decisions.

Source-faithful product entry

For a supplied PDF or product URL, reproduce only supported facts for the selected product/variant, with source page/URL locators and units. Missing or inaccessible values remain explicit unknowns. Do not add other manufacturers, "or approved equal", submittals, execution clauses, performance requirements or other Project Manual editorial content absent from that source, even when labeled as recommendations. User-supplied project identifiers remain separately identified metadata, not manufacturer facts. Preserve source limits and selected-versus-available configurations; a source page is not approval or schedule adoption. A request for new design requirements belongs to `/as:spec-writer`; a complete FF&E book belongs to `/as:ffe-spec-book`.

Native preparation and publication

Read the complete [native output owner](../../tools/renderers/ffe-output-contract.md) and [design resolver](../../tools/renderers/document-design-contract.md), including exact schemas, identity/versioned filenames, hashes and retry boundaries. Use the actual host's native tooling; operation names identify semantic work and do not dispatch an Arch Studio executable.

Follow [Inspect → Prepare → Verify preparation → Apply → Verify result → Complete](../../docs/workspace-model.md#native-mutation-sequence). The whole affected preparation set is the new manifest, projected data and every image asset; guard full source/template/design/current record pins. For verification, the whole set is the receipt, its immutable companion evidence and actual artifacts. Finish durable saves and separately reopen and validate **all full saved originals/prepared bytes and access metadata before the first publisher**. Inspect pending state before preparing or allocating another revision. Publish complete file bytes without clobbering prior jobs, then freshly read back every actual destination and dependency, including access metadata, before completion. Real every-page visual/link/privacy inspection is required; a hash or supplied flag does not substitute for an inspection.

1. Resolve context and inputs

For project or adopted-schedule work, resolve the nearest valid `PROJECT.md` using `/as:project` context resolution and read its instructions. If that project is unresolved, select it through `/as:studio`; never create one implicitly or write into the plugin. Discover canonical records independently of indexes; preserve malformed records and report their path/problem. Project facts and decisions stay owned by `/as:project`; schedule adoption and revisions stay owned by `/as:master-schedule`.

For samples, random products or demonstrations without a named project, default to standalone one-off work and state that assumption without a project-selection gate. Use an authorized task output folder, not a studio registry or project library. Ask only if an output destination or permission is actually missing. Research real products when selection was delegated, retain sourced facts and label the sheets as samples; never invent product evidence. An existing studio does not change this default. Explicit project/schedule instructions take precedence.

For standalone work, the [native intake owner](../../tools/transformers/ffe-intake-contract.md) uses the explicitly authorized task output root as the one-off boundary. Keep the same `ffe/jobs/<job-id>/` relative structure, evidence, templates and verification below within that task folder. No PROJECT.md or studio registration is required or created.

Use existing task authorization. Ask once only for an unresolved material choice, covering exact target, audience and side effects in one gate; do not re-ask accepted scope/template choices. Read the supplied source before writing. Do not infer approval, price, availability or configuration from a generated sheet.

For **adopted** schedules, read the exact schedule snapshot through `ffe_records.read`. Pin schedule ID/revision/hash and item ID/revision. Select the requested item(s) without changing their identity. For **one-off** work, preserve a source-identified input snapshot with stable local item IDs and positive snapshot revisions; explicitly record that no schedule adoption occurred. Never convert a workbook into authoritative records implicitly. Workbook editing/reconciliation belongs to the host and `/as:master-schedule`, not this output skill.

Accepted input handoff and derived projection

Consume `ffe/jobs/<job-id>/i