Your team and its agents, in one workspace. Chat, calls, tasks, docs, pull requests and decisions, with Claude Code, Codex, Cursor, Gemini, OpenCode and pi as teammates. Everything links back to the session that did it.
This repository also configures its own agents. See what codecast tells them →
Skill Claude CodeCodex
Drive a plan to completion by orchestrating implementer, reviewer, and critic agents across waves of parallel work. Use when the user says "orchestrate", "implement this plan", "execute plan", "drive this", or approves a plan for execution.
Skill Claude Code
Ask the team a question without blocking on it. Posts the question to the team channel with the context needed to answer it cold, parks this session as dormant, and continues when an answer arrives. Use when a question is for a person who is not in this thread, when the human is away, or when asked to check with the…
Skill Claude Code
Try several approaches to the same problem in parallel and compare the results side by side. Forks this conversation once per approach, waits for the branches to settle, then lays out each branch's diff, evidence and cost with a verdict. Use when two or more designs are plausible and the cheapest way to choose is to…
Skill Claude Code
Before editing or fanning out work, find the live sessions on this repository that are changing the same files, show what they changed, and warn them. Use before starting a task that touches shared files, before spawning workers, or when asked who else is working on this.
Skill Claude Code
Close the working day so nothing is lost and tomorrow starts cold without cost. Checks every live session for an honest pinned state, writes handoffs for work that will pause, arms follow ups that should run overnight, tidies the inbox, and leaves a short digest. Use at the end of a working day or before a long pause.
Skill Claude Code
Turn a team call's action items into tasks people can pick up, each linked to the line in the transcript where it was agreed. Reads the call's summary and transcript, confirms each commitment against what was actually said, and files tasks marked as decided in a meeting. Use after a call, when asked what was agreed…
Skill Claude Code
Package the current work so the next session or a teammate can continue without reading this thread. Writes the decisions, the direction, what is verified, open questions and ordered next steps as a shared doc, pins the state, and optionally forks, spawns or hands the work to a session. Use before stopping, before a…
Skill Claude Code
Turn what this session learned into guidance the next session and the team will read. Extracts corrections the human made, decisions taken, and gotchas found; writes project guidance into the repository's agent instructions, records decisions where they are searchable, and files the rest as a doc. Use at the end of a…
Skill Claude Code
Harvest the corrections humans made across the team's sessions in a window, cluster them, and propose the guidance that would have prevented each. Reads every session where someone said stop, no, not like that, or redirected an agent, and turns the pattern into instruction lines, decisions, or a doc. Use for a weekly…
Skill Claude Code
Run an autonomous loop that works through a queue of tasks one fresh session at a time, with verification as the gate and a human decision at merge. Sets up a recurring trigger that spawns a session per ready task, a precheck that spends nothing when the queue is empty, and the rules each run follows. Use for a…
Skill Claude Code
Start the day with the state of everything that waits on the human or is ready to pick up: sessions that need input, pull requests with reviews or red checks, tasks ready to start, what teammates and overnight triggers did, unread team chat and mail. Use at the start of a working day, after time away, or when asked…
Skill Claude Code
Hand this session to a teammate so it lands in their inbox with everything they need. Pins where the work stands and what is next, adds them as an owner, and sends them the brief. Use when work should continue under someone else, when a decision is theirs, or when asked to pass, hand over, or assign a session.
Skill Claude Code
Rehydrate before working. Reads the bound task or plan, the pinned state, what the team did on this project recently, and the repository and tmux state, then names the work and the next three actions. Use at the start of a session, after a resume or compaction, or when asked to pick up work.
Skill Claude Code
Turn a request into a plan the team can review before code exists. Explores the codebase, searches prior sessions and recorded decisions for earlier attempts, interviews the user on the open questions, then writes a codecast plan with tasks and dependencies ready for orchestrate. Use when work has several parts, when…
Skill Claude Code
Stop and re-examine a piece of work from the top: what it was meant to be, what every earlier session did, which decisions constrain it, and whether the current direction still serves the intent. Reconstructs the history from the team's sessions, decisions and tasks before touching code. Use when a feature feels off…
Skill Claude Code
Review another session's work from its transcript and diff, then deliver findings to that session or its owner. Reads what the session was asked to do, what it changed, and how it verified, and reports correctness, missed requirements and risks with file and line. Use when asked to review a session, a teammate's work…
Skill Claude Code
Get an independent review of the current change from a different model in a fresh context, then verify its findings and fold the real ones in. Use before shipping, after a long debugging session, or when asked for another model's view.
Skill Claude Code
Take finished work through to merge. Commits in topical pieces, opens the pull request with a description that links the session, then binds this session to the pull request so review comments, failing checks and a stale branch wake it until the merge lands. Use when asked to ship, open a PR, or handle review…
Skill Claude Code
Build a standup or digest for a time window from the team's agent sessions, commits, tasks, pull requests, calls and chat. Use for a daily standup, a weekly retro, or when asked what happened since yesterday.
Skill Claude Code
Tidy the fleet of sessions so the inbox shows only what needs a person. Reads every session by who acts next, resolves the stalled ones, stashes the finished, kills the dead, and surfaces the few that need the human with a one line ask each. Use when the inbox is crowded, after a fan out, or when asked what all these…
Skill Claude Code
Prove the work before calling it done, and leave the evidence where reviewers read it. Runs the repository's checks, exercises the change in the human's own browser or on the command line, captures screenshots or output, attaches them to the task and the thread, and only then marks the work done. Use before declaring…
Skill Claude Code
Explain why a line of code is the way it is. Traces the line through cast blame to the codecast session that wrote it and the message where it was decided, then answers from the author's own reasoning. Use when asked why code looks like this, who wrote it and why, or what the intent behind a change was.
Skill Claude Code
Move this work into an isolated worktree with its own env files, ports and setup, so it cannot collide with other sessions in the shared checkout. Use before parallel work, before a risky change, when another session is editing the same files, or when asked to work in a worktree.
Skill Claude Code
Talk through the organization of agents and people around this work with the person, in this session: who reports to whom, what each role looks after, where their sessions go. Reads what the code and the sessions say before it trusts a plan or a task, asks what the records cannot settle, and posts each agreed change…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: