Pilot a versioned coordinator and subagent workflow

Open
#8,989 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker
Domain
devops, tooling

Research direction

No implementation files, orchestrator, entry points, or tests are named. Start by identifying the reusable skills and isolated execution environment referenced in the issue, then determine where coordinator configuration can be versioned and how representative trials will be run. Done means the workflow is reproducible, has hosted versus self-hosted criteria, and records the listed evaluation measures.

Written by the indexing model from the issue text.

Description

Goal

Pilot a small, versioned agent-orchestration workflow for LibreSign after the reusable skills and isolated development environment are available.

Runtime dependency

Use a runtime that provides genuinely separate subagent contexts. The current reference implementation is the OpenAI Agents API multi-agent capability. Do not emulate subagents with repeated sequential prompts or duplicated analysis in one context.

This dependency is independent from Behat and from LibreSign's test-suite modernization.

Approach

Start with one coordinator that can delegate independent work to temporary subagents with separate context.

Do not create permanent specialized agents for every engineering role.

Candidate parallel tasks include:

  • independent investigation of an issue;
  • review of a completed diff with clean context;
  • targeted test/compatibility research that does not depend on another subtask's intermediate state.

Sequential work whose next step depends on the previous output should normally remain in one execution flow.

Execution environments

Use hosted execution for ordinary repository work where it is sufficient.

Use self-hosted/persistent execution only when the task needs capabilities such as:

  • the canonical Docker/Nextcloud environment;
  • multiple isolated worktrees;
  • long-lived Docker image/cache reuse;
  • browser/integration tests requiring a real local service topology.

Self-hosting must not become a mandatory transfer hop for all work.

Versioning

Keep coordinator instructions/configuration in version control with explicit inputs, allowed tools, handoff rules and evaluation cases.

Do not add WORKFLOW.md or SPEC.md merely for convention. Introduce a workflow/spec file only if the chosen orchestrator actually consumes it.

Evaluation

Compare the pilot with a single-agent flow on representative tasks, recording at least:

  • completion correctness;
  • human interventions required;
  • wall-clock latency where measurable;
  • duplicated/repeated work;
  • tool failures/handoffs;
  • token/model cost where available.

Done when

  • The coordinator workflow is versioned and reproducible.
  • Subagents are used only for genuinely independent work.
  • Hosted versus self-hosted execution has a concrete decision rule.
  • Representative trials show whether orchestration reduces manual coordination without adding a new bottleneck.
Dominant language
PHP
Stars
844
Forks
176
Avg merge
14h 3m
Merged PRs (30d)
344

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LibreSign/libresign

All issues in LibreSign/libresign

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.