Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By duronext
Orchestrate AI-driven team development pipelines across the full lifecycle: classify tickets, brainstorm designs, generate PRDs and TDD plans, execute parallel/serial implementations with quality gates, automate code reviews, create GitHub PRs, address feedback, and run post-mortems.
npx claudepluginhub duronext/jig --plugin jigUse when starting creative work — designing features, adding functionality,
Execute an implementation plan — analyzes task graph and picks parallel (team-dev) or serial (sdd) automatically.
Use when encountering any bug, test failure, or unexpected behavior, before
Use the `jig:eng-copywriting` skill to handle this request.
Use the `jig:eng-logging` skill to handle this request.
Use when committing code. Triggered by "commit the work", "commit this", or "commit with {name}". Reads jig.config.md for conventions, respects existing hooks, supports co-author resolution.
Use when reviewing code before opening a PR. Triggered by "review my code", "review my changes", or "run the review swarm". Dispatches the review swarm and produces a confidence-scored report.
Use when posting inline code review comments on a PR. Triggered by "post review comments", "leave feedback on PR", or "post inline comments". Pairs with code-review agent (analyze) then this agent (post).
Use when starting development work on a bug, feature, improvement, or task. Guides engineers through the full development pipeline: discover, brainstorm, plan, execute, review, ship. Invoked by "let's work on", "I need to build", "fix this bug", "start a new task", or /kickoff.
Use when starting creative work — designing features, adding functionality, modifying behavior, or exploring approaches. Guides collaborative design exploration through one-at-a-time questions, approach proposals, and incremental design approval. Hard gate: no code until design approved.
Use when capturing product requirements for features, improvements, or bugs before brainstorming or implementation. Triggered by "create a PRD", "capture requirements", "document requirements", "write a PRD", or /prd.
Use when you have an approved design or requirements for a multi-step task, before touching code. Turns designs into implementation plans with bite-sized TDD-oriented tasks, exact file paths, and verification steps. Save to docs/plans/.
Use when you have an implementation plan and want to execute it. Analyzes the plan's task graph, determines the best execution strategy (parallel via team-dev or serial via sdd), and orchestrates the full build with quality gates. The single entry point for plan execution — you don't need to choose between team-dev and sdd yourself.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Corca Workflow Framework — consolidated hooks and skill orchestration for structured development sessions
HelloAGENTS — The orchestration kernel that makes any AI CLI smarter. Adds intelligent routing, quality verification (Ralph Loop), safety guards, and notifications.
Persona-driven AI development team: orchestrator, team agents, review agents, skills, slash commands, and advisory hooks for Claude Code
Give soul to your workflow. 58 AI-powered skills across 17 roles — PM, Dev, Backend, Frontend, QA, UX, Data, Detect, WordPress, Release, Security, DevOps, and Core. Spec-to-ship pipeline: scaffold, implement, test, secure, deploy. Features two-phase workflow with human approval, quality-reviewer agent, token optimization, and continuous improvement via LEARN.md system.
Long-running agent harness with 5-layer memory architecture, GitHub integration, autonomous batch processing, Agent Teams with ATDD, 9 hooks (safety, quality gates, team coordination), and 6 Agent Skills
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
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.