alignment-sync

Generate pull-based alignment summaries for pipeline stages and human gates.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill alignment-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alignment-sync
Source: https://github.com/yiwei79/azoth/tree/main/.opencode/skills/alignment-sync
Command: npx skills add https://github.com/yiwei79/azoth --skill alignment-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Alignment reviews in automated pipelines are often a bottleneck; this Skill provides pull-based, phone-friendly summaries that keep humans informed without blocking agents.

Core Features & Use Cases

  • Standard, stage-oriented summaries for pipeline progress, entropy shifts, and session closeouts.
  • Dual outputs: narrative Markdown for human review and machine-readable handoffs for orchestration.
  • On-demand status reporting to enable human gates and decoupled decision-making.

Quick Start

Generate a concise Alignment Summary for the latest pipeline stage completion.

Frequently Asked Questions about alignment-sync

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

FAQPage Schema
What are pull-based pipeline alignment summaries and how do they work?

Pipeline alignment summaries are on-demand status reports for pipeline stages, entropy escalations, and human gates. They enable pull-based human review without blocking automated agents, producing both narrative Markdown and machine-readable YAML handoffs.

How do I generate a human gate summary without blocking my automation pipeline?

Generate a human gate summary without blocking your pipeline by requesting a pull-based alignment summary. This provides a concise, phone-friendly narrative Markdown for human review and a structured YAML handoff for the orchestrator, ensuring agents remain unblocked.

Does alignment-sync work for session closeouts and entropy escalations?

Yes, alignment summaries are applicable to session closeouts and entropy escalations. They generate stage-oriented summaries capturing entropy shifts and final states, outputting narrative Markdown for human review and structured YAML handoffs for orchestrator forwarding.

What is the best way to format pipeline handoffs for orchestrator forwarding?

The best way to format pipeline handoffs is using canonical, machine-readable structured formats like YAML. These accompany narrative Markdown summaries, enabling orchestrators to process stage completions and human gate decisions automatically.

Can I use pipeline status summaries for phone-friendly human review?

Yes, pipeline status summaries are designed to be concise and phone-friendly. They provide narrative Markdown formats tailored for on-demand human review, allowing decision-makers to monitor stage progress and entropy shifts from mobile devices.

When should I not use pull-based alignment summaries in an automation pipeline?

Avoid pull-based alignment summaries when synchronous blocking is required for pipeline progression. They are designed for decoupled, on-demand human review and do not automatically halt agent execution while awaiting human gate decisions.