The AI engineering workflow framework for teams.

Jig is a full-lifecycle development framework that guides AI agents through a structured pipeline — from ticket to post-mortem. Named after the manufacturing tool that holds workpieces and guides tools to produce consistent results, Jig aligns your entire team around shared conventions, quality gates, and development workflows.

Without a framework, teams end up with scattered AI skills, inconsistent workflows, and no shared conventions. Some engineers brainstorm before coding; others don't. Code review quality varies. Nobody's sure which skills exist or when to use them.

Jig fixes this the way Rails fixed web development: with strong opinions, sensible defaults, and a clear structure that everyone follows.

Full Pipeline — Every stage of development has a skill:

DISCOVER → BRAINSTORM → PLAN → EXECUTE → REVIEW → SHIP → LEARN

Parallel Execution — /jig:team-dev spawns parallel agent teammates with staggered quality gates. Your implementation plan runs in parallel, with spec compliance and code review at every step.

Review Swarm — /jig:review dispatches specialist reviewers in parallel (security, dead code, error handling, async safety, performance). Teams add their own domain-specific specialists.

Configurable, Not Rigid — jig.config.md lets you tune the pipeline per work type, define your concerns checklist, choose your ticket system, and set review policies. Override only what you need.

Extensible — Add domain skills (be-database, fe-react), custom specialists (typeorm.md, i18n.md), and team agents. They wire into the framework's discovery system automatically.

Add this to your project's .claude/settings.json — every teammate gets Jig automatically on clone:

{
  "enabledPlugins": {
    "jig@duronext-jig": true
  },
  "extraKnownMarketplaces": {
    "duronext-jig": {
      "source": {
        "source": "github",
        "repo": "duronext/jig"
      }
    }
  }
}

Commit that file. Done. Every teammate gets the full framework on clone — pipeline skills, review specialists, agents, and an engineering starter pack.

If you prefer the interactive approach:

# Add the Jig marketplace (one-time per user)
/plugin marketplace add duronext/jig

# Install for your whole team
/plugin install jig@duronext-jig --scope project

/jig:init       # Set up your project — guided interview, generates jig.config.md
/jig:kickoff    # Start working on a task — guides you through the full pipeline
/jig:extend     # Add your first team skill

/jig:init auto-detects your git host, branch, and commit conventions, then walks you through five questions to generate your jig.config.md and team directory structure. Type /jig: to see all available commands.

Clone the repo and reference the skills directly:

git clone https://github.com/duronext/jig.git .jig

See adapters/ for platform-specific integration guides.

Jig ships as a plugin with core skills, agents, and review specialists. Your team adds domain skills in .claude/skills/ that wire into the framework automatically.

Dispatched by /review as parallel subagents. Language-agnostic:

Teams add their own specialists in .claude/specialists/ (e.g., typeorm.md, i18n.md, graphql-contracts.md). The swarm discovers them automatically.

Ships with Jig. Three skills + one specialist for universal engineering practices:

Your domain expertise lives in .claude/skills/ in your project. These follow Jig's schema and wire into the framework:

• Glob-triggered: edit a database entity file → be-database skill auto-loads
• Concerns checklist: listed in jig.config.md → surfaces during /jig:brainstorm
• Review swarm: team specialists in .claude/specialists/ → dispatched by /jig:review
• Created with: /jig:extend scaffolds new skills with valid frontmatter

jig.config.md in your project root controls the pipeline:

## Team
name: Acme
platform: claude
git-host: github
ticket-system: linear
ticket-prefix: ENG

## Concerns Checklist
- i18n: .claude/skills/fe-i18n
- security: core/specialists/security
- test-strategy: manual

The concerns checklist surfaces during brainstorming — mapping your team's engineering concerns to specific skills. See framework/CONCERNS_CHECKLIST.md.

Jig is distributed as a Claude Code plugin. To get the latest version:

/plugin marketplace update duronext-jig
/plugin install jig@duronext-jig --scope project

Jig skills are platform-agnostic markdown. Adapters handle loading for:

• Claude Code (primary) — native plugin integration
• Gemini CLI — GEMINI.md context loading
• Codex — AGENTS.md integration

Teams using GitLab or Bitbucket are supported via the git host adapter.

Jig was extracted from Duro's new platform, where 31 battle-tested skills, 6 agents, and 10 specialist reviewers evolved into a comprehensive AI-assisted development system. Born from a hardware startup that knows what jigs do.

MIT