Run any Skill in Manus with one click

ticket-creator

Stars0

Forks0

UpdatedJuly 6, 2026 at 10:42

Create a new Jira ticket (Bug/Story/Task) end-to-end — gathers requirements via GDS plain-English questions, drafts the ticket to ~/git/defra/trade-imports-animals-workspace/workareas/ticket-creation/<slug>/draft.md for user iteration, then creates it in Jira via the shared create-ticket script. Use when the user wants to raise, file, log, open or otherwise create a new Jira ticket from scratch (triggers: "create ticket", "raise ticket", "new ticket", "file a bug", "log a story", "open a ticket", "flesh out ticket"). NOT for working an existing ticket (use the ticket skill) and NOT for assessing whether an existing ticket is refinement-ready (use the ticket-refiner skill).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

DEFRA

DEFRA/trade-imports-animals-workspace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

5 files

SKILL.md

readonly

More from this repository

same repository

test-stack-analysis

DEFRA/trade-imports-animals-workspace

'Given a feature description, Jira ticket, or Confluence URL, finds every related test file across the 8 EUDP Live Animals repos, classifies each by pyramid level (unit/integration/E2E) and concern type, and reports coverage gaps and cross-level duplication with file:line evidence — so a developer knows where to add or remove test coverage before writing new tests. Triggers: "test-stack-analysis EUDPA-X", "find test gaps EUDPA-X", "test pyramid analysis EUDPA-X", "analyse test coverage EUDPA-X", "check test pyramid for <feature>". One-shot, report-only — makes no code changes. NOT for correctness/style review of existing code (use `review` or `code-style`), NOT for verifying a PR author understands their own change (use `understanding-check`), NOT for scaffolding CLAUDE.md (Claude Code'\''s built-in `/init`).'

2026-07-160

govuk-upgrade

DEFRA/trade-imports-animals-workspace

Upgrade the govuk-frontend package across every EUDP Live Animals Node.js repo that consumes it. A four-stage workflow driven by canonical per-repo JSON state (`versions.{repo}.json`): Phase 1 = `start-upgrade.sh` (ticket → branch → discover repos → seed state + pre-bake CHANGELOG sections + best-practices bundle), Phase 2 = fan-out one `general-purpose` Task subagent per pending version following `references/VERSION_PLANNER.md` (uses `version-classify.sh` + `version-add-change.sh`), optional Walker = batch triage of pending plans following `references/PLAN_WALKER.md`, Phase 3 = strict-semver-order `apply-version.sh` per `todo` version (package.json + npm install + npm test + commit + state transition), then E2E once at the end. Stays inside the govuk-frontend toolbox — Nunjucks macros, govuk-* utility classes, no custom CSS or hand-rolled components. Triggers: "upgrade govuk-frontend", "govuk upgrade", "govuk-frontend upgrade", "bump govuk-frontend", "walk govuk EUDPA-XXX", "start-upgrade.sh". NOT for non-go

2026-07-090

journey-builder

DEFRA/trade-imports-animals-workspace

Build the real live-animals journey prototype (prototypes/standalone/live-animals in trade-imports-animals-frontend) on the obligations-v2 page-owned-spine model. Digest mode distils the requirement sources — Confluence "Live Animals Data Fields V4", the src/server skeleton journey, the interaction-design canvas — into a canonical machine-readable spec (journey-spec.json + conflicts.json) reviewed at a spec gate. Backlog mode derives ordered increments from the spec; build mode runs the serial implementor loop (one INCREMENT_IMPLEMENTOR subagent per increment, parent re-verifies, commit-or-rollback), halting at model-extension gates and milestone walk-throughs. Use when the user asks to digest journey requirements, regenerate the backlog, run/resume the build loop, or verify the prototype (triggers: "digest journey requirements", "journey spec", "journey-builder", "build the live-animals prototype", "run the loop"). NOT for the car-insurance spike itself or for generic ticket work.

2026-07-080

code-style

DEFRA/trade-imports-animals-workspace

Multi-language code-style/lint review (formatting, conventions, style rules) and remediation for EUDP Live Animals PRs (EUDPA-*). Reviews Java, GDS/Nunjucks (.njk), Playwright specs, k6 and Node source files, each against its context-appropriate best-practices bundle (Java modern-java + Javadoc; GDS components/styles/patterns; Playwright; k6; Node 17-rule style guide + JSDoc). Supports fresh review, refresh review (re-review after new commits), interactive walker that triages findings one item at a time, and batched implementor that applies queued style fixes. Fans out per-file review and per-file implementation to `general-purpose` Task subagents that follow worker personas under `references/`. Use when the user asks for code style/lint review or to apply agreed style fixes (triggers: "style review EUDPA-", "code style review", "re-style review", "style refresh", "walk style EUDPA-", "triage style", "fix style EUDPA-", "implement style fixes", "lint review"). NOT for correctness/design review across language

2026-07-060

npm-upgrade

DEFRA/trade-imports-animals-workspace

Upgrade (non-govuk-frontend) npm packages across the EUDP Live Animals repos via a three-phase workflow plus interactive walker — discover outdated packages, classify each as auto (no code changes) or manual (breaking changes), run automated upgrades with rollback safety, produce a handoff manifest for the remaining manual work, then walk the manual list keystroke-by-keystroke and spawn a per-package implementor worker on demand. Per-package classification and implementation state lives in canonical JSON (`packages.{repo}.json`) — no markdown plan files on disk. Fans out per-package research in Phase 1 to `general-purpose` Task subagents following `references/PACKAGE_PLANNER.md`, and per-package implementation from the walker to subagents following `references/MANUAL_UPGRADE_IMPLEMENTOR.md`. Use when the user asks to bring npm packages up to date across repos (triggers: "upgrade npm deps", "upgrade npm dependencies", "upgrade dependencies", "run npm upgrades", "walk upgrade EUDPA-XXX", "triage upgrade EUDPA-X

2026-07-060

review

DEFRA/trade-imports-animals-workspace

Code review for correctness, security, error handling, performance, best-practices and test coverage across all languages and repos (Java, Node.js, frontend, tests) for EUDP Live Animals tickets. Handles fresh first-pass review, refresh (re-review after further work, merge conflicts or coverage gaps), interactive walker that triages findings one item at a time, and batched implementor that applies queued fixes. Fans out per-file reviews, per-repo consistency analysis and per-item fixes to `general-purpose` Task subagents that follow worker personas under `references/`. Use when the user says "review EUDPA-XXX", "code review", "re-review EUDPA-XXX", "refresh review", "check fixes", "walk review EUDPA-XXX", "triage review", "implement review EUDPA-XXX", or "apply review fixes". NOT for JS lint/format/style findings — use the code-style skill for those.

2026-07-060

Question

Purpose

Type (Bug/Story/Task)?

Template

One-line summary?

Summary field

Context - why needed?

Description

Acceptance criteria?

AC section

Field

How to Determine

Type

Bug=broken, Story=user-facing, Task=technical

Summary

<80 chars, specific, action-oriented

Priority

Highest/High=blocking; Medium=normal; Low/Lowest=nice-to-have

Type

Template file

Bug

assets/templates/bug.md

Story

assets/templates/story.md

Task

assets/templates/task.md

# Ticket Draft: <slug> **Type:** [Bug/Story/Task] **Summary:** [Summary] **Priority:** [Priority] **Parent:** [Epic or None] **Labels:** [labels or None] **Assignee:** [Self or None] ## Description [Wiki markup body — see assets/templates/<type>.md] ## Open Questions - [Anything still missing or ambiguous] ## Status DRAFT — awaiting user approval

Flag

Description

Default

-t, --type

Bug/Story/Task

Task

-p, --parent

Epic key

None

-P, --priority

Lowest-Highest

Medium

-l, --label

Add label (repeatable)

None

-a

Self-assign

Question

Purpose

Type (Bug/Story/Task)?

Template

One-line summary?

Summary field

Context - why needed?

Description

Acceptance criteria?

AC section

Field

How to Determine

Type

Bug=broken, Story=user-facing, Task=technical

Summary

<80 chars, specific, action-oriented

Priority

Highest/High=blocking; Medium=normal; Low/Lowest=nice-to-have

Type

Template file

Bug

assets/templates/bug.md

Story

assets/templates/story.md

Task

assets/templates/task.md

Flag

Description

Default

-t, --type

Bug/Story/Task

Task

-p, --parent

Epic key

None

-P, --priority

Lowest-Highest

Medium

-l, --label

Add label (repeatable)

None

-a

Self-assign

name	ticket-creator
description	Create a new Jira ticket (Bug/Story/Task) end-to-end — gathers requirements via GDS plain-English questions, drafts the ticket to ~/git/defra/trade-imports-animals-workspace/workareas/ticket-creation/<slug>/draft.md for user iteration, then creates it in Jira via the shared create-ticket script. Use when the user wants to raise, file, log, open or otherwise create a new Jira ticket from scratch (triggers: "create ticket", "raise ticket", "new ticket", "file a bug", "log a story", "open a ticket", "flesh out ticket"). NOT for working an existing ticket (use the ticket skill) and NOT for assessing whether an existing ticket is refinement-ready (use the ticket-refiner skill).
context	inline
allowed-tools	["Bash","Read","Write","Edit"]
argument-hint	[optional one-line summary]

name	ticket-creator
description	Create a new Jira ticket (Bug/Story/Task) end-to-end — gathers requirements via GDS plain-English questions, drafts the ticket to ~/git/defra/trade-imports-animals-workspace/workareas/ticket-creation/<slug>/draft.md for user iteration, then creates it in Jira via the shared create-ticket script. Use when the user wants to raise, file, log, open or otherwise create a new Jira ticket from scratch (triggers: "create ticket", "raise ticket", "new ticket", "file a bug", "log a story", "open a ticket", "flesh out ticket"). NOT for working an existing ticket (use the ticket skill) and NOT for assessing whether an existing ticket is refinement-ready (use the ticket-refiner skill).
context	inline
allowed-tools	["Bash","Read","Write","Edit"]
argument-hint	[optional one-line summary]

ticket-creator

Path conventions

Step 0: Session start

Workflow

Step 1: Gather Information

Required Questions

Parent epic — always asked

Capability code (Stories only — optional)

Tech-debt modifier (opt-in)

For Bugs

For Stories

For Tasks

Step 1.5: Verify parent epic (if provided)

Step 2: Determine Fields

Labels

Step 3: Write Description

Step 4: Iterate on Draft

Step 5: Create Ticket

After Creation

References

Path conventions

Step 0: Session start

Workflow

Step 1: Gather Information

Required Questions

Parent epic — always asked

Capability code (Stories only — optional)

Tech-debt modifier (opt-in)

For Bugs

For Stories

For Tasks

Step 1.5: Verify parent epic (if provided)

Step 2: Determine Fields

Labels

Step 3: Write Description

Step 4: Iterate on Draft

Step 5: Create Ticket

After Creation

References