Ticket-to-Shipped: The 10-Skill Jira Dev Workflow
Ten skills that compose into one deterministic pipeline, so a coding agent never skips a step or guesses when it shouldn't: turn an approved requirement into a well-structured Jira ticket, load its full context, verify the real repository against the ticket's claims, plan a bounded implementation, prepare a safe git branch, implement, verify with real checks, confirm every acceptance criterion individually, stop for explicit human review, publish only on approval, and keep Jira honest at every real milestone.
Built and proven over dozens of real tickets on a production codebase. Repo-agnostic: works with your own branch convention and issue-key pattern, not hardcoded to one project. Defensive by design — every skill has explicit stop conditions and never fabricates a result when something's ambiguous or a tool call fails.
The tenth skill, Ticket Execution Workflow, is the orchestrator that runs all nine others end to end from one entry point. Buy the bundle instead of the nine pieces separately and get the whole pipeline, plus the orchestrator, at a real discount.
Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.
One payment, lifetime access. 10 skills unlock instantly in your library.
What's included
10 skillsChecks every acceptance criterion individually against real evidence — never counts "most of them look fine" as done.
The one explicit checkpoint where a human — not the agent — decides a change is ready to go public. No commit, push, or PR without a real, current, specific approval.
Converts Jira context and repository investigation facts into a grounded, bounded implementation plan.
Proves a change actually works by running the real checks — never claims "verified" based on what a passing local run merely suggests.
Turns an approved requirement into a well-structured Jira ticket — checks for duplicates and the right parent epic first.
Load and normalize Jira ticket data, acceptance criteria, and dependency context into structured JSON for developers.
Keeps Jira an honest record of real progress — posts evidence-backed comments at defined points, and only moves a ticket to Done when a real merge actually happened.
Conducts a read-only audit of a repository to verify ticket claims and document current architecture before planning.
Enforces safe, standardized Git branch creation and worktree verification before implementation begins.
The orchestrator — runs all 9 other skills in deterministic order, from Jira ticket to merged, reviewed, recorded code. One entry point for an entire ticket's lifecycle.
See it in action
Acceptance Criteria Verification
Example session with this skill installed
Check the acceptance criteria for the E2E testing ticket — the verification report just came back.
- Read your context and instructions
- Compiled the acceptance criteria verification
Summary
6 of 8 criteria look fine — but the ticket isn't done. One ambiguous locator matches two different "Add item" buttons, so the core happy-path test doesn't actually pass yet.
| Criterion | Status |
|---|---|
| Playwright configured, runs in CI | Satisfied |
| Critical happy-path flow passes | Not satisfied — locator matches 2 elements |
| Stable selectors | Not satisfied — same locator issue |
| Failure artifacts captured | Satisfied |
| Blocks promotion on failure | Not verifiable — no promotion pipeline exists yet |
| ...3 more | Satisfied |
{
"criteria": [
{ "text": "Critical happy-path flows are covered first.", "status": "not-satisfied", "evidence": "critical-flow.spec.ts exists but fails: strict-mode violation on an ambiguous locator.", "gap": "Locator needs scoping to its section before this flow genuinely passes." }
],
"overallStatus": "incomplete",
"ambiguousCriteria": []
}
Next steps
- Scope the ambiguous locator to its containing section
- Re-run implementation verification, then re-check acceptance criteria — don't call this done at "6 of 8"
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads these skills and uses them on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every skill in this bundle goes through our trust checks.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.