workflow-onboarding

You can automate repository setup by running a skill that synchronizes mandatory labels and generates capability documentation. This idempotently creates the six canonical LOOP/NETWORK labels and seeds the installed-skills markdown file to ensure consistent agent-to-repo communication.

Synchronizing canonical labels provides consistent triage surfaces for remote agents operating within the repository. Without the mandatory LOOP/NETWORK labels, automated proposal-loop workflows cannot properly categorize and route agent-driven interactions.

Yes, the GitHub CLI is required to configure repository infrastructure for proposal loops. The onboarding process relies on the CLI to execute network mutations, create mandatory labels, and enforce the mandatory human-in-the-loop safety guardrails.

Yes, you can generate capability documentation by running the workflow-onboarding skill, which automatically creates the docs/agents/installed-skills.md file. This file explicitly exposes repository capabilities to remote agents, enabling proper agent-to-repo communication.

The label synchronization process enforces a mandatory human-in-the-loop confirmation step before executing any network mutations or file writes. This guardrail prevents unauthorized or unintended changes to the repository infrastructure during the onboarding process.

Yes, the repository label synchronization process is idempotent, safely creating or updating the six canonical LOOP/NETWORK labels without duplicating entries. Running the workflow-onboarding skill multiple times maintains repository consistency without causing label conflicts.