skills.rest
JoyJoin-Tech-Limited
JoyJoin-Tech-LimitedOFFICIAL
Explore all skills by this author →
GitHub

orchestration-turn-reporting

Generates structured turn-end summary JSON and supervisor consolidation reports for multi-agent orchestration.

Updated Dec 24, 2025
Search Tags:#multi-agent#orchestration#feedback loop#json schema#session logging#turn summary#supervisor consolidation
One-click install
npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill orchestration-turn-reporting-joyjoin-tech-limited
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration-turn-reporting
Source: https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1/tree/main/.github/skills/orchestration-turn-reporting
Command: npx skills add https://github.com/JoyJoin-Tech-Limited/JoyJoin_app_v0.1 --skill orchestration-turn-reporting-joyjoin-tech-limited

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Multi-agent orchestration sessions lose track of what each agent delivered, learned, and should improve next, making it impossible to run feedback loops or audit turn-by-turn progress. This Skill standardizes per-agent turn summaries and supervisor consolidation so every turn produces truthful, persisted, machine-readable records. ## Core Features & Use Cases - Agent turn summaries: Emit record-summary JSON capturing what was done, learned, files changed, blockers, and 1-2 self-suggested improvements per turn. - Supervisor consolidation: Merge child agent summaries into a canonical supervisor_turn_report with turn status, cross-agent insights, and a recommended orchestration strategy. - Bounded persistence: Store full entries in .git/.orchestration/events.jsonl and compact last-5-turn projections in context.json, never publishing to repo-memory/. - Use Case: After a Supervisor coordinates Researcher and Backend Engineer agents on a feature, use this Skill to record each agent's summary JSON, consolidate them into one executive briefing with a Ready/Blocked/Done status, and feed the last 5 turns into the next routing decision. ## Quick Start Ask the agent to end its turn with a record-summary JSON and an executive briefing note covering what was delivered, learned, and the next step.

Frequently Asked Questions about orchestration-turn-reporting

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

FAQPage Schema
How do I add a turn-end summary protocol for orchestration agents?▼

Define a record-summary JSON schema with done, learned, nextSteps, and turnStatus fields, then have each agent emit it at turn end alongside an executive briefing note. Persist entries to .git/.orchestration/events.jsonl before returning control.

How does supervisor consolidation of agent summaries work?▼

The Supervisor gathers child summary JSON objects, persists any unrecorded ones, and builds one supervisor_turn_report with key bullets, cross-agent insights, and sourceSummaryIds. It consolidates without rewriting child facts, treating child JSON as authoritative.

Where are orchestration turn summaries persisted?▼

Summaries are persisted only under .git/.orchestration/, with full entries in events.jsonl and compact bounded projections in context.json. They are never published to repo-memory/, and skipped or failed persistence must be stated explicitly.

What is the last-5-turn feedback loop in agent orchestration?▼

Agents review their own recent summaries and supervisor feedback from the last 5 turns by default before acting, then include 1-2 self-suggested improvements in each new summary. The Supervisor uses the last 5 reports to refine the next routing decision.

Why does a turn summary conflict with actual file changes?▼

This happens when summaries infer from vague recollection instead of current-turn evidence. The rule is to record only what happened in the current turn using explicit file references, and treat recorded child JSON as authoritative over prose paraphrases.

Can agents automatically update skill files from turn reports?▼

No. Turn reports do not rewrite .github/skills/; agents may propose updates but humans merge them after governance review. The Supervisor is forbidden from autonomously editing skill files.

Related Skills

Explore More Software Engineering Skills→
dayvidphamdayvidpham
2

Architect: Handoff to Supervisor

Create a HANDOFF document linking ratified proposals to Supervisor tasks.

Community
Advanced
BordaBorda
24

distill

Analyze memory, tasks, and lessons to generate structured governance proposals.

Community
Advanced
dtabordadtaborda

contract-testing

Validate JSON contract fixtures against Zod schemas with Vitest.

Community
Intermediate
astrolabe-appsastrolabe-apps
1

astrolabe-schemas

A JWT-based authentication system for a React app.

Official
Intermediate