factory-batch-interactivity

Batch dependency-tiered user decisions into fewer agent handoffs for SDLC workflows.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-batch-interactivity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-batch-interactivity
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-batch-interactivity
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-batch-interactivity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the inefficiency of sequential one-question-at-a-time Q&A for commands requiring prolonged user interaction, which wastes agent handoff round trips, fragments context, and consumes unnecessary tokens during complex workflows like project setup or feature codesign.

Core Features & Use Cases

  • Tiered Decision Batching: Groups user decisions by dependency tier to reduce agent handoffs from 26+ to 3-4 for commands like SETUP --init, while preserving the familiar one-question-at-a-time user experience.
  • Conditional Navigation & Re-Harvesting: Pre-computes IF/THEN navigation rules to show, skip, or unlock questions automatically, and triggers partial agent re-harvesting only when users override pivotal decisions that impact downstream recommendations.
  • Resumable Workflows: Persists all batch and answer state to docs/.bip/ files, allowing interrupted prolonged interactive commands to resume exactly where they left off without restarting the entire decision process. Use Case: A team running SETUP --init for a new greenfield project completes all 26 required project configuration decisions with only 3-4 background agent handoffs instead of 26+, with no change to the familiar step-by-step user Q&A flow.

Quick Start

Use the factory-batch-interactivity skill to handle the prolonged user decision workflow for commands like SETUP --init, CODESIGN --start, or AUDIT --audit to reduce unnecessary agent handoffs while preserving the familiar one-question-at-a-time user experience.

Frequently Asked Questions about factory-batch-interactivity

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

FAQPage Schema
How do I reduce agent handoffs during prolonged Q&A workflows?

To reduce agent handoffs in prolonged Q&A workflows, batch user decisions by dependency tier. This method groups questions to cut round trips from 26+ to 3-4 while keeping the familiar one-question-at-a-time user experience.

What is conditional navigation in batch interactive decision workflows?

Conditional navigation in batch interactive workflows pre-computes IF/THEN rules to automatically show, skip, or unlock questions. It triggers partial agent re-harvesting only when users override pivotal decisions impacting downstream recommendations.

How do I resume interrupted SDLC interactive commands without restarting?

To resume interrupted SDLC interactive commands, use a workflow tool that persists batch and answer state to docs/.bip/ files. This allows prolonged interactive commands to resume exactly where they left off without restarting.

Can I use batch interactivity for project setup and codesign commands?

Yes, batch interactivity applies to governed agentic SDLC workflows including SETUP --init, CODESIGN --start, CODESIGN --vision, and AUDIT --audit that require extended user input across dependency-tiered decision batches.

What is the best way to handle multiple decision rounds in SDLC workflows?

The best way to handle multiple decision rounds in SDLC workflows is a two-layer batch and RDR communication model. It eliminates sequential one-at-a-time Q&A inefficiency, removing wasted agent handoff round trips and context fragmentation.

Why does sequential one-at-a-time Q&A waste tokens in agentic workflows?

Sequential one-at-a-time Q&A wastes tokens in agentic workflows because it fragments context and requires an agent handoff round trip for every single question, creating severe inefficiency during complex multi-step commands like project setup.