[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASJZHYPSJ9DP9JRFPH29G5":3,"skill-same:01M7ASJZHYPSJ9DP9JRFPH29G5":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ASJZHYPSJ9DP9JRFPH29G5","setup-matt-pocock-skills",null,"Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.","ozzycodes2\u002Fclaudellum","ozzycodes2","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F21285094?v=4","01M7ASJ57KTP519F96S4QGM7C5","Osniel Quintana","01M7ASJ589JS8S075AA92Y08S4",1,"MIT","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: setup-matt-pocock-skills\ndescription: Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.\n---\n\n# Setup Matt Pocock's Skills\n\nScaffold per-repo config the engineering skills assume:\n\n- **Issue tracker** — where issues live (GitHub by default; local markdown also supported)\n- **Triage labels** — strings for the five canonical triage roles\n- **Domain docs** — where `CONTEXT.md` and ADRs live, plus consumer rules for reading them\n\nPrompt-driven, not a deterministic script. Explore, present findings, confirm with user, then write.\n\n## Process\n\n### 1. Explore\n\nInspect current repo state. Read what exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig` — GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at repo root — either exist? Already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` dirs\n- `docs\u002Fagents\u002F` — this skill's prior output already there?\n- `.scratch\u002F` — sign a local-markdown issue tracker convention is in use\n- Is `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in available skills.) Decides whether Section B runs.\n- Monorepo signals — `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or populated `packages\u002F*` with own `src\u002F`. Present only in a genuinely large multi-package repo; absence means single-context, almost every repo.\n\n### 2. Present findings and ask\n\nSummarise present vs missing. Take sections in order — one section, one answer, then next.\n\nLead each section with recommended answer so user accepts in a word. One-line explainer only when choice genuinely branches; skip section when exploration settled it (Section B when `triage` not installed, Section C when no monorepo).\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read\u002Fwrite it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow another workflow you describe. Pick where you actually track work.\n\nDefault posture: designed for GitHub. If a `git remote` points at GitHub, propose that. If at GitLab (`gitlab.com` or self-hosted), propose GitLab. Otherwise (or if user prefers), offer:\n\n- **GitHub** — issues in repo's GitHub Issues (uses `gh` CLI)\n- **GitLab** — issues in repo's GitLab Issues (uses [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown** — issues as files under `.scratch\u002F\u003Cfeature>\u002F` (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.) — ask user to describe workflow in one paragraph; recorded as freeform prose\n\nRecord choice in `docs\u002Fagents\u002Fissue-tracker.md`. GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off** — leave it off and don't raise it; user can flip the flag in the file later.\n\n**Section B — Triage label vocabulary.** Skip entirely if `triage` skill not installed — an uninstalled skill needs no labels.\n\nIf installed, ask exactly one question:\n\n> Keep default triage labels? (recommended: **yes**)\n\nDefaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write as-is. Only if user says no — usually because their tracker uses other names (e.g. `bug:triage` for `needs-triage`) — collect overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C — Domain docs.** Default **single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at repo root. Fits almost every repo; write without asking.\n\nOffer **multi-context** — a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files — only when exploration found monorepo signals. Then confirm which layout they want.\n\n### 3. Confirm and edit\n\nShow user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is edited (see step 4 for selection rules)\n- Contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (last only when `triage` installed)\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask user which to create — don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa) — always edit the one already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout — \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` installed and Section B ran. Otherwise both omitted.\n\nThen write the docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md) — GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md) — GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md) — local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md) — label mapping (only if `triage` installed)\n- [domain.md](.\u002Fdomain.md) — domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell user setup is complete and which engineering skills now read these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later — re-running this skill is only necessary to switch issue trackers or restart from scratch.\n","# Setup Matt Pocock's Skills\n\nScaffold per-repo config the engineering skills assume:\n\n- **Issue tracker** — where issues live (GitHub by default; local markdown also supported)\n- **Triage labels** — strings for the five canonical triage roles\n- **Domain docs** — where `CONTEXT.md` and ADRs live, plus consumer rules for reading them\n\nPrompt-driven, not a deterministic script. Explore, present findings, confirm with user, then write.\n\n## Process\n\n### 1. Explore\n\nInspect current repo state. Read what exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig` — GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at repo root — either exist? Already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` dirs\n- `docs\u002Fagents\u002F` — this skill's prior output already there?\n- `.scratch\u002F` — sign a local-markdown issue tracker convention is in use\n- Is `triage` skill installed? (a `triage` skill folder alongside this one, or `triage` in available skills.) Decides whether Section B runs.\n- Monorepo signals — `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or populated `packages\u002F*` with own `src\u002F`. Present only in a genuinely large multi-package repo; absence means single-context, almost every repo.\n\n### 2. Present findings and ask\n\nSummarise present vs missing. Take sections in order — one section, one answer, then next.\n\nLead each section with recommended answer so user accepts in a word. One-line explainer only when choice genuinely branches; skip section when exploration settled it (Section B when `triage` not installed, Section C when no monorepo).\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-tickets`, `triage`, and `to-spec` read\u002Fwrite it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow another workflow you describe. Pick where you actually track work.\n\nDefault posture: designed for GitHub. If a `git remote` points at GitHub, propose that. If at GitLab (`gitlab.com` or self-hosted), propose GitLab. Otherwise (or if user prefers), offer:\n\n- **GitHub** — issues in repo's GitHub Issues (uses `gh` CLI)\n- **GitLab** — issues in repo's GitLab Issues (uses [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown** — issues as files under `.scratch\u002F\u003Cfeature>\u002F` (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.) — ask user to describe workflow in one paragraph; recorded as freeform prose\n\nRecord choice in `docs\u002Fagents\u002Fissue-tracker.md`. GitHub and GitLab templates carry a \"PRs as a request surface\" flag, defaulted **off** — leave it off and don't raise it; user can flip the flag in the file later.\n\n**Section B — Triage label vocabulary.** Skip entirely if `triage` skill not installed — an uninstalled skill needs no labels.\n\nIf installed, ask exactly one question:\n\n> Keep default triage labels? (recommended: **yes**)\n\nDefaults are the five canonical roles, each label string equal to its name: `needs-triage`, `needs-info`, `ready-for-agent`, `ready-for-human`, `wontfix`. On **yes**, write as-is. Only if user says no — usually because their tracker uses other names (e.g. `bug:triage` for `needs-triage`) — collect overrides so `triage` applies existing labels instead of creating duplicates.\n\n**Section C — Domain docs.** Default **single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at repo root. Fits almost every repo; write without asking.\n\nOffer **multi-context** — a root `CONTEXT-MAP.md` pointing to per-context `CONTEXT.md` files — only when exploration found monorepo signals. Then confirm which layout they want.\n\n### 3. Confirm and edit\n\nShow user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is edited (see step 4 for selection rules)\n- Contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Fdomain.md`, and `docs\u002Fagents\u002Ftriage-labels.md` (last only when `triage` installed)\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask user which to create — don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa) — always edit the one already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout — \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nInclude the `### Triage labels` sub-block, and write `docs\u002Fagents\u002Ftriage-labels.md`, only when `triage` installed and Section B ran. Otherwise both omitted.\n\nThen write the docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md) — GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md) — GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md) — local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md) — label mapping (only if `triage` installed)\n- [domain.md](.\u002Fdomain.md) — domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell user setup is complete and which engineering skills now read these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later — re-running this skill is only necessary to switch issue trackers or restart from scratch.\n",{"name":5,"description":7},"main","a3f19bcc313571bff79dca391a83f9c4d38bb335","architecture-design\u002Fskills\u002Fsetup-matt-pocock-skills",0,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum","https:\u002F\u002Fgithub.com\u002Fozzycodes2","Software Engineer | Engineering Manager | AI whisperer | ☕Enjoyer","2026-11-14 04:50:11",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add ozzycodes2\u002Fclaudellum --skill setup-matt-pocock-skills",{"tool":38,"command":39},"bunx","bunx skills add ozzycodes2\u002Fclaudellum --skill setup-matt-pocock-skills",{"tool":41,"command":42},"pnpm","pnpm dlx skills add ozzycodes2\u002Fclaudellum --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",true,[46,52,56,60,64,68],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",152,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"domain.md",2045,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"issue-tracker-github.md",3746,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"issue-tracker-gitlab.md",3827,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"issue-tracker-local.md",1815,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Farchitecture-design\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[73,80,87,94,101,108],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7ASQB3CTKMKDNAXD9DCF1YC","writing-design-docs","Use when the user wants to write a problem-statement design doc, says \"let's plan a feature properly\" \u002F \"write a design doc\" \u002F \"I'm thinking about how to do X\" for a non-trivial X, or before committing to a non-obvious technical direction","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwriting-design-docs\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7ASQ6JD4QRV5ZKK2QME401Y","write-doc","Use when the user asks to write or draft a README, ADR, runbook, tutorial, how-to, explanation, or reference doc, or a caller passes \"type ADR\" or \"type README\". Picks the type, fills a template, adds diagrams. RFCs and design docs belong to writing-design-docs.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fwrite-doc\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7ASQ1VWNVP1RE7M5D4G2QMG","review-doc","Use when the user asks to review, critique, score, grade, or \"how good is this doc\" for a Markdown doc or pasted text. Read-only. Scores it on the 20 Practical Prose dimensions and emits a findings table. Does not edit; fix-doc applies the findings next.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Freview-doc\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7ASPWST208JZNR7HF7J6KMV","fix-doc","Use when the user asks to fix, edit for prose quality, polish, tighten, humanize, or de-slop a Markdown doc or pasted text, or says \"make this read less AI\". Applies review-doc findings, generates flagged diagrams, lists substantive issues for the author, then runs the AI-tell pass last. Modifies the target.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Ffix-doc\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7ASPS6Y9ZGK9KCDHNPDR75A","create-slides","Use when the user asks for a slide deck, presentation, talk, or slides from a document, report, PR, notes, or topic. Builds one self-contained Machinify-branded HTML deck in a minimalist style, with headline-plus-visual slides, speaker notes, and every diagram drawn by architecture-design:create-diagram.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Ftechnical-writing\u002Fskills\u002Fcreate-slides\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7ASPAKFY045KHR92Y4QFTWV","start-session","Open a Claude Code working session in a fresh, isolated git worktree, so the user can start a task with a single \u002Fstart-session \u003Cname>. Use at the START of a session when the user says \"start session\", \"start a worktree\", \"spin up a worktree for ABC-123\", \"begin work on \u003Cticket>\", or passes a name\u002Fticket to work under. Creates and ENTERS a worktree via the EnterWorktree tool (never `git worktree add`) under .claude\u002Fworktrees\u002F, named exactly after the argument, on a local branch `worktree-\u003Cargument>`. Reports what the worktree inherited (`.worktreeinclude` copies, symlinked node_modules) and whether its `.env` still points at the main checkout's stack. If the argument is a JIRA key (e.g. ABC-123, PROJ-1505), also loads that story with the Atlassian CLI (`acli`) when available and summarizes the implementation ask. Also renames the session to the argument (the same effect as `\u002Frename \u003CNAME>`) so it's easy to find in `\u002Fresume`. Then stops and waits — it sets up the workspace and context, it does not implement.","https:\u002F\u002Fgithub.com\u002Fozzycodes2\u002Fclaudellum\u002Fblob\u002Fmain\u002Fsession-mgmt\u002Fskills\u002Fstart-session\u002FSKILL.md",[],[]]