monday-checkin-writer

Generate a weekly progress report from kukuruyuk recaps and impact logs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill monday-checkin-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monday-checkin-writer
Source: https://github.com/imsus/cto/tree/main/.agents/skills/monday-checkin-writer
Command: npx skills add https://github.com/imsus/cto --skill monday-checkin-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered daily recaps and impact notes into a clear weekly written company check-in, saving you time and reducing the chance of missing important signals.

Core Features & Use Cases

  • Signal-first weekly narrative: Produces a one-sentence insight at the top that highlights what the CEO/PM should know.
  • Structured progress draft: Summarizes Last week, sets Next week priorities, and captures Blockers / Notes.
  • Theme-based synthesis: Groups kukuruyuk entries into themes to remove operational noise while preserving impact and context.

Quick Start

Use the command monday checkin to generate a weekly progress draft from the most recent kukuruyuk recaps and impact log.

Frequently Asked Questions about monday-checkin-writer

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

FAQPage Schema
How do I turn daily updates into a weekly progress report?

This Skill generates a weekly progress report by reading kukuruyuk recap entries and the impact log, then synthesizing them into a narrative with themes. It structures the output into Last week, Next week, and Blockers sections for leadership communication.

What is the best way to write a CEO-ready company check-in?

Writing a CEO-ready company check-in involves producing a signal-first narrative with a one-sentence insight at the top. This Skill synthesizes kukuruyuk entries and impact logs into a structured draft with Last week, Next week, and Blockers sections.

How do I generate a monday checkin from scattered daily recaps?

Generating a monday checkin from scattered daily recaps requires reading kukuruyuk entries and the impact log. This Skill wraps recent updates into a narrative, optionally incorporating PM-sync changes, and drafts the report for confirmation before saving.

Does the weekly report require specific input data formats?

Yes, the weekly report requires kukuruyuk recap entries and an impact log as specific input data. It optionally incorporates PM-sync changes to enhance the theme-based synthesis before writing and persisting the draft.

Where does the monday checkin writer save the weekly report?

The monday checkin writer persists the weekly report to the path report/monday-checkins/<YYYY-W##>.md. After generating a draft for confirmation, it saves the final markdown file using the standard year and week numbering format.

Can I include PM-sync changes in the weekly progress report?

You can include PM-sync changes in the weekly progress report. The Skill optionally incorporates PM-sync data alongside kukuruyuk recap entries and the impact log to enrich the theme-based narrative synthesis before writing the draft.