inquiry

Files (7)

• README.md
• SKILL.md
• __init__.py · scripts/
• consensus_builder.py · scripts/
• debate_structurer.py · scripts/
• phase_manager.py · scripts/
• synthesis_generator.py · scripts/

SKILL.md (first lines)

# Skill: Inquiry Orchestration

You are the Inquiry Orchestration agent. Your goal is to guide INQ work items through all four deliberation phases—Research, Synthesis, Debate, and Consensus—coordinating multiple agents to reach well-reasoned decisions.

## Overview

The `/inquiry` skill manages the complete lifecycle of an INQ (Inquiry) work item:

1. **Phase 1: Research** - Spawn independent agents to explore the problem space
2. **Phase 2: Synthesis** - Consolidate findings into unified understanding
3. **Phase 3: Debate** - Resolve conflicts through structured argumentation
4. **Phase 4: Consensus** - Formalize decisions and spawn FEAT work item(s)

## Usage

```bash
# Start or continue an inquiry
/inquiry INQ-001

# Start a specific phase
/inquiry INQ-001 --phase research
/inquiry INQ-001 --phase synthesis
/inquiry INQ-001 --phase debate
/inquiry INQ-001 --phase consensus

# With agent configuration
/inquiry INQ-001 --agents 5 --model claude

# Fallback mode (no ccmux)
/inquiry INQ-001 --mode manual
```

## Arguments

| Argument | Required | Description |
|----------|----------|-------------|
| `inquiry_id` | Yes | The inquiry ID (e.g., INQ-001) or path to inquiry directory |
| `--phase` | No | Start/resume at specific phase (auto-detects if omitted) |
| `--agents` | No | Number of research agents (overrides inquiry_report.json) |
| `--model` | No | Model for spawned agents (claude, gemini, codex) |
| `--mode` | No | Execution mode: `ccmux` (default) or `manual` |
| `--timeout` | No | Timeout per phase in seconds (default: 600) |

## Workflow

### 1. Initialization

Read `inquiry_report.json` to determine:
- Current phase and status
- Number of research agents required
- Constraints and context

```bash
# Locate inquiry
INQUIRY_PATH=$(find_inquiry "$1")

# Load configuration
inquiry_report.json → phase, status, research_agents, constraints
```

### 2. Phase Detection

Automatically detect which phase to execute based on:
- Current `phase` field in inquiry_report.json
- Existence of phase artifacts (research/, SYNTHESIS.md, DEBATE.md, CONSENSUS.md)

```
if phase == "new" or phase == "research":
    → Execute Phase 1: Research
elif phase == "synthesis":
    → Execute Phase 2: Synthesis
elif phase == "debate":
    → Execute Phase 3: Debate
elif phase == "consensus":
    → Execute Phase 4: Consensus
elif phase == "completed":
    → Report completion, show spawned features
```

---

## Phase 1: Research

**Goal**: Gather diverse perspectives through parallel, independent exploration.

### With ccmux (Recommended)

1. **Generate Prompts** via `/inquiry-prompts`:
   ```bash
   /inquiry-prompts $INQUIRY_PATH --algorithm round-robin --output json
   ```

2. **Spawn Research Agents**:
   ```
   For each agent prompt:
     ccmux_create_session(
       name: "inq-{inquiry_id}-agent-{N}",
       command: "claude --dangerously-skip-permissions",
       tags: ["worker", "{inquiry_id}"]
     )
     ccmux_send_input(pane_id, prompt)
   ```

3. **Monitor Completion** via `/inquiry-collect`:
   ```bash
   /inquiry-collect $INQUIRY_ID --mode ccmux --timeout $TIMEOUT
   ```

4. **Update Status**:
   ```json
   {
     "phase": "synthesis",
     "status": "synthesis",
     "phase_history": [
       {"phase": "research", "entered_date": "...", "notes": "Completed N/N agents"}
     ]
   }
   ```

From brendanbecker/featmgmt, MIT.

More from brendanbecker/featmgmt