chief-of-staff

Automate PR merges, issue tracking, and pipeline lane dispatching for repository maintenance.

2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/adamaltmejd/registry-research-toolkit --skill chief-of-staff-adamaltmejd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chief-of-staff
Source: https://github.com/adamaltmejd/registry-research-toolkit/tree/main/.agents/skills/chief-of-staff
Command: npx skills add https://github.com/adamaltmejd/registry-research-toolkit --skill chief-of-staff-adamaltmejd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv, and includes scripts (resource) components.

What problem does it solve?

This skill solves the coordination overhead of managing a complex research repository by automating routine maintenance, PR merging, and pipeline scheduling.

Core Features & Use Cases

  • Automated PR Lifecycle: Merges ready pull requests, manages merge gates, and handles follow-up issue filing.
  • Pipeline Coordination: Monitors concurrency budgets, dispatches work lanes, and ensures dev previews remain current.
  • Issue Maintenance: Automatically updates issue metadata, priorities, and lane status to keep the project roadmap accurate.

Quick Start

Invoke the chief of staff skill to run one coordination tick and update the registry project state.

Frequently Asked Questions about chief-of-staff

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

FAQPage Schema
What is pipeline lane dispatching and how does it manage concurrency budgets?

Pipeline lane dispatching allocates concurrency budgets by monitoring available resources and dispatching work lanes sequentially. This ensures dev previews remain current and pipeline tasks execute without exceeding repository limits.

Do I need uv and git installed locally to run repository maintenance coordination?

Yes, local access to git and uv is required along with the repository's internal script suite. These dependencies execute the deterministic coordination tasks necessary for updating metadata database alignment.

How do I keep issue metadata and project roadmaps accurate automatically?

Issue metadata and project roadmaps are kept accurate by automatically updating issue priorities and lane status during each coordination tick. This ensures the roadmap reflects the current state of merged PRs and dispatched work lanes.

Can I use this coordination tool for Swedish registry microdata research pipelines?

Yes, the tool operates specifically within the context of Swedish registry microdata research to ensure consistent dev previews and metadata database alignment. It schedules repository maintenance tasks tailored to this research environment.

What's the best way to schedule dev previews and align a metadata database in a research repo?

Scheduling dev previews and aligning a metadata database is best handled by running a coordination tick that dispatches pipeline lanes and merges ready PRs. This deterministic process ensures previews remain current and metadata stays aligned.