cool-down

Synthesize GitHub issues and project documentation into next-cycle work pitches.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/cmbays/mokumo --skill cool-down
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cool-down
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/cool-down
Command: npx skills add https://github.com/cmbays/mokumo --skill cool-down

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and templates (resource) components.

What problem does it solve?

This Skill helps you systematically review project progress, synthesize feedback, and generate actionable pitches for future work, ensuring continuous improvement and strategic alignment.

Core Features & Use Cases

  • Structured Retrospectives: Analyze accumulated feedback, project status, and recent work.
  • Forward Planning: Shape and propose new work items based on synthesized insights.
  • Use Case: After completing a development cycle, use this Skill to review user feedback from GitHub issues, identify key themes, and propose the top 2-3 features or improvements for the next cycle.

Quick Start

Run the cool-down skill to harvest feedback and synthesize new work candidates.

Frequently Asked Questions about cool-down

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

FAQPage Schema
How do I run a structured retrospective after a software development cycle?

Run a retrospective by synthesizing accumulated feedback and project state documentation to analyze recent work, identify key themes, and propose actionable improvements for the next development cycle.

What is the Shape Up methodology for project planning and synthesis?

The Shape Up methodology for project planning involves synthesizing feedback and project state to shape pitches, which are structured proposals for new work items to tackle in the next development cycle.

How do I synthesize GitHub issues to propose features for the next cycle?

Synthesize GitHub issues by harvesting user feedback from them, reviewing project status, and identifying key themes to shape and propose the top 2-3 features or improvements for your next cycle.

Can I use this approach to review project progress without a specific project management framework?

Yes, you can review project progress by analyzing accumulated feedback and recent work documentation, though the forward planning component specifically shapes pitches based on the Shape Up methodology.

What do I need to prepare before synthesizing feedback for forward planning?

Before synthesizing feedback for forward planning, you need access to GitHub issues, project progress documentation, and roadmap artifacts to properly inform the synthesis and shape new work pitches.