القائمة
Apply EngiFoundry automation preferences to verified-available PAK evidence, obtain acceptance when required, close delivery, or record rejected acceptance for rework.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | engifoundry-deliver |
| description | Apply EngiFoundry automation preferences to verified-available PAK evidence, obtain acceptance when required, close delivery, or record rejected acceptance for rework. |
Read ./engifoundry.config.json, the project-owned workspace guide, Workflow config, and contracts.md. Then read the PAK, its execution.verificationRef, the referenced Verify record, required artifacts, and closeout requirements.
The Agent reads this contract only for a PAK whose latest verification result is verified-available and whose execution status is verified-available or acceptance-pending. Verification evidence is input; during this work the Agent does not repeat Verify or Review, implement rework, or revise contracts.
The acceptance record and Package state describe exactly one current fact:
full-auto supplies auto-accepted when current verification is verified-available.job-approval and package-approval are acceptance-pending until the user decides on the concise Verify result.user-approved.rework-required with kind implementation.rework-required with kind contract.acceptance-pending and requires the reason.Every rework-required acceptance fact has an immutable rejection record attached as execution.deliveryRef. Implementation rejection means the affected Jobs and Package execution are also rework-required; contract rejection means Package planning is also rework-required.
Confirm every required artifact is referenced and every closeout requirement is satisfied. Create only delivery outputs required by the PAK. Satisfied acceptance and closeout facts are recorded in one immutable delivery JSON, attached as execution.deliveryRef, with execution.status: completed.
Every completed PAK also has the matching human-readable DELIVERY-<NNN>.md defined by the reference contract. It summarizes PAK execution, current engineering state, evidence and artifacts, severity-labeled risks, and handoff facts. This summary is required even when no additional user-facing document was requested.
A missing closeout item is work to finish, not acceptance failure. blocked describes only an objective closeout condition the Agent cannot resolve during delivery work; it has an immutable record attached as execution.deliveryRef.
completed is terminal with its delivery record.implementation rejection makes Exec the applicable correction contract.contract rejection makes Orch the applicable correction contract.acceptance-pending and blocked are terminal for the current turn while their facts remain.The Agent never reports delivery completion without execution.status: completed and a durable execution.deliveryRef.
Create or migrate the EngiFoundry project scaffold and create or modify its Executor and Workflow configuration through a controlled interactive flow.
Create a detailed human-readable document from EngiFoundry project records when the user explicitly requests documentation, a report, guide, specification, detailed summary, or handoff document.
Declare EngiFoundry Node Skill contracts, their project-state signals, records, responsibilities, and possible navigation destinations so the Agent can assemble the contracts needed for a request.
Review EngiFoundry planning, Job work, code, documents, research, or other durable outputs in clean context and record pass, rework-required, or factual blocked conclusions.
Classify new EngiFoundry work as direct Agent action, Package orchestration, or factually blocked before a Package exists. Use when deciding whether new work needs Orch.
Execute ready EngiFoundry Jobs in dependency order, apply configured Executor fallback, enforce engineering discipline, and record concise results. Use for implementation or rework of an existing ready PAK.