jmagly

AIWG: Reusable Workflows for AI Coding Tools

AIWG provides reusable project context, specialist agents, and workflows for tools including Claude Code, Codex, Copilot, and Cursor. Its TypeScript CLI deploys these assets across providers and supports persistent project artifacts, reviews, and optional decision support.

Stars
224
Forks
34
Stars, last 30 days
+9
Last commit
today
Contributors
5

Our take

Activeregular commits and releases

Health score

63/100

How it is scored
Activity
90
Community
16
Issues
95
Pull requests
51

+9 stars in the last 30 days

  • Releases more often than 93% of the projects we track
  • Closes issues faster than 81% of the projects we track

AIWG is a broad, actively maintained workflow toolkit for teams that want portable AI instructions and durable project artifacts, but its development is highly concentrated in one contributor.

Good fit if

  • You use a supported AI tool and want project context and workflows deployed into its native instruction paths.
  • Your work spans sessions and benefits from saved requirements, decisions, reviews, or runbooks.
  • You can use Node.js 24 or newer and want an MIT-licensed toolkit with frequent updates.

Look elsewhere if

  • You need a bundled AI model or expect AIWG itself to execute every workflow independently of your provider.
  • You need project changes to be maintained by a broadly distributed contributor base; most recent work comes from one person.
  • You only need an occasional one-off answer and have no need for reusable workflows or saved project artifacts.
All health signals
Last commit2026-10-20 (today)
Commits, last 90 days100+
Releases, last 12 months100+ (latest v2026.10.3, 2026-10-15)
Contributors5 (top contributor: 100% of commits)
Issues closed, last 90 days67+ (typically closed in 0 days)
Pull requests merged, last 90 days29 (typically merged in 1 day)
Project age14 months

Checked on 2026-10-20 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

229

Forks

35

Change since Nov 5, 2026: +1 stars·+1 forks

Overview

AIWG is a TypeScript toolkit for reusable project context and specialist workflows across AI tools such as Claude Code, Codex, Copilot, and Cursor. It addresses the loss of project decisions between sessions by organizing work into reusable instructions and saved artifacts, while letting teams use their existing AI provider.

Its CLI deploys agents, skills, rules, and templates into provider-readable locations. Workflows can share project artifacts in .aiwg/, coordinate specialist reviews, and support tasks across software development, research, operations, and other domains. AIWG supplies procedures and tools, not a model of its own; provider capabilities and optional integrations determine what can run.

Key Features

  • Deploy shared workflow assets to multiple AI providers with aiwg use.
  • Save project-specific requirements, decisions, reviews, and other artifacts in .aiwg/ for later sessions.
  • Use specialist agents and skills for software delivery, security, testing, research, marketing, forensics, and operations.
  • Structure reviews as authoring, specialist feedback, synthesis, and human approval where supported.
  • Run bounded agent loops with verification, checkpoints, and recovery options.
  • Use optional Jev decision support to handle bounded choices such as gates or severity scores, with fallback to the assistant's reasoning.
  • Extend the installed capabilities with project-local frameworks, addons, and other custom assets.

Use Cases

  • Engineering teams can retain requirements and architecture decisions across sessions, then use them to guide implementation and review.
  • Technical leads can organize security, performance, and testability feedback around a shared design artifact before approving a change.
  • Researchers can maintain source-linked notes and reuse them in later synthesis work.
  • Operators can prepare deployment runbooks, monitoring checks, and rollback plans before a production change.
  • Individual developers can install a focused workflow for a bounded review or writing task without adopting a full project lifecycle.

What you need

Detected in the repository

  • Node.js >=24 (from package.json)
  • A test suite and automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

With Node.js 24 or newer, install and deploy the complete asset set:

npm i -g aiwg
cd /path/to/your/project
aiwg use all --provider claude

Replace claude with your provider selector. See the README for setup guidance, supported providers, and framework choices.

Alternatives

  • compound-engineering-plugin: Focuses on an end-to-end cycle of brainstorming, planning, implementation, review, and captured learnings rather than deploying broader project context and specialist agents.
  • agent-skills: Provides skills for specification, implementation, review, testing, and sprints, rather than a CLI for deploying project context and workflows across providers.
  • agent-skills: Offers a portable Markdown skill pack for engineering workflows, rather than project artifacts and a TypeScript deployment CLI.
  • agent-feed: Installs repository-owned instructions, task and review gates, and tool adapters, rather than a broader library of project context and specialist agents.
ProjectLanguageLicenseStarsStatus
AIWGTypeScriptMIT224Active
compound-engineering-pluginTypeScriptMIT25.4kActive
agent-skillsShellMIT2Active
agent-skillsJavaScriptMIT109kActive
agent-feedPythonMIT4Quiet

Considerations

  • AIWG is actively developed, with regular commits and releases and recent issue and pull-request activity. However, its contributor base is small and work is overwhelmingly concentrated in one person, creating a maintainer-dependency risk.
  • Node.js 24 or newer is required. The base install excludes some native features that require explicit opt-in; those features are not necessary for core deployment.
  • Installing workflow assets does not start optional servers, storage services, or orchestration components. Those have separate prerequisites and configuration.
  • Provider support varies. A role definition is not a separate model, and a written rule does not by itself enforce a constraint. Parallel reviews and recovery behavior depend on the provider and environment.
  • The project describes its workflows as support for review and verification, not a guarantee of correct results, citations, or unattended completion.

Found this useful?

Share it with someone who would like AIWG.

Comparisons