ginee-iterate

Forward user review replies verbatim to the active warm cardinal.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-iterate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ginee-iterate
Source: https://github.com/kostiantyn-matsebora/ginee/tree/main/core/skills/ginee-iterate
Command: npx skills add https://github.com/kostiantyn-matsebora/ginee --skill ginee-iterate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Relay a user review reply to the warm cardinal who owns the in-flight task, verbatim, avoiding edits in the main thread.

Core Features & Use Cases

  • Verbatim forwarding of user replies to the warm cardinal without modification.
  • Surface the cardinal's response unsynthesized back to the user for review.
  • Hand back to @team-lead when triggers indicate routing changes or task state updates.
  • Supports multi-match routing decisions to escalate to the team-lead when needed.

Quick Start

To use this skill, invoke ginee-iterate to forward the current user reply to the active warm cardinal without editing the main thread.

Frequently Asked Questions about ginee-iterate

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

FAQPage Schema
How do I relay user review replies to the active task owner without editing the main thread?

To relay user review replies verbatim, forward the message to the warm cardinal owning the in-flight task. This prevents main thread edits and surfaces the cardinal's unsynthesized response directly back to the user for iterative review.

When do I need to hand off a routed task back to the team-lead?

You need to hand off a routed task to the team-lead when triggers like open issues, hand-offs, status changes, or routing updates occur. Multi-match routing decisions also escalate back to the team-lead for resolution.

What is verbatim message forwarding for iterative review routing?

Verbatim message forwarding for iterative review routing detects the live warm cardinal and transmits the user reply without modification. It enables routing decisions by surfacing the cardinal's unedited response for review.

Can I use verbatim forwarding if the warm registry does not contain an active cardinal?

No, verbatim forwarding applies only when the warm registry contains an active cardinal whose ownership covers the surface the reply targets. Without an active cardinal, the routing condition is not met.

Does the relayed response get synthesized before returning to the user?

No, the relayed response is surfaced unsynthesized back to the user. The warm cardinal's reply returns verbatim, ensuring the user reviews the exact output without synthesis or modification.

Why does the warm cardinal approach avoid editing replies in the main thread?

The warm cardinal approach avoids editing replies in the main thread by forwarding the user message verbatim to the task owner. This preserves the original context and enables iterative review without altering main thread content.