cos-session

Convert operator observations into GitHub issues and code fixes during bm chat sessions.

18|4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/botminter/botminter --skill cos-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cos-session
Source: https://github.com/botminter/botminter/tree/main/profiles/scrum/roles/chief-of-staff/coding-agent/skills/cos-session
Command: npx skills add https://github.com/botminter/botminter --skill cos-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The chief-of-staff session converts informal operator observations, bugs, and operational concerns into structured, verifiable work items and immediate fixes so issues do not languish or get lost across multiple agent workflows.

Core Features & Use Cases

  • Filing Rich Issues: Investigate reports, gather technical context and affected files, and create detailed GitHub issues via the github-project skill rather than echoing the operator's words.
  • Reviewing Member Activity: Inspect Claude Code session logs and Ralph state to report what a member is working on, identify wrong dispatches, and recommend or apply corrections.
  • Fix Now & Propagate: Make small code or config fixes in the team repo, commit and push with the project's convention, and run bm teams sync --all to ensure changes reach all workspaces.
  • Observability & Troubleshooting: Surface patterns in wasted cycles, rate limits, or sync failures and drive remediation or tooling where recurring problems appear.

Quick Start

Start a chief of staff session by saying "chief of staff session" or "cos session" and describe the observations, issues, or members you want reviewed.

Frequently Asked Questions about cos-session

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

FAQPage Schema
How do I turn operator observations into structured GitHub issues?

To turn operator observations into structured GitHub issues, this Skill investigates reports, gathers technical context and affected files, and creates detailed issues via delegated GitHub operations rather than echoing the operator's words.

What is the best way to review Claude Code session logs for team activity?

Reviewing Claude Code session logs is handled by inspecting local Claude session logs and Ralph state to report what a member is working on, identify wrong dispatches, and recommend or apply corrections.

Can I make immediate code fixes and propagate them across team workspaces?

Yes, you can make immediate code or configuration fixes in the team repo, commit and push with project conventions, and run bm teams sync --all to ensure changes reach all team workspaces.

How do I troubleshoot rate limits and sync failures across agent workflows?

To troubleshoot rate limits and sync failures, this Skill surfaces patterns in wasted cycles or sync failures across agent workflows and drives remediation or tooling updates where recurring problems appear.

Do I need a chief-of-staff session to file bugs and triage priorities?

Yes, you need to start a chief-of-staff session via interactive chat to file bugs, review member activity, triage priorities, and propagate fixes across team workspaces.