orchestrator-log

Writes orchestrator decisions and subagent results to session audit log files.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill orchestrator-log-oleyna80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator-log
Source: https://github.com/oleyna80/agentic-sdlc-framework/tree/main/skills/orchestrator-log
Command: npx skills add https://github.com/oleyna80/agentic-sdlc-framework --skill orchestrator-log-oleyna80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-stage AI agent workflows make many decisions (tier selection, skill skips, critic verdicts, scope changes) that are lost when the conversation ends. This Skill maintains a persistent audit trail so you can answer "why did the orchestrator make this choice?" without the original transcript. ## Core Features & Use Cases - Decision Logging: Records Control Tower decisions (tier, skips, topology, critic verdict, outcome) to memory_bank/orchestrator-log.md after preflight, critic review, scope changes, Hard Stops, and closeout. - Subagent Result Tracking: Logs each subagent's verdict, key findings, and evidence summary to memory_bank/review-log.md after every return. - External Team Consolidation: Reads external-team-log.md from delegated Claude Code handoff sessions and consolidates verdicts into the review log during closeout. - Use Case: After a Work Block completes, an Owner reviews orchestrator-log.md to see why Standard tier was chosen, which skills were skipped, and what the critic verdict was — all in one table row. ## Quick Start Ask the agent to log the current orchestrator decision and subagent results to the session audit trail.

Frequently Asked Questions about orchestrator-log

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

FAQPage Schema
How do I log orchestrator decisions in an AI agent workflow?▼

Write one row to memory_bank/orchestrator-log.md after each decision point: Stage 0 Preflight, critic review, scope changes, Hard Stops, and Stage 3 Closeout. Each row captures the decision, rationale, subagents used, critic verdict, and outcome.

How to track subagent results across a session?▼

Record each subagent return in memory_bank/review-log.md with the agent name, verdict, one-line key finding, and evidence summary. Add the row immediately after the Control Tower reads the subagent's report.

What is the difference between orchestrator-log and review-log?▼

orchestrator-log.md records why Control Tower made decisions (tier, skips, critic verdicts). review-log.md records what subagents found (verdicts, findings, evidence). Both are write-only for the Control Tower.

When should I skip writing to the orchestrator log?▼

Skip logging for trivial single-file fixes with no logic change and routine documentation-only Work Blocks with no workflow, contract, release, safety, or governance impact. There is nothing meaningful to audit in those cases.

Can logging block the agent pipeline?▼

No. Logging is inline and auto-proceeds — it never blocks the pipeline and is not a separate stage, subagent, or plan. The Control Tower writes log rows as part of its normal stage transitions.

What should never be written to agent audit logs?▼

Never log secrets, tokens, or credentials. Keep entries under one line, avoid duplicate rows, and put task status in progress.md instead — the log is an audit trail, not a task tracker.