kukuruyuk-writer

Generate a daily standup recap from impact-log entries and prior recaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered impact-log entries into a clear, concise daily all-hands standup update that the whole company can quickly understand.

Core Features & Use Cases

  • Daily kukuruyuk drafting: Produces a business-friendly update from today’s impact-log entries under the current date header.
  • Avoids repetition: References the last 2–3 prior kukuruyuk recap files so key items aren’t repeated unnecessarily.
  • Engineering-to-impact translation: Rephrases technical work into measurable outcomes (progress, blockers, customer/business effect) for a non-technical, whole-company audience.

Quick Start

Use kukuruyuk-writer to write my daily kukuruyuk from report/impact-log.md for today and save the confirmed draft to report/kukuruyuk-recaps/<YYYY-MM-DD>.md.

Frequently Asked Questions about kukuruyuk-writer

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

FAQPage Schema
How do I generate a daily standup update from impact-log notes?

You generate a daily standup update by processing report/impact-log.md entries; the Skill translates technical work into business impact and drafts a concise, Slack-ready all-hands update.

How does kukuruyuk-writer avoid repeating points in daily standup updates?

To avoid repeating points in daily standup updates, the Skill references the last 2-3 files in report/kukuruyuk-recaps/ to ensure previously reported items are excluded from the new draft.

Can I translate technical progress and blockers into business impact for a non-technical audience?

Yes, you can translate technical progress and blockers into business impact for a non-technical audience by rephrasing engineering work into measurable outcomes and customer effects suitable for a whole-company update.

What is the best way to format an engineering standup for Slack?

The best way to format an engineering standup for Slack is to summarize impact-log entries into concise, business-friendly progress and blockers, saving the confirmed draft to report/kukuruyuk-recaps/<YYYY-MM-DD>.md.

Do I need prior recap files to generate a daily kukuruyuk draft?

You do not need prior recap files to generate a daily kukuruyuk draft, but the Skill consults the last 2-3 files in report/kukuruyuk-recaps/ when available to prevent unnecessary repetition of key items.