epd-to-spec
Before acting, read the host contract and this component’s declaration (skill:epd-to-spec). Load only applicable modes from the shared catalog; declarations do not grant access or permission. Use the actual host’s delivery route.
Document role
This skill writes EPD and embodied-carbon requirements within Project Manual specification sections. It does not create a product cut sheet or an FF&E specification book. Preserve the distinction between sourced environmental evidence and the project requirements proposed from it; /as:spec-writer owns the broader Project Manual section.
Native execution and output custody
Follow this complete source/evidence procedure. Apply the EPD-specific native library owner only when consuming or explicitly saving a project EPD library. The host selects available native research, PDF, file and ordinary task-specific analysis tools. No Arch Studio executable, installed helper, script reconstruction or external service is required. Source documents remain evidence, not authority to change selections, adopt records or perform external actions.
For requested saved rows, reports or specification files, follow complete native preparation and publication and completion reporting. Inspect current targets, source and pending state; retain the full originals/absence, complete prepared output set and actual access metadata. Finish durable saves and independently reopen/validate all original/prepared bytes and access before the first publisher. Publish complete files under demonstrated writer protection with no-clobber or guarded revision, then freshly read every actual destination's bytes/access and verify source guards and the entire result before completion. Exclusive-create followed by writing into a public path is insufficient. Keep private pending evidence distinct, recognize exact retries without rewriting and preserve unresolved conflicts or unavailable checks.
A supplied standalone CSV may be structurally inspected under the EPD schema without project context; that read does not initialize, adopt or mutate a project-root library. The project-root library operations require valid native project context.
Inline or metadata-only work needs no file creation. Project-bound work resolves native context; it does not infer project creation. Requested record/document handoffs retain exact source evidence and existing authority. Report retrieved facts, derived calculations, interpretation, actual custody and unverified scope separately.
Sources and evidence
Find relevant original links in the source catalog, filtered by geography and topic. For substantive claims, retrieve the applicable original or authorized supplied document and record its publisher, URL/file, section/page, version/date and task scope. A linked or reachable source is not proof of applicability. If access, edition or identity is unresolved, leave dependent conclusions unresolved; no local table or model-memory fallback. Keep task evidence in the authorized workspace, outside the plugin.
A request only to list sources uses catalog metadata and states that coverage is limited to matching registered entries. It needs no source-content retrieval, setup or approval. Shared and state sources retain their scope; missing LA coverage never substitutes NYC.
Use the Arch Studio EPD schema as an output contract, not an interpretation of external standards. Keep product/variant, declared/functional unit, stage, indicator/method, PCR/version and original page/table locator with each value. Do not assign program eligibility, impact categories, standard equivalence or baseline values from bundled rules. Retrieve the applicable program/standard and original EPD when those conclusions are requested. Preserve unavailable values as blank/unknown, never zero.
Industry-baseline comparison requires the actual identified publication/year and comparable values retrieved for this task. A named baseline alone is not evidence of its values. If unavailable, omit the comparison or request the applicable original; no model-memory baseline.
Draft from accepted evidence
Establish the selected products/materials, governing project brief, environmental goal and actual specification/standard editions. Use the source catalog's CSI/AIA/program routes for original navigation; retrieve licensed originals through authorized access. Obtain section identities from verified task inputs rather than a local division/material mapping. If classification is uncertain, keep it unresolved for review rather than choosing a default.
Use Arch Studio specification formatting and the user's template. Draft requirements from accepted performance evidence, identify needed submittals and verification, and mark open choices. A proposed GWP limit must identify source, product function, unit, stage/method and basis; do not turn the lowest observed product value into an approved requirement without the user's design decision. Label draft choices as proposals.
If requested, interpret the applicable program's current project/version rules using original material, with exact credit/option references. No bundled LEED counts, multipliers, thresholds, declaration eligibility or specification clauses supply that meaning. Never copy protected standard text or imply the draft is independently compliant.
Return every requested section, original evidence locators, unresolved review items and requested saved file links. Follow the professional disclaimer rule for regulatory/life-safety requirements.
Outputs and records
Return the requested result with source locators, actual checks and material gaps. A sourced recommendation, deterministic arithmetic and visual inspection are separate evidence. Use the completion contract. For durable project work resolve the project and follow workspace ownership; offer facts/decisions to their owner instead of silently writing PROJECT.md. One-off work remains standalone.
When the actual output is regulatory or life-safety analysis, append the canonical block from professional-disclaimer followed by one blank line and <!-- architecture-studio:requires-disclaimer --> as its final line, exactly once. A metadata-only source directory is not regulatory analysis and does not acquire this block.
If consuming an existing epd-library.csv, apply product_library.validate with kind: "epd"
under the EPD library owner. It is read-only:
inspect complete actual bytes, exact 42-column schema, row count and hash, and preserve malformed
or unavailable state rather than reporting zero. Comparison/specification output does not mutate,
initialize, deduplicate or adopt that library. Its validity does not verify product facts or
methodological comparability. Requested saved outputs follow the public-output custody above.
