epf-full-cycle

Orchestrate end-to-end 1C EPF creation from scaffold to build.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill epf-full-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epf-full-cycle
Source: https://github.com/msrv-tech/skills/tree/main/epf-full-cycle
Command: npx skills add https://github.com/msrv-tech/skills --skill epf-full-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the full lifecycle of creating a 1C external processing (EPF) from scaffold to build, reducing manual orchestration and potential for errors in EPF pipelines.

Core Features & Use Cases

  • Orchestrates end-to-end EPF workflow from epf-init to epf-build.
  • Supports optional steps such as adding forms, templates, and BSP registration for extended customization.
  • Enables reproducible EPF development pipelines suitable for automated testing and deployment.

Quick Start

Start with epf-init and sequentially add the form, templates, and BSP, then validate and build to generate the EPF.

Frequently Asked Questions about epf-full-cycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate 1C external processing development from scaffold to build?

Automating 1C external processing development from scaffold to build involves orchestrating sequential steps like epf-init, form creation, template addition, and epf-build. This Skill coordinates that workflow, reducing manual pipeline orchestration and potential errors.

What is the full lifecycle of a 1C EPF creation pipeline?

A full 1C EPF creation pipeline includes initializing the scaffold, adding forms and templates, registering BSP components, validating the structure, and executing the build. This process ensures reproducible external processing suitable for automated testing and deployment.

Can I add optional forms and templates during 1C EPF workflow automation?

Yes, you can add optional forms and templates during 1C EPF workflow automation. The orchestration supports extended customization by allowing sequential integration of epf-add-form, template-add, and bsp-registration steps before validation and building.

Does the 1C EPF build workflow require BSP registration for validation?

BSP registration is not strictly required for validation but is supported as an optional step for extended customization. The workflow enforces compatibility with bsp-registration, epf-validate, and epf-build, allowing flexible pipeline configuration depending on project requirements.

What is the best way to ensure reproducible 1C EPF development pipelines?

The best way to ensure reproducible 1C EPF development pipelines is to orchestrate the end-to-end workflow from initialization to build. Automating sequential steps including scaffold, form creation, validation, and build reduces manual errors and creates consistent deployment artifacts.

When should I not use end-to-end EPF workflow orchestration?

You should not use end-to-end EPF workflow orchestration for isolated 1C development tasks that only require a single step, such as adding a form or template independently. It specifically targets comprehensive lifecycle management requiring coordination across multiple pipeline stages.