j2c-workflow
v1.0.2
Published
Jira to Code — modular, installable AI workflow system for Copilot and Cursor
Maintainers
Readme
J2C Workflow
Jira to Code — A modular, installable AI workflow system for GitHub Copilot and Cursor.
Teams install only the workflows they need. Each module does one thing. Everything composes.
Quick Start
npx j2c-workflow installFollow the interactive prompts. Workflows are installed in under 2 minutes.
What It Does
J2C gives your AI coding assistant a structured, step-by-step workflow from Jira ticket to merged PR — with safety gates, quality checklists, and full traceability built in.
implement LPA-12345
│
├─ Validates ticket completeness
├─ Generates an executable spec
├─ Designs a test plan
├─ Requires your approval before coding
├─ Implements tests + code
├─ Self-reviews against a quality checklist
├─ Creates a PR with full AC traceability
└─ Updates Jira to "In Code Review"Or, for quick tasks:
setup LPA-12345 ← branch + Jira "In Progress"
# ... code ...
finish ← commit + PR + Jira "In Code Review"Module System
J2C is built from 16 independent modules organized into three tiers:
| Tier | Modules | Description | |------|---------|-------------| | Core | 6 | Always installed. Git sync, Jira fetch, commit, PR, Jira update, quality checklist. | | Optional | 7 | Opt-in. Repo analysis, ticket validation, branch discovery, TDD, approval gate. | | Advanced | 3 | For complex teams. Spec drafting, spec validation, implementation planning. |
And three pre-composed pipelines:
| Pipeline | Trigger | Best For |
|----------|---------|---------|
| implement | implement LPA-XXXXX | Complex features, API changes, multi-component work |
| setup-finish | setup + finish | Bug fixes, small tasks, exploratory work |
| pr-only | pr LPA-XXXXX | Code written outside workflow |
Installation
# Interactive install
npx j2c-workflow install
# Non-interactive (CI/CD)
npx j2c-workflow install \
--platform copilot \
--pipeline setup-finish \
--jira-cloud-id YOUR_CLOUD_ID \
--jira-url https://your-org.atlassian.net/browse/ \
--modules tool-activate,branch-discovery,jira-validate \
--yes
# Add a module after install
npx j2c-workflow add repo-analysis
# See what's installed
npx j2c-workflow list
# Upgrade to latest
npx j2c-workflow upgradeSee INSTALL.md for the full installation guide.
Custom Workflows
Teams can create their own workflow modules and inject them into any pipeline:
# During install — creates copilot-rules/custom/security-scan.md from template
npx j2c-workflow install # → "Add a custom workflow? yes" → "security-scan"
# After install
cp templates/custom-workflow.md copilot-rules/custom/security-scan.md
# Edit the file, then reference it in your pipelineCustom modules follow the same schema as built-in modules and can be inserted at any point in any pipeline.
Repository Structure
j2c-workflow/
│
├── package.json ← npm package, bin: j2c
├── README.md ← This file
├── INSTALL.md ← Full installation guide
│
├── copilot-rules/ ← Workflow content (the AI instructions)
│ ├── README.md ← Workflow architecture map
│ ├── modules/
│ │ ├── core/ ← 6 core modules + module.yaml manifest
│ │ ├── optional/ ← 7 optional modules + module.yaml manifest
│ │ └── advanced/ ← 3 advanced modules + module.yaml manifest
│ └── pipelines/ ← 3 pipeline compositions + module.yaml
│
├── tools/ ← CLI installer
│ ├── j2c-npx-wrapper.js ← npx entry point
│ └── cli/
│ ├── j2c-cli.js ← CLI with install|add|list|upgrade commands
│ ├── commands/
│ │ ├── install.js ← Interactive installer (clack/prompts)
│ │ ├── add.js ← Add single module post-install
│ │ ├── list.js ← List modules and status
│ │ └── upgrade.js ← Upgrade installed modules
│ └── lib/
│ ├── installer.js ← File copy + platform config logic
│ ├── module-registry.js ← Module manifest loader
│ └── config-writer.js ← j2c.config.yaml generator
│
└── templates/
├── j2c.config.yaml ← Team config template
└── custom-workflow.md ← Custom module starter templateLicense
MIT
