AI-Powered SDLC Platform
Jira Workflow Kit
From business idea to merged PR.
For your whole team. From the browser.
> /idea
+
🎤 "Run standup"
The Problem
AI-driven development is locked away
📝
Hard to get right
Stakeholders know what they want — but writing testable acceptance criteria takes time and expertise
🔄
Slow feedback loops
Weeks between requirement and implementation. Stakeholders lose context, developers lose momentum
😴
Idle capacity
Approved tickets sit in the backlog. Developer machines idle 16 hours a day. Time zones don't align.
🔒
CLI-only barrier
Today's AI dev tools require terminal expertise. 80% of your team — POs, BAs, stakeholders — are locked out.
The Solution
One platform. Every role. No CLI.
Jira Workflow Kit is a web-based SaaS platform where your entire team participates in AI-driven development.
Admin configures. Developers build. Business gives input.
Nothing happens without human approval.
The Unfair Advantage
AI knows your entire codebase
When a business user submits an idea, AI analyzes every file, every pattern, every dependency.
It writes Epics and Stories with technically precise acceptance criteria.
No human BA in the world can do this. They don't know the code. AI does.
Requirement
"Add two-factor authentication to the login"
Acceptance Criteria
"User can enable 2FA on their account"
Missing context
Which auth flow? Which models? Which endpoints? Unknown.
vs
Story 1
Add TotpSecret model with migration, relate to existing User model via hasOne
Story 2
Create POST /api/auth/totp/enroll endpoint using existing AuthController pattern
Story 3
Add TOTP verification step to LoginRequest validation, following existing FormRequest pattern
Requirements that developers can build immediately. No back-and-forth. No ambiguity.
Role-Based Access
Three roles. One platform.
🔐
Admin
- Connect Jira, Git, Claude API keys
- Manage users and custom roles
- Configure Project Registry
- View audit logs and billing
- Enforce MFA and security policies
💻
Developer
- /plan, /develop, /qa, /deploy
- /bug, /autopilot, /standup
- Full development lifecycle
- View agent progress in real-time
- Cannot modify tenant configuration
💡
Business
- /idea — submit feature requests
- /status — simplified sprint view
- /feedback — provide input in Jira
- No code, no technical details
- Focus on requirements and outcomes
18 granular permissions. Custom roles. Admin is immutable — can never lock yourself out.
The Interface
Chat UI with streaming output
AI
Starting development of MVP-42: Customer login with 2FA
✓ Reading ticket from Jira...
✓ Analyzing codebase patterns...
✓ Subtask 1/5: Add TOTP model — committed & pushed
▶ Subtask 2/5: Create enrollment endpoint...
WebSocket streaming via Laravel Reverb. Real-time agent output.
No terminal. No SSH. Just your browser.
Core Principle
Human in the loop — always
💡
Business submits idea/idea
↓
👤
Dev team reviewsRequirements check
↓
✅
Human approvesNothing starts without this
GATE
↓
🤖
AI builds/plan → /develop → /qa
↓
👤
Human reviews PREvery change reviewed
GATE
↓
✅
Human mergesOnly by human decision
GATE
↓
Approval Gate
No code without "Approved" status. AI can never approve. Your organization defines the approver — PO, Business, IT-Sec, or a custom role.
Feedback Loop
Before approval, stakeholders iterate in Jira. Comments, requirement changes, scope adjustments. AI processes every update via /feedback.
QA Gate
Independent AI agents review. Writer never reviews own code. UX, Security, and QA checks before any PR.
PR Review
Every change is a Pull Request. Only a human can merge. No direct commits to main. No exceptions.
AI can never approve its own work. AI can never merge its own code.
Customizable
Your approval process. Your rules.
Config A — Simple
Single Product Owner approval. Fast and lean for small teams.
Config B — Dual Approval
Business
+
IT-Sec
→
AI builds
Both Business and IT-Security must approve. For regulated environments.
Config C — Custom Role
Dedicated Release Manager or any custom role your org defines.
Define your approval chain in Jira. Every organization is different.
JWK respects your existing workflow. No changes to your process required — AI integrates into it.
Feedback Loop
Before approval — a real conversation
Stakeholders refine requirements in Jira. AI adjusts automatically via /feedback.
Real conversation. Real adjustments. Before any code is written.
How It Works
From idea to PR — through the browser
> /idea "Customers need 2FA on login"
→
→
> /plan PROJ-42
→
> /develop PROJ-42
→
> /qa PROJ-42
→
Every step documented in Jira. Every commit linked to a subtask.
Live Board
Your Jira board — always in sync
📖 PROJ-48
Export reports as PDF
☑ PROJ-51
Optimize DB indices
📖 PROJ-47
Customer notification preferences
📖 PROJ-42
Customer login with 2FA
🐛 PROJ-50
Fix timezone offset in scheduler
📖 PROJ-43
Role-based dashboard widgets
📖 PROJ-44
Multi-currency invoice support
📖 PROJ-40
Email template engine
📖 PROJ-39
GDPR data export
Full Traceability
Every decision documented in Jira
Acceptance Criteria
✓ TOTP-based 2FA with QR enrollment
✓ Recovery codes (10, single-use)
▶ Remember device for 30 days
○ Rate limiting: 5 attempts per minute
○ Admin can reset user 2FA
Subtasks
✓
PROJ-52
Add TOTP model and migration
✓
PROJ-53
QR enrollment endpoint
▶
PROJ-54
Verification middleware
PROJ-55
Recovery code generation
PROJ-56
Device remember cookie
Multi-Agent Collaboration
A full team. Per ticket.
🤖
Lead Architect
Opus
Plans implementation, coordinates the team, resolves conflicts. Final authority on architecture.
💻
Backend Dev
Sonnet
APIs, database design, business logic. Implements subtask by subtask with auto-push.
🎨
Frontend Dev
Sonnet
UI components, state management, API integration. Works in parallel with backend.
👁
UX Lead
Opus
Accessibility, design patterns, user flows. Reviews plan and final code independently.
🔒
Security Lead
Opus
OWASP, GDPR compliance, vulnerability detection. MEDIUM+ findings = hard block.
🔎
QA Lead
Opus
Acceptance criteria validation, edge cases, code review. Devil's advocate mindset.
The agent that writes the code never reviews it. Right-sized teams: 1 agent for trivial tasks, 6 for complex features.
Game Changer
/autopilot
Your team goes home. A full AI team keeps working.
6 specialized agents per ticket — overnight, from the platform.
Agent Team per ticket
- Lead Architect plans and coordinates
- Backend + Frontend devs work in parallel
- UX Lead reviews every deliverable
- Security Lead audits for vulnerabilities
- QA Lead validates acceptance criteria
- Writer never reviews own code
When stuck
- Documents the question in Jira
- Parks the ticket for team review
- Moves to the next ticket
- Right-sizes teams by complexity
- 1 agent for trivial — 6 for complex
- Never guesses — asks via Jira
The Morning After
Wake up to /standup
AI
Good morning. Here's what happened:
Autopilot overnight:
Completed: PROJ-42, PROJ-43, PROJ-44
Parked: PROJ-45 (needs input)
Sprint: 3/5 done, 1 parked
Recent: 11 commits across 2 projects
📱 Mobile — Voice Mode
🎤
"Run standup"
🔈
"Good morning. Autopilot completed 3 tickets overnight. PROJ-45 is parked — needs your input on notification handling. Sprint is at 60%."
Same data. Spoken back. Hands-free.
Complete Toolkit
14 skills, full lifecycle
| Command | Purpose | Mode | Roles |
|---|
| /idea | Structure requirements → Epic + Stories in Jira | Interactive | All |
| /feedback | Process stakeholder feedback from Jira comments | Interactive | All |
| /status | Sprint overview or ticket detail | Read-only | All |
| /plan | Codebase analysis → implementation subtasks | Interactive | Dev |
| /develop | Implement subtask by subtask with auto-push | Interactive | Dev |
| /qa | Test, validate acceptance criteria, create PR | Interactive | Dev |
| /ux-review | Independent UX review of developed code | Review | Dev |
| /security-review | Security audit (OWASP, GDPR, vulnerabilities) | Review | Dev |
| /bug | Investigate root cause, quick-fix or ticket | Interactive | Dev |
| /vibe | Pragmatic mode — work first, document later | Pragmatic | Dev |
| /autopilot | Autonomous overnight development (Agent Teams) | Autonomous | Dev |
| /standup | Morning briefing with overnight summary | Read-only | Dev |
| /deploy | Build, test, deploy a project | Interactive | Dev |
| /retro | Sprint wrap-up + learning capture | Interactive | Dev |
Role-based access. Business sees /idea, /status, /feedback. Developers get the full toolkit.
Flexibility
Two modes. Same platform.
Formal Pipeline
Full SDLC with quality gates. Every step documented, every decision traced.
/idea
→
Approve
→
/plan
→
/develop
→
/qa
→
PR
Best for: features, planned work, regulated environments
Vibecoding
Work first, document later. Build it together, then retroactively create Jira tickets.
Build together
→
/vibe doc
→
Epic + tickets
→
Done
Best for: prototyping, quick fixes, exploratory work
Jira stays the source of truth — whether you document before or after.
Continuous Learning
The AI gets better — per tenant
Three-layer memory system. Platform knowledge ships with the product.
Your team's patterns and project conventions build up over time.
Platform Memory
Read-only. Ships with the base image. Skills, workflow rules, best practices.
CLAUDE.md
commands/*.md
Updated with every release
Tenant Memory
Read-write. Persistent across sessions. Your team's conventions and preferences.
MEMORY.md
working-style.md
debugging.md
Project Memory
Read-write. Per project. Architecture patterns, known issues, tech stack details.
diemcrm.md
mobile-app.md
Knowledge compounds
Architecture
Container per tenant. Full isolation.
→
🌐
Web App
Laravel + Vue 3
Auth, Billing, API
→
📦
Tenant A
JWK Engine + MCP
Git workspace
📦
Tenant B
JWK Engine + MCP
Git workspace
→
📋
Jira
Customer's instance
🐙
GitHub
Customer's repos
🤖
Claude
Customer's API key
Each tenant runs in its own Docker container. Separate filesystem, network namespace, resource limits.
Code is cloned, processed, pushed, then purged. Never persisted on our servers.
Enterprise Security
NIS2 compliant. Enterprise-grade.
🔐
Mandatory MFA
TOTP-based two-factor authentication for all users. Google Authenticator compatible. No exceptions.
📜
Immutable Audit Logs
Every action logged with timestamp, user, IP, and detail. 3-year retention. Append-only — cannot be modified or deleted.
📦
Container Isolation
Dedicated Docker container per tenant. CPU + RAM limits. No inter-container communication. Network restricted to customer services.
🛡
Data Protection
Credentials AES-256 encrypted at rest. Code ephemeral only. GDPR-compliant IP logging with documented legal basis.
Granular RBAC with 18 permissions. Custom roles. Immutable Admin role — can never lock yourself out.
Customer Ownership
Your keys. Your control.
🤖
Claude API Key
Your key, your usage, your spend. Or use Claude Max per user. We never see your prompts.
📋
Jira Instance
Your Atlassian Cloud. Your projects, your boards, your workflows. We connect — we don't store.
🐙
Git Repos
Your GitHub or GitLab. Code is cloned into ephemeral containers, pushed to your remote, then purged.
No vendor lock-in for your data. No AI training on your code.
You bring the credentials — we bring the orchestration.
Pricing
Per-seat. Predictable. Fair.
Starter
$49
per seat / month
- Up to 5 seats
- All 3 roles
- 1 project
- 14 skills
- Community support
Team
$39
per seat / month
- Up to 20 seats
- All 3 roles + custom roles
- 5 projects
- 14 skills + priority updates
- Email support
Enterprise
Custom
contact us
- Unlimited seats
- SSO / SAML (Phase 2)
- Unlimited projects
- Dedicated support + SLA
- On-prem option (Phase 3)
You bring your Claude API key + Jira + Git. We bring the platform.
German + English from day one.
Battle-Tested
8 projects. Proven foundation. Now for everyone.
💻
DiemCRM
Laravel, Filament, Vue 3
📱
Meridiem Mobile
SwiftUI, React Native, Node.js
⚙️
MCP Server
Node.js, TypeScript, MCP SDK
🔍
SiteMedic
TypeScript, Playwright, Vitest
💰
Invoice Exporter
Python, httpx
🏠
Home Server
ioBroker, Grafana, evcc
🎬
Pitch Deck
HTML, Docker
The engine behind the SaaS platform is battle-tested across 8 real projects.
Per-project AI memory. Per-project conventions. One board, full visibility.
Impact
Before vs. After
Without
- AI dev tools require CLI expertise
- Only engineers can participate
- BAs write vague requirements manually
- Weeks from idea to working code
- Jira status always outdated
- No work happens outside business hours
- Every session starts from zero
→
With JWK SaaS
- Web UI — no CLI needed
- Business, Developer, Admin — everyone contributes
- AI helps write structured, testable tickets
- Hours from approval to PR
- Jira always in sync, automatically
- Autopilot develops overnight
- Three-layer persistent memory per tenant
The Output
PRs ready for review — by morning
Summary
- Add TOTP-based two-factor authentication to customer login flow
- QR code enrollment endpoint for initial 2FA setup
- Recovery codes (10 single-use, auto-generated)
- Device trust cookie (30-day remember)
- Rate limiting: 5 verification attempts per minute
Jira
Epic: PROJ-38 Authentication Overhaul
Story: PROJ-42 Customer login with 2FA — 5 subtasks completed
✓ Tests passing (47 new)
✓ Security review: clean
✓ UX review: approved
✓ QA: all AC met
Roadmap
From MVP to enterprise scale
Phase 1 — MVP
Launch
- Auth with 3 roles + custom roles
- Admin panel (Jira, Git, Claude config)
- Chat UI with WebSocket streaming
- On-demand Docker containers
- 14 skills, full SDLC
- Stripe billing (per-seat)
- NIS2: MFA + audit logs
- Demo tenant "testdator"
- German + English
Phase 2 — Enterprise
Scale
- SSO / SAML (Azure AD, Okta)
- Compliance audit trails + export
- Custom Jira workflow mapping
- Kubernetes migration
- GitLab / Bitbucket support
- API proxy IP protection
- Jira Marketplace listing
- Legal (ToS, DPA, SLA)
Phase 3 — Ecosystem
Expand
- Self-hosted option (Helm chart)
- Skill marketplace
- AI impact analytics
- Multi-region (EU / US)
- White-label / partner program
Under the Hood
Built on proven tools, with guardrails
Platform
- Laravel 12 + Vue 3 + Inertia.js
- PostgreSQL (multi-tenant)
- Redis + Laravel Horizon
- Laravel Reverb (WebSockets)
- Docker container orchestration
- Stripe billing (Cashier)
Engine
- Claude Code CLI (Anthropic)
- Custom Jira MCP (batch, cache)
- Agent Teams (Opus + Sonnet)
- Native Git operations
- Three-layer memory system
- JWK Overlay Pattern
Safety
- No coding without "Approved" status
- Independent UX + Security review gates
- No self-review — writer never reviews
- Tests mandatory before completion
- Container isolation per tenant
- Full audit trail in Jira + platform
Your team + AI. Together, faster. Now for everyone.
Business gives input. AI builds. Humans review.
No CLI. No setup. No lock-in.
Just your browser.
> /autopilot
+
🎤
"Run standup"
github.com/diem2001/jira-workflow-kit