npx claudepluginhub jskladan/claude.md --plugin jira<project> <summary> [options]## Name jira:create ## Synopsis ## Description Create a new Jira ticket. Uses `jtk` CLI for all operations. ## Parameters Required: - `<project>`: Project key (e.g., PROJ, MYTEAM) - `<summary>`: Ticket summary/title (quote if contains spaces) Optional: - `--type <type>`: Issue type (Task, Bug, Story, Epic) - default: Task - `--description "<text>"` or `-d`: Issue description - `--assignee <user>`: Assign to user (email, account ID, or "me") - `--parent <KEY>`: Parent issue key (for subtasks or epic children) - `--field key=value`: Set custom fields (can be repeated) ## Implementation ...
/createCreates a new beads issue interactively or via title, type (bug/feature/task/epic/chore/decision), and priority args. Uses beads MCP create tool, shows ID/details, offers linking.
/createLaunches Socratic workflow designer subagent to create orchestration workflows from natural language descriptions using interactive questioning. Accepts optional initial description argument.
/createCreates a new scaffold template in .scaffold/<name> with scaffold.yaml config, Go template files for project or template scaffolds, and validates via lint and dry-run generation.
/createCreates a workspace directory with git worktrees for multi-repository development. Parses description for GitHub PRs, JIRA keys, and repos; sets up feature branches or PR checkouts.
/createAnalyzes project state (git, Node.js, Python, Rust, Go) and creates 9 baseline Markdown context files in .claude/context/ for structure, tech, progress, vision, and more.
/createCreates a new NotebookLM notebook via CLI with given title and optional sources (URLs, files, YouTube, PDFs, etc.). Reports notebook ID and added sources.
jira:create
/jira:create <project> "<summary>" [options]
Create a new Jira ticket. Uses jtk CLI for all operations.
Required:
<project>: Project key (e.g., PROJ, MYTEAM)<summary>: Ticket summary/title (quote if contains spaces)Optional:
--type <type>: Issue type (Task, Bug, Story, Epic) - default: Task--description "<text>" or -d: Issue description--assignee <user>: Assign to user (email, account ID, or "me")--parent <KEY>: Parent issue key (for subtasks or epic children)--field key=value: Set custom fields (can be repeated)Ensure project and summary are provided. If missing, prompt user.
jtk issues create \
--project <PROJECT> \
--summary "<summary>" \
[--type <type>] \
[--description "<description>"] \
[--assignee <assignee>] \
[--parent <parent>] \
[--field key=value] \
-o json
Run the command and parse the JSON output to extract the created issue key and URL.
Report back:
Simple task:
/jira:create PROJ "Fix login button alignment"
Bug with description:
/jira:create PROJ "Login fails with SSO" --type Bug -d "Users cannot log in when using SSO provider"
Task under an epic, assigned to me:
/jira:create PROJ "Implement caching layer" --parent PROJ-100 --assignee me
Story with priority:
/jira:create PROJ "User profile redesign" --type Story --field priority=High