From logvalet
Create a Backlog issue interactively: gather project, type, summary, description, priority, assignee, and other fields via questions, preview with dry-run, then submit. Use this skill whenever the user wants to create, register, file, or add a new Backlog issue, ticket, task, or bug report. TRIGGER when: user says "課題作成", "issue作成", "チケット作成", "タスク登録", "backlogに課題を作って", "バックログに登録", "新しいissue", "create issue", "file a ticket", "make a task", "backlog.com に課題追加", "課題を作りたい", "issueを立てたい", "チケットを切って", "タスクを作って", "バグ報告を登録", "新規課題", "register an issue", "open a ticket", "add a task to backlog", "課題追加", "バックログに追加". DO NOT TRIGGER when: user wants to update an existing issue (use logvalet CLI directly) or wants to bulk-create issues from a spec (use spec-to-issues).
npx claudepluginhub youyo/claude-plugins --plugin logvaletThis skill uses the workspace's default tool permissions.
Backlog 課題をインタラクティブに作成する。不足情報は質問で補完し、dry-run でプレビューしてから実行する。
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Backlog 課題をインタラクティブに作成する。不足情報は質問で補完し、dry-run でプレビューしてから実行する。
For full logvalet CLI documentation, see the
logvaletskill.
If project-key is provided by the user, use it directly.
If not provided, list available projects:
lv project list -f md
Then ask the user to select a project using AskUserQuestion.
Required:
--project-key — from Step 1--summary — the issue titleIf summary is not provided, ask for it.
Ask about optional fields in a single question (not one-by-one). Present them as a checklist. The user can skip any or all.
Optional fields:
--description — issue body text--assignee — user ID or name (use lv user list -f md if needed)--priority — name or ID (default: "normal"). Values: 高/中/低 or high/normal/low--due-date — YYYY-MM-DD format--start-date — YYYY-MM-DD format--issue-type — name or ID (use lv meta status PROJECT_KEY if user needs to see options)--category — name or ID, multiple allowed (use lv meta category PROJECT_KEY if needed)--milestone — name or ID, multiple allowed (use lv meta version PROJECT_KEY if needed)--parent-issue-id — parent issue ID for sub-tasksIf the user needs to see available options for issue-type, category, milestone, or assignee:
lv meta category PROJECT_KEY -f md
lv meta version PROJECT_KEY -f md
lv user list -f md
Run these only when the user explicitly asks or is unsure about available values.
ALWAYS run with --dry-run first:
lv issue create --project-key PROJ --summary "..." \
[--description "..."] [--assignee USER_ID] [--priority normal] \
[--due-date YYYY-MM-DD] [--issue-type "タスク"] \
[--category "カテゴリ名"] [--milestone "マイルストーン名"] \
--dry-run
Show the dry-run output to the user and ask for confirmation.
After user confirms, run the same command without --dry-run:
lv issue create --project-key PROJ --summary "..." \
[--description "..."] [--assignee USER_ID] [--priority normal] \
[--due-date YYYY-MM-DD] [--issue-type "タスク"] \
[--category "カテゴリ名"] [--milestone "マイルストーン名"]
Display:
PROJ-456)--priority "高") instead of IDs; logvalet resolves them--description for short text, --description-file for long content (write to a temp file first)--category and --milestone accept multiple --category A --category B flagsIf the user wants to create multiple issues at once from a spec file or requirements document, use the logvalet-spec-to-issues skill instead.
When to switch:
spec.md, requirements.md)How to switch:
Tell the user:
複数の課題をまとめて作成する場合は
logvalet-spec-to-issuesスキルを使います。spec ファイルのパスを教えてください。
The logvalet-spec-to-issues skill handles:
logvalet-spec-to-issues instead