[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75TSTCVC2JK1FRSV4HGVQAC":3,"skill-same:01M75TSTCVC2JK1FRSV4HGVQAC":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75TSTCVC2JK1FRSV4HGVQAC","roadmap-clips",null,"Use when the operator wants a cross-source roadmap from the luna vault — writes a 60-Maps\u002F note. Proposals only.","yotamleo-org\u002FHimmel","yotamleo-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F344898079?v=4","01M75TKGRE629BDM7G461ABVZP","01M75TKGS2GVCFR1A28MBMK997",15,"MIT","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fmarketplace\u002Fplugins\u002Fobsidian-triage\u002Fskills\u002Froadmap-clips\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: roadmap-clips\ndescription: Use when the operator wants a cross-source roadmap from the luna vault — writes a 60-Maps\u002F note. Proposals only.\n---\n\n# roadmap-clips — cross-source roadmap synthesis\n\nYou turn the luna vault's scattered actionable signal into ONE sequenced\nroadmap note in `60-Maps\u002F`. You **propose** — you never auto-file Jira tickets\nand never restructure the vault (same contract as `\u002Fsynthesize-clips`).\n\nDeterministic collection lives in `tools\u002Froadmap-aggregate.mjs` (read-only,\nno network). You do the judgement work: cluster, sequence, map to tools, dedup\ncandidate tickets against open Jira. **NEVER headless:** invoke the tool and the\nJira CLI with the `Bash` tool only — no headless \u002F print-mode claude invocations.\n\n## Inputs\n\n`$ARGUMENTS` (all optional): `[--vault \u003Cpath>] [--dry-run]`.\n- `--vault \u003Cpath>` — luna vault root. Default `$HOME\u002FDocuments\u002Fluna`.\n- `--dry-run` — do everything EXCEPT the final write; print the roadmap to\n  stdout instead.\n\n## Steps\n\n### 1. Aggregate (deterministic)\nRun the aggregator and capture its JSON inventory:\n```bash\nnode \u003Cplugin>\u002Ftools\u002Froadmap-aggregate.mjs [--vault \"$VAULT\"]\n```\n`\u003Cplugin>` = `marketplace\u002Fplugins\u002Fobsidian-triage`. The JSON is\n`{vault, counts, total, items:[{source_type, text, origin, category}]}` with\n`source_type ∈ action-item | deferred | synthesis-proposal | promotion |\ncomponent`. If `total` is 0, print `roadmap-clips: no actionable items found —\nnothing to map` and exit 0.\n\n### 2. Cluster into themes (judgement)\nGroup the items into 3–8 coherent **themes** (e.g. \"vault enrichment depth\",\n\"pipeline automation\", \"source-trust hygiene\"). A theme spans source types —\na `deferred` github ref, a `synthesis-proposal`, and an `action-item` can all\nbelong to the same theme. Note the supporting item count + origins per theme.\nSkip pure noise (e.g. a bare fan-out URL with no thematic signal) but log how\nmany items you dropped so coverage is honest.\n\n### 3. Sequence + map to tools (judgement)\nOrder themes by a rough **effort × impact** read (cheap-high-impact first).\nFor each theme, annotate the **target** it would land in: `code` (harness \u002F\nplugin \u002F tooling work in a tracked repo) or `vault-only` (a note\u002FMOC, no\ncode). These are hints, not commitments. Don't assume any particular repo —\nwhich repo `code` maps to is the operator's call.\n\n### 4. Dedup candidate tickets against open Jira (skip when no project configured)\nDedup against the operator's **tracked** Jira project(s) — never a hardcoded\nproject. The tracked keys are the keys of `projects` in the jira metadata\ncache that `\u002Fjira-init` writes (not a secret — project keys + issue types):\n`~\u002F.cache\u002Fhimmel-cli\u002Fjira\u002Fmetadata.json` (POSIX) \u002F\n`%LOCALAPPDATA%\u002Fhimmel-cli\u002Fjira\u002Fmetadata.json` (Windows).\n\nIf the cache is missing or has no projects, **SKIP this step**: emit no Jira\ncandidate list and mark every candidate `(new)` — i.e. vault-only proposals\n(a user who doesn't track this work in Jira gets no spurious ticket\nsuggestions). Otherwise, for each tracked project KEY, fetch open issues (one\nliteral command per project):\n```bash\nnode scripts\u002Fjira\u002Fdist\u002Findex.js list --project \u003CKEY> --status \"To Do,In Progress,Backlog\" --limit 50\n```\nFor each theme you'd propose as a ticket, compare its title against the open\nsummaries across all tracked projects. If an open issue clearly already covers\nit, mark the candidate `already-tracked: \u003CKEY>` and EXCLUDE it from the\n\"propose to file\" list. Only genuinely-new work reaches the candidate list.\n**Do NOT create tickets** — that is the operator's call (and an external write\nthe auto-mode classifier gates).\n\n### 5. Write the roadmap note (skip entirely under `--dry-run` — print instead)\nDeterministic path `60-Maps\u002F\u003CTODAY>-roadmap.md` (`TODAY=$(date +%Y-%m-%d)`).\nIf it already exists, rewrite it in place and add `supersedes:` listing the\nprior content's `generated_at` (idempotent per day). Shape:\n```markdown\n---\ntype: roadmap\ngenerated_at: \u003CISO>\ngenerated_by: \u002Froadmap-clips\nsource_counts: { deferred: N, synthesis-proposal: M, ... }   # = the aggregator's `counts`\n---\n\n# Roadmap — \u003CTODAY>\n\n> Auto-generated by `\u002Froadmap-clips` from the luna vault. Proposals only —\n> nothing here is filed or restructured automatically.\n\n## Themes (sequenced: cheap-high-impact first)\n### 1. \u003Ctheme> — effort:\u003Clo|med|hi> impact:\u003Clo|med|hi> → \u003Ctarget: code|vault-only>\n\u003C1–2 line synthesis>. Supporting items (\u003Ccount>): [[\u003Corigin>]], …\n\n## Candidate tickets (deduped vs open Jira — NOT filed; omitted when no Jira project is configured)\n- [ ] \u003Ctitle> → \u003Ctarget>  (new)\n- ~~\u003Ctitle>~~ already-tracked: \u003CKEY>\n\n## Sources scanned\n\u003Ccounts table from the aggregator JSON>\n```\n\n### 6. Report\nOne summary line: `roadmap-clips: \u003CT> themes from \u003CN> items (\u003CS> sources);\n\u003CC> candidate tickets (\u003CD> deduped vs open Jira). Wrote 60-Maps\u002F\u003CTODAY>-roadmap.md`\n(or `(dry-run, nothing written)`).\n\n## Scope (MVP)\n- Proposals only — no Jira creation, no vault restructuring.\n- Dedup is title-vs-summary judgement, not a guaranteed match; when unsure,\n  keep the candidate and annotate `verify-not-dup`.\n- Read-only aggregation; the only write is the single 60-Maps roadmap note.\n","# roadmap-clips — cross-source roadmap synthesis\n\nYou turn the luna vault's scattered actionable signal into ONE sequenced\nroadmap note in `60-Maps\u002F`. You **propose** — you never auto-file Jira tickets\nand never restructure the vault (same contract as `\u002Fsynthesize-clips`).\n\nDeterministic collection lives in `tools\u002Froadmap-aggregate.mjs` (read-only,\nno network). You do the judgement work: cluster, sequence, map to tools, dedup\ncandidate tickets against open Jira. **NEVER headless:** invoke the tool and the\nJira CLI with the `Bash` tool only — no headless \u002F print-mode claude invocations.\n\n## Inputs\n\n`$ARGUMENTS` (all optional): `[--vault \u003Cpath>] [--dry-run]`.\n- `--vault \u003Cpath>` — luna vault root. Default `$HOME\u002FDocuments\u002Fluna`.\n- `--dry-run` — do everything EXCEPT the final write; print the roadmap to\n  stdout instead.\n\n## Steps\n\n### 1. Aggregate (deterministic)\nRun the aggregator and capture its JSON inventory:\n```bash\nnode \u003Cplugin>\u002Ftools\u002Froadmap-aggregate.mjs [--vault \"$VAULT\"]\n```\n`\u003Cplugin>` = `marketplace\u002Fplugins\u002Fobsidian-triage`. The JSON is\n`{vault, counts, total, items:[{source_type, text, origin, category}]}` with\n`source_type ∈ action-item | deferred | synthesis-proposal | promotion |\ncomponent`. If `total` is 0, print `roadmap-clips: no actionable items found —\nnothing to map` and exit 0.\n\n### 2. Cluster into themes (judgement)\nGroup the items into 3–8 coherent **themes** (e.g. \"vault enrichment depth\",\n\"pipeline automation\", \"source-trust hygiene\"). A theme spans source types —\na `deferred` github ref, a `synthesis-proposal`, and an `action-item` can all\nbelong to the same theme. Note the supporting item count + origins per theme.\nSkip pure noise (e.g. a bare fan-out URL with no thematic signal) but log how\nmany items you dropped so coverage is honest.\n\n### 3. Sequence + map to tools (judgement)\nOrder themes by a rough **effort × impact** read (cheap-high-impact first).\nFor each theme, annotate the **target** it would land in: `code` (harness \u002F\nplugin \u002F tooling work in a tracked repo) or `vault-only` (a note\u002FMOC, no\ncode). These are hints, not commitments. Don't assume any particular repo —\nwhich repo `code` maps to is the operator's call.\n\n### 4. Dedup candidate tickets against open Jira (skip when no project configured)\nDedup against the operator's **tracked** Jira project(s) — never a hardcoded\nproject. The tracked keys are the keys of `projects` in the jira metadata\ncache that `\u002Fjira-init` writes (not a secret — project keys + issue types):\n`~\u002F.cache\u002Fhimmel-cli\u002Fjira\u002Fmetadata.json` (POSIX) \u002F\n`%LOCALAPPDATA%\u002Fhimmel-cli\u002Fjira\u002Fmetadata.json` (Windows).\n\nIf the cache is missing or has no projects, **SKIP this step**: emit no Jira\ncandidate list and mark every candidate `(new)` — i.e. vault-only proposals\n(a user who doesn't track this work in Jira gets no spurious ticket\nsuggestions). Otherwise, for each tracked project KEY, fetch open issues (one\nliteral command per project):\n```bash\nnode scripts\u002Fjira\u002Fdist\u002Findex.js list --project \u003CKEY> --status \"To Do,In Progress,Backlog\" --limit 50\n```\nFor each theme you'd propose as a ticket, compare its title against the open\nsummaries across all tracked projects. If an open issue clearly already covers\nit, mark the candidate `already-tracked: \u003CKEY>` and EXCLUDE it from the\n\"propose to file\" list. Only genuinely-new work reaches the candidate list.\n**Do NOT create tickets** — that is the operator's call (and an external write\nthe auto-mode classifier gates).\n\n### 5. Write the roadmap note (skip entirely under `--dry-run` — print instead)\nDeterministic path `60-Maps\u002F\u003CTODAY>-roadmap.md` (`TODAY=$(date +%Y-%m-%d)`).\nIf it already exists, rewrite it in place and add `supersedes:` listing the\nprior content's `generated_at` (idempotent per day). Shape:\n```markdown\n---\ntype: roadmap\ngenerated_at: \u003CISO>\ngenerated_by: \u002Froadmap-clips\nsource_counts: { deferred: N, synthesis-proposal: M, ... }   # = the aggregator's `counts`\n---\n\n# Roadmap — \u003CTODAY>\n\n> Auto-generated by `\u002Froadmap-clips` from the luna vault. Proposals only —\n> nothing here is filed or restructured automatically.\n\n## Themes (sequenced: cheap-high-impact first)\n### 1. \u003Ctheme> — effort:\u003Clo|med|hi> impact:\u003Clo|med|hi> → \u003Ctarget: code|vault-only>\n\u003C1–2 line synthesis>. Supporting items (\u003Ccount>): [[\u003Corigin>]], …\n\n## Candidate tickets (deduped vs open Jira — NOT filed; omitted when no Jira project is configured)\n- [ ] \u003Ctitle> → \u003Ctarget>  (new)\n- ~~\u003Ctitle>~~ already-tracked: \u003CKEY>\n\n## Sources scanned\n\u003Ccounts table from the aggregator JSON>\n```\n\n### 6. Report\nOne summary line: `roadmap-clips: \u003CT> themes from \u003CN> items (\u003CS> sources);\n\u003CC> candidate tickets (\u003CD> deduped vs open Jira). Wrote 60-Maps\u002F\u003CTODAY>-roadmap.md`\n(or `(dry-run, nothing written)`).\n\n## Scope (MVP)\n- Proposals only — no Jira creation, no vault restructuring.\n- Dedup is title-vs-summary judgement, not a guaranteed match; when unsure,\n  keep the candidate and annotate `verify-not-dup`.\n- Read-only aggregation; the only write is the single 60-Maps roadmap note.\n",{"name":5,"description":7},"main","2a00f5c1203047a27ae79f5626e1ae4d34f03c79","marketplace\u002Fplugins\u002Fobsidian-triage\u002Fskills\u002Froadmap-clips",2,"https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel","https:\u002F\u002Fyotamleo-org.github.io\u002FHimmel\u002F","https:\u002F\u002Fgithub.com\u002Fyotamleo-org","2026-11-15 05:10:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add yotamleo-org\u002FHimmel --skill roadmap-clips",{"tool":37,"command":38},"bunx","bunx skills add yotamleo-org\u002FHimmel --skill roadmap-clips",{"tool":40,"command":41},"pnpm","pnpm dlx skills add yotamleo-org\u002FHimmel --skill roadmap-clips","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fmarketplace\u002Fplugins\u002Fobsidian-triage\u002Fskills\u002Froadmap-clips\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M75TY3C1HJV3PACB8R2FTAX7","medic","Use inside a Salus medical vault to FILE a medical item into its structured place (skin photo → photo archive + capture note; lesion\u002Fsymptom note; lab\u002FPDF → 00-Sources) and auto-commit, OR to QUERY the vault for a health follow-up (grounded answer + flagged, non-diagnostic morphology read). Triggers on \"file this photo \u002F note \u002F lab\", \"log this into the medical vault\", \"ask the medic\", or any health follow-up while cwd = the medical vault. Organize & surface only — never diagnose (posture-A).","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Ftemplates\u002Fluna-second-brain\u002F_profiles\u002Fsalus\u002F.claude\u002Fskills\u002Fmedic\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75TY1AV2E5DECQFSGZ01FQ3","stuck-playbook","fixture skill, invoked in the basic transcript fixture","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Ftool-usage\u002Fskills\u002F.claude\u002Fskills\u002Fstuck-playbook\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75TY05TH00N1KX4H0W1AASQ","never-used-skill","fixture skill, never invoked in any fixture transcript","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Ftool-usage\u002Fskills-config\u002Fskills\u002Fnever-used-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M75TXV4XKHHV36JKHPXK0QAN","used-skill","fixture skill invoked via a Skill tool_use in the fixture transcript","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Fdead-parts\u002Fbasic-repo\u002F.claude\u002Fskills\u002Fused-skill\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75TXJYNA5BQWC5WWZN4HY95","dead-skill","fixture skill never invoked and never referenced","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fscripts\u002Flanes\u002Fbench\u002Fscorecard\u002Ffixtures\u002Fdead-parts\u002Fbasic-repo\u002F.claude\u002Fskills\u002Fdead-skill\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75TXAB3RCTMWB02GEKDT17Q","jira-transition","Move\u002Ftransition a Jira issue status (\"move PROJ-46 to In Progress\"). Needs key + target status. Not PR status changes.","https:\u002F\u002Fgithub.com\u002Fyotamleo-org\u002FHimmel\u002Fblob\u002Fmain\u002Fplugins\u002Fhimmel-jira\u002Fskills\u002Fjira-transition\u002FSKILL.md",[],[]]