kiwi-pipeline

Automate Kiwi workflow pipeline steps from event-driven triggers and user input.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiwi-pipeline
Source: https://github.com/Snoworca/speckiwi/tree/main/.agents/skills/kiwi-pipeline
Command: npx skills add https://github.com/Snoworca/speckiwi --skill kiwi-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Kiwi, Codex, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the orchestration of the Kiwi workflow pipeline, streamlining the development process and reducing manual intervention.

Core Features & Use Cases

  • Pipeline Orchestration: Automates the execution of Kiwi workflow steps based on event-driven triggers.
  • Event Analysis: Analyzes pipeline events to determine the next step in the workflow.
  • User and Auto-Gating: Provides options for user intervention or automatic execution based on predefined rules.
  • End-to-End Cycle: Supports full research-to-implementation cycles with conditional feasibility checks and worktree isolation.
  • Integration with Codex: Integrates with Codex for clarification gates and user input handling.

Quick Start

Run the kiwi-pipeline skill to automatically proceed with the next step in the Kiwi workflow pipeline.

Frequently Asked Questions about kiwi-pipeline

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

FAQPage Schema
How do I automate workflow pipeline orchestration for event-driven development cycles?

Workflow pipeline orchestration is automated by analyzing event-driven triggers and user input to determine and execute the next Kiwi workflow step, streamlining the full research-to-implementation development cycle.

Do I need Codex and Kiwi to parse and execute workflow events?

Yes, you need both Kiwi and Codex. Kiwi manages the workflow pipeline, while Codex integrates to handle clarification gates and user input during event parsing and conditional feasibility checks.

Can I run an end-to-end research-to-implementation pipeline with conditional feasibility checks?

Yes, the pipeline supports full end-to-end research-to-implementation cycles. It performs conditional feasibility checks and uses worktree isolation before proceeding with automated or user-gated execution steps.

How does event analysis determine the next step in a pipeline workflow?

Event analysis evaluates incoming pipeline events against predefined rules to decide the next workflow step. This mechanism allows options for either automatic execution or user intervention gating based on the event context.

What is the best way to reduce manual intervention in a development pipeline?

Automating the Kiwi workflow pipeline based on event-driven triggers minimizes manual intervention. It supports auto-gating rules and integrates with Codex for clarification gates to maintain control when needed.

When should I use user gating instead of automatic execution in pipeline orchestration?

Use user gating when pipeline events require manual clarification via Codex, and use automatic execution when predefined rules safely determine the next step in the workflow without needing user intervention.