Pilot a versioned coordinator and subagent workflow

オープン
#8,989 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
docker
領域
devops, tooling

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
PHP
スター
844
フォーク
176
平均マージ
14時間 3分
マージ済み PR(30日)
344

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

LibreSign/libresign のほかの issue

LibreSign/libresign の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。