convez.ai
MCP ServerDevOps & InfraestruturaAvançado
aryeko

Agentic Workflow Kit

aryeko/agentic-workflow-kit

Pipeline tracker-driven com drivers interativo e autônomo para entrega spec-first

Ver no GitHub
BomPluginScore · de 0 a 100

MCP server que transforma qualquer repositório em um pipeline de entrega orientado por tracker e spec-first. Fornece um driver interativo (skill de IA) e um orquestrador autônomo que compartilham um contrato declarativo em YAML e markdown, automatizando desde a definição do produto até o merge de PRs.

Instalação

$npx convez-ai aryeko/agentic-workflow-kit

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
100%
Último commit
há 3 meses
Versão
@agentic-workflow-kit/orchestrator@0.7.0
Issues abertas
7
Contribuidores
3

Casos de uso

  • Automatizar workflows de desenvolvimento end-to-end com políticas de PR/merge declarativas
  • Orquestrar múltiplas sessões de coding autônomo a partir de um tracker centralizado
  • Decomposição iterativa de PRDs em histórias rastreáveis e implementáveis

Veredito

Ferramenta sofisticada para times que buscam automação profunda de workflows de desenvolvimento. Requer arquitetura clara e disciplina de processo, mas oferece controle granular sobre orquestração, CI/CD e políticas de merge — ideal para repositórios complexos e equipes que precisam de entrega determinística e auditável.

README

A tradução para o português deste README ainda está na fila.

CI License: MIT Node >=24

A generic, OSS Claude Code + Codex plugin, with a bundled MCP runtime and optional standalone CLI, that turns any repo into a tracker-driven, spec-first delivery pipeline — and makes the per-repo differences (most notably PR/merge gating) declarative config rather than forked skills.

The core idea: one markdown tracker (a status matrix + dependency graph) plus one .workflow/config.yaml form a single contract that two interchangeable drivers read — an interactive "one story at a time" skill and an autonomous multi-session orchestrator.

Architecture

flowchart LR
  subgraph Author["Author (skills)"]
    PP[define-product] --> PA[design-technical-solution<br/>when needed]
    PP --> PT[plan-delivery-track]
    PA --> PT
  end
  WI[workflow-init] --> CFG
  PT --> TRK
  subgraph Contract["Shared contract (the spine)"]
    CFG[".workflow/config.yaml"]
    TRK["markdown trackers"]
  end
  CFG --> IN["implement-next<br/>(interactive)"]
  TRK --> IN
  CFG --> OR["bundled MCP runtime<br/>or CLI<br/>(autonomous)"]
  TRK --> OR
  OR --> CODEX["Codex MCP child sessions"]
  CODEX -. update .-> TRK

workflow-init scaffolds the config; define-product, design-technical-solution when needed, and plan-delivery-track produce the PRD, technical solution, and tracker. That config + tracker is the single contract both drivers consume. Completion authority is always the tracker row — never a child session's prose. Full detail and more diagrams in docs/architecture.md.

How it works

flowchart LR
  A["/workflow-init<br/>config + scaffolding<br/><i>(once per repo)</i>"] --> B["/define-product<br/>author PRD"]
  B --> C{"technical<br/>solution needed?"}
  C -->|yes| D["/design-technical-solution<br/>high-level technical how"]
  C -->|no| E["/plan-delivery-track<br/>tracker + briefs"]
  D --> E
  E --> F{Drive how?}
  F -->|interactive| G["/implement-next<br/>one story end-to-end"]
  F -->|autonomous| H["orchestrator run-eligible<br/>fan out child sessions"]
  G --> I["ship per pr: policy<br/>(create / CI / review / merge)"]
  H --> I
  I --> J{More eligible<br/>stories?}
  J -->|yes| F
  J -->|no| K["track complete"]
  1. Set up once — /workflow-init detects your package manager, CI, default branch, and branch protection, picks a PR/merge preset, writes .workflow/config.yaml, and scaffolds a tracks index plus an example tracker.
  2. Plan the product — /define-product runs a guided interview into a multi-file PRD.
  3. Design the technical solution when needed — /design-technical-solution turns complex PRDs into a technical solution document before story slicing.
  4. Decompose into a tracker — /plan-delivery-track turns the PRD, and technical solution when present, into a tracker plus story briefs.
  5. Implement — /implement-next takes one eligible story end-to-end (isolate → spec review → plan → implement → review → verify → ship), or workflow-autopilot uses the bundled MCP runtime to fan eligible stories out to Codex child sessions autonomously. The CLI provides the same runtime for local development, CI, and troubleshooting.
  6. Ship — under the declarative pr: policy (open a PR, wait on CI/review, auto-merge — or not), then repeat until the tracker is drained.

PR/merge presets

The one block that genuinely differs between repos is pr:. Pick a preset and go:

PresetWaits on CIWaits on reviewAuto-mergeMirrors
push-and-mergenonoyes (squash)a repo that ships fast
gated-automergeyesbot (e.g. codex)yes (squash)a repo with CI + bot review
push-onlynonono (open PR, stop)a repo with human review gates

Switch behavior by editing the pr: block in .workflow/config.yaml. See references/config-schema.md.

For the gated-automerge preset, pr.review.wait: bot with pr.review.bot: codex waits on Codex's GitHub reaction/comment signal: eyes means started or pending, thumbs-up means clear/no findings, and Codex PR review comments or PR comments are findings to triage when triageComments: true. It does not require Codex to submit a native GitHub approval.

Documentation

Install

Claude Code plugin

/plugin marketplace add aryeko/agentic-workflow-kit
/plugin install agentic-workflow-kit@agentic-workflow-kit

Codex plugin

Add the marketplace from the CLI (Codex docs), then install from the Codex plugin directory:

codex plugin marketplace add aryeko/agentic-workflow-kit

Restart Codex, then open the plugin directory, select the agentic-workflow-kit marketplace, and install the agentic-workflow-kit plugin (CLI equivalent: codex plugin add agentic-workflow-kit@agentic-workflow-kit).

Optional standalone CLI

pnpm add -D @agentic-workflow-kit/orchestrator

Local development

pnpm install
pnpm check
pnpm agentic-workflow-kit -- --help

Optional local Codex plugin smoke requires the Codex CLI. It is intentionally outside pnpm check so the default development gate works on machines that only have the package toolchain installed.

Local plugin testing

The repository includes local-only plugin metadata for development testing:

  • Claude Code: load this repo with claude --plugin-dir ./, then invoke namespaced skills such as /agentic-workflow-kit:workflow-init; the root .mcp.json wires the bundled MCP runtime.
  • Codex: .agents/plugins/marketplace.json is the marketplace manifest — the same one a public codex plugin marketplace add aryeko/agentic-workflow-kit reads. Locally you add it from the repo directory; it points at the materialized fixture at ./plugins/agentic-workflow-kit, including the fixture-specific .mcp.json and bundled mcp/server.mjs.
tmp_home="$(mktemp -d)"
CODEX_HOME="$tmp_home" codex plugin marketplace add .
CODEX_HOME="$tmp_home" codex plugin list
CODEX_HOME="$tmp_home" codex plugin add agentic-workflow-kit@agentic-workflow-kit
CODEX_HOME="$tmp_home" codex plugin list

The same Codex install and prompt-visibility check is available as:

pnpm smoke:codex-plugin

Keep manual plugin smokes pending until they are run in the relevant tool environment.

Layout

  • skills/ — the plugin's instructions and slash-command entry points.
  • references/ — the config schema (human + machine), tracker, PRD, technical solution contracts, and templates.
  • presets/ — the three starter configs.
  • examples/ — a worked PRD and tracker.
  • mcp/server.mjs — the bundled MCP runtime used by plugin installs.
  • packages/orchestrator/ — the TypeScript runtime source: the config schema, loader, presets, MCP server adapter, autonomous multi-session orchestrator, and standalone CLI.
  • docs/ — architecture, the docs hub, and the getting-started guide.

Project status

agentic-workflow-kit is published as v0.1.0: the six skills (workflow-init, define-product, design-technical-solution, plan-delivery-track, implement-next, workflow-autopilot), the bundled MCP runtime, the contracts, the three presets, the worked examples, and the optional standalone @agentic-workflow-kit/orchestrator CLI package (on npm) are implemented and covered by the test suite (pnpm check).

It is an early 0.x release — the install paths above are live. Feedback and issues are welcome as the agent-driven skills get broader real-world mileage.

Ver o original no GitHub

Bom para

Relacionados