feat(claude): add acli skill with business-only restriction

.chezmoiignore

@@ -39,6 +39,7 @@ homebrew/
 .config/git/freee
 homebrew/Brewfile.work
 .claude/rules/pr-size.md
+.claude/skills/acli/
 {{ end }}
 
 # Local files (never managed by chezmoi)

dot_claude/skills/acli/SKILL.md

@@ -0,0 +1,269 @@
+---
+name: acli
+description: Atlassian CLI (acli) for Jira operations. Use when (1) creating Jira tickets/issues, (2) updating or editing existing tickets, (3) searching Jira issues, (4) viewing ticket details, (5) managing work items programmatically. Provides correct syntax and ADF format for descriptions.
+---
+
+# Atlassian CLI (acli)
+
+CLI tool for Jira Cloud operations. Use `acli jira workitem` commands for issue management.
+
+## Initial Setup
+
+Before using acli, always confirm with user:
+
+1. **Project Key**: Required for all operations
+2. **Parent Epic/Ticket**: Required when creating sub-tasks or linking issues
+3. **Issue Type**: Task, Bug, Story, etc.
+
+```
+AskUserQuestion examples:
+- "What is the Jira project key?" (e.g., PROJ, TEAM)
+- "What is the parent Epic key?" (e.g., PROJ-100)
+- "What issue type should I use?" (Task, Bug, Story, Sub-task)
+- "Are there any reference tickets I should check for format/style?"
+```
+
+**Important**: Always verify the parent ticket exists before creating sub-tasks:
+
+```bash
+acli jira workitem view --key PROJ-100
+```
+
+## Quick Reference
+
+| Operation | Command |
+|-----------|---------|
+| View | `acli jira workitem view --key KEY-123` |
+| Create | `acli jira workitem create --from-json file.json` |
+| Edit | `acli jira workitem edit --from-json file.json --yes` |
+| Search | `acli jira workitem search --jql "project = PROJ"` |
+| Delete | `acli jira workitem delete --key KEY-123` (requires confirmation) |
+
+## Ticket Templates
+
+When creating tickets, ask user for reference tickets to match existing style:
+
+```bash
+# Check existing ticket format
+acli jira workitem view --key PROJ-50
+```
+
+### Standard Ticket Structure
+
+Recommended sections for task tickets:
+
+1. **Summary** (概要): Brief description of the task
+2. **Background/Investigation** (調査結果): Context, data, evidence
+3. **Acceptance Criteria** (受け入れ条件): Checklist of completion criteria
+4. **References** (参考資料): Links to documentation, Datadog, PRs, etc.
+
+## Creating Tickets
+
+Use `--from-json` with ADF (Atlassian Document Format) for proper formatting:
+
+```bash
+acli jira workitem create --from-json /tmp/ticket.json
+```
+
+### JSON Structure
+
+```json
+{
+  "projectKey": "PROJ",
+  "type": "Task",
+  "parentIssueId": "PROJ-100",
+  "summary": "Ticket title",
+  "description": {
+    "type": "doc",
+    "version": 1,
+    "content": [...]
+  }
+}
+```
+
+### Issue Types
+
+| Type | Use Case |
+|------|----------|
+| Epic | Large feature/initiative grouping multiple tasks |
+| Story | User-facing feature |
+| Task | Technical work item |
+| Bug | Defect fix |
+| Sub-task | Child of another issue |
+
+### ADF Content Types
+
+See [references/adf-format.md](references/adf-format.md) for complete ADF reference.
+
+**Common patterns:**
+
+```json
+// Heading
+{"type": "heading", "attrs": {"level": 2}, "content": [{"type": "text", "text": "Title"}]}
+
+// Paragraph
+{"type": "paragraph", "content": [{"type": "text", "text": "Content"}]}
+
+// Bullet list
+{"type": "bulletList", "content": [
+  {"type": "listItem", "content": [
+    {"type": "paragraph", "content": [{"type": "text", "text": "Item"}]}
+  ]}
+]}
+
+// Task list (checkboxes) - for acceptance criteria
+{"type": "taskList", "attrs": {"localId": "list-1"}, "content": [
+  {"type": "taskItem", "attrs": {"localId": "item-1", "state": "TODO"},
+   "content": [{"type": "text", "text": "Task item"}]}
+]}
+
+// Code (inline)
+{"type": "text", "text": "code here", "marks": [{"type": "code"}]}
+
+// Link - for references
+{"type": "text", "text": "Link text", "marks": [{"type": "link", "attrs": {"href": "https://..."}}]}
+```
+
+### Including References
+
+Always include relevant links in tickets:
+
+```json
+{
+  "type": "bulletList",
+  "content": [
+    {
+      "type": "listItem",
+      "content": [
+        {
+          "type": "paragraph",
+          "content": [
+            { "type": "text", "text": "Datadog URL", "marks": [
+              { "type": "link", "attrs": { "href": "https://app.datadoghq.com/logs?..." } }
+            ]}
+          ]
+        }
+      ]
+    },
+    {
+      "type": "listItem",
+      "content": [
+        {
+          "type": "paragraph",
+          "content": [
+            { "type": "text", "text": "Related PR", "marks": [
+              { "type": "link", "attrs": { "href": "https://github.com/..." } }
+            ]}
+          ]
+        }
+      ]
+    }
+  ]
+}
+```
+
+## Editing Tickets
+
+Use `--from-json` with `issues` array to specify targets:
+
+```bash
+acli jira workitem edit --from-json /tmp/edit.json --yes
+```
+
+### Edit JSON Structure
+
+```json
+{
+  "issues": ["PROJ-123", "PROJ-124"],
+  "description": {
+    "type": "doc",
+    "version": 1,
+    "content": [...]
+  }
+}
+```
+
+**Important flags:**
+- `--yes`: Skip confirmation prompt (required for automation)
+- `--from-json`: Use JSON file with `issues` array
+
+**Common mistake:** `--key` and `--from-json` cannot be used together. Use `issues` array inside JSON instead.
+
+## Linking Issues
+
+### Issue Links (blocks, relates to, etc.)
+
+```bash
+acli jira workitem link --help
+```
+
+### Parent-Child Relationships
+
+Set `parentIssueId` in create JSON for Epic-Task relationships.
+
+## Bulk Operations
+
+### Create Multiple Tickets
+
+Loop through data and create JSON for each:
+
+```bash
+for item in "Item1" "Item2" "Item3"; do
+  # Generate JSON with proper ADF
+  cat > /tmp/ticket.json << EOF
+  {...}
+EOF
+  acli jira workitem create --from-json /tmp/ticket.json
+done
+```
+
+### Edit Multiple Tickets
+
+Include all keys in `issues` array:
+
+```json
+{
+  "issues": ["PROJ-1", "PROJ-2", "PROJ-3"],
+  "summary": "Updated title"
+}
+```
+
+## Common Workflows
+
+### Create Task Under Epic
+
+1. Ask user for project key and parent Epic
+2. Verify parent Epic exists: `acli jira workitem view --key EPIC-KEY`
+3. Ask if there are reference tickets for format
+4. Generate JSON with `parentIssueId`
+5. Create with `--from-json`
+
+### Update Ticket Description
+
+1. View current ticket: `acli jira workitem view --key PROJ-123`
+2. Generate edit JSON with `issues` array
+3. Include new ADF description
+4. Run with `--yes` flag
+
+### Create Tickets with References
+
+1. Gather all reference URLs (Datadog, GitHub, docs)
+2. Include as links in description using ADF link marks
+3. Verify links are accessible
+
+## Troubleshooting
+
+| Error | Cause | Solution |
+|-------|-------|----------|
+| `INVALID_INPUT` | Bad ADF format | Validate JSON structure |
+| `flags cannot be used together` | `--key` with `--from-json` | Use `issues` array in JSON |
+| Markdown not rendering | Plain text description | Use ADF format |
+| Confirmation prompt blocking | Missing `--yes` | Add `--yes` flag |
+| `Issue does not exist` | Wrong key or no permission | Verify key with `view` first |
+
+## References
+
+- [ADF Format Reference](references/adf-format.md) - Complete ADF syntax guide
+- Run `acli jira workitem --help` for all available commands
+- Run `acli jira workitem create --generate-json` for JSON template
+- Run `acli jira workitem edit --generate-json` for edit JSON template

dot_claude/skills/acli/assets/example_asset.txt

@@ -0,0 +1,24 @@
+# Example Asset File
+
+This placeholder represents where asset files would be stored.
+Replace with actual asset files (templates, images, fonts, etc.) or delete if not needed.
+
+Asset files are NOT intended to be loaded into context, but rather used within
+the output Claude produces.
+
+Example asset files from other skills:
+- Brand guidelines: logo.png, slides_template.pptx
+- Frontend builder: hello-world/ directory with HTML/React boilerplate
+- Typography: custom-font.ttf, font-family.woff2
+- Data: sample_data.csv, test_dataset.json
+
+## Common Asset Types
+
+- Templates: .pptx, .docx, boilerplate directories
+- Images: .png, .jpg, .svg, .gif
+- Fonts: .ttf, .otf, .woff, .woff2
+- Boilerplate code: Project directories, starter files
+- Icons: .ico, .svg
+- Data files: .csv, .json, .xml, .yaml
+
+Note: This is a text placeholder. Actual assets can be any file type.