eforge-playbook

You can create reusable automation playbooks by describing your recurring workflow and using the create command to validate and save templates with frontmatter and a standardized body. This ensures repeatable deployments and governance across your team.

Playbook scope shadowing allows you to localize templates at the project-local level while inheriting shared project-team configurations. You can promote or demote playbooks across these scopes to control whether workflows are shared or localized to specific projects.

Managing recurring build step workflows is handled through a unified interface that supports list, run, edit, create, promote, and demote actions. This structure ensures consistent automation and governance for your recurring deployment workflows.

Yes, running and validating playbooks relies on the eforge daemon API. The Skill uses this API to validate frontmatter-defined names and descriptions, ensuring your saved playbooks meet the required standardized format before execution.

Yes, you can promote a personal playbook to a shared project-team scope. The Skill supports promotion and demotion workflows, allowing you to transition templates between user, project-team, and project-local scopes to share or localize automation.

Saving eforge playbooks requires a standardized format with frontmatter defining the name and description, followed by a standardized body. The Skill validates this structure against the eforge daemon API to ensure repeatable deployments and consistent governance.