daily-sync

Aggregates Kanban board status, flags blockers, WIP violations, and stale tasks.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Zeyad-37/tech-agency --skill daily-sync-zeyad-37
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: daily-sync
Source: https://github.com/Zeyad-37/tech-agency/tree/main/.claude/skills/daily-sync
Command: npx skills add https://github.com/Zeyad-37/tech-agency --skill daily-sync-zeyad-37

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a multi-agent Kanban board accurate requires manually checking every column, cross-referencing git activity, and spotting stalled work. This Skill automates that daily check-in by reading the board through its configured backend and producing a structured status report. ## Core Features & Use Cases - Board Status Aggregation: Reads all columns (In Progress, Review, Blocked, Done) through the board adapter configured in .claude/settings.json, supporting both markdown and GitHub backends. - Health Checks: Flags agents exceeding the 2-item WIP limit, tasks stuck In Progress for more than 5 days, and blocked items with days-blocked counts. - Git Correlation: Runs git log to summarize recent commits grouped by agent and story, and cross-checks open PRs and branches on the markdown backend. - Use Case: A team lead starts the day by asking for a board status check and receives a formatted report with WIP violations, cycle-time alerts, blockers, and recommended actions such as unblocking or reassigning tasks. ## Quick Start Ask the assistant to run the daily sync and report the current board status with any blockers or stale tasks.

Frequently Asked Questions about daily-sync

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

FAQPage Schema
How do I run a daily Kanban board status check?▼

Invoke the daily sync by asking for a daily sync, board status, or check-in. It reads the board through the configured backend adapter, reviews recent handoff docs and git commits, then outputs a formatted report with WIP checks, cycle-time alerts, and blockers.

How does the daily sync detect stale or blocked tasks?▼

It reads the Cycle Day field on In Progress tasks and flags any exceeding 5 days, and reads Blocked Since on Blocked tasks to report days blocked. It also flags any agent exceeding the 2-item WIP limit.

Does the daily sync work with both markdown and GitHub board backends?▼

Yes. It checks board_backend in .claude/settings.json, defaulting to markdown when absent. On GitHub, counts are exact API writes; on markdown, in-flight work lives on unmerged branches, so it cross-checks open PRs and remote branches.

Can the daily sync update task statuses directly?▼

It applies corrections via board.update_task() and board.move_task() through the configured backend. On markdown, corrections are committed on the owning task's branch rather than main; uncommitted discrepancies are recorded in the report and raised with the owning agent.

Why does the markdown board under-report in-progress work?▼

In Progress and Blocked entries live on unmerged task branches, so the merged board only shows a lower bound of actual work. The sync compensates by cross-checking gh pr list and git branch -r, or you can migrate to the GitHub backend.