[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75EAFE3C3MTSRCZEF43VTFT":3,"skill-same:01M75EAFE3C3MTSRCZEF43VTFT":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75EAFE3C3MTSRCZEF43VTFT","make-plan",null,"Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.","Army161\u002Fclaude-mem","Army161","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F186505093?v=4","01M6DGVVYW0939ESSV7SRCV1TE","Army","01M75E9DADERQH0ZP528KB0PEM",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmake-plan\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: make-plan\ndescription: Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.\n---\n\n# Make Plan\n\nYou are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.\n\n## Delegation Model\n\nUse subagents for *fact gathering and extraction* (docs, examples, signatures, grep results). Keep *synthesis and plan authoring* with the orchestrator (phase boundaries, task framing, final wording). If a subagent report is incomplete or lacks evidence, re-check with targeted reads\u002Fgreps before finalizing.\n\n### Subagent Reporting Contract (MANDATORY)\n\nEach subagent response must include:\n1. Sources consulted (files\u002FURLs) and what was read\n2. Concrete findings (exact API names\u002Fsignatures; exact file paths\u002Flocations)\n3. Copy-ready snippet locations (example files\u002Fsections to copy)\n4. \"Confidence\" note + known gaps (what might still be missing)\n\nReject and redeploy the subagent if it reports conclusions without sources.\n\n## Plan Structure\n\n### Phase 0: Documentation Discovery (ALWAYS FIRST)\n\nBefore planning implementation, deploy \"Documentation Discovery\" subagents to:\n1. Search for and read relevant documentation, examples, and existing patterns\n2. Identify the actual APIs, methods, and signatures available (not assumed)\n3. Create a brief \"Allowed APIs\" list citing specific documentation sources\n4. Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)\n\nThe orchestrator consolidates findings into a single Phase 0 output.\n\n### Each Implementation Phase Must Include\n\n1. **What to implement** — Frame tasks to COPY from docs, not transform existing code\n   - Good: \"Copy the V2 session pattern from docs\u002Fexamples.ts:45-60\"\n   - Bad: \"Migrate the existing code to V2\"\n2. **Documentation references** — Cite specific files\u002Flines for patterns to follow\n3. **Verification checklist** — How to prove this phase worked (tests, grep checks)\n4. **Anti-pattern guards** — What NOT to do (invented APIs, undocumented params)\n\n### Final Phase: Verification\n\n1. Verify all implementations match documentation\n2. Check for anti-patterns (grep for known bad patterns)\n3. Run tests to confirm functionality\n\n## Key Principles\n\n- Documentation Availability ≠ Usage: Explicitly require reading docs\n- Task Framing Matters: Direct agents to docs, not just outcomes\n- Verify > Assume: Require proof, not assumptions about APIs\n- Session Boundaries: Each phase should be self-contained with its own doc references\n\n## Anti-Patterns to Prevent\n\n- Inventing API methods that \"should\" exist\n- Adding parameters not in documentation\n- Skipping verification steps\n- Assuming structure without checking examples\n\n## See Also\n\n- `oh-my-issues` — the issue-side sibling. When the plan you're being asked to make is rooted in a bug or feature backlog rather than a fresh idea, route through `oh-my-issues` first to cluster issues by root cause into plan masters and `plans\u002F0X-*.md` design docs. `make-plan` then operates on the design doc for one plan slice.\n","# Make Plan\n\nYou are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.\n\n## Delegation Model\n\nUse subagents for *fact gathering and extraction* (docs, examples, signatures, grep results). Keep *synthesis and plan authoring* with the orchestrator (phase boundaries, task framing, final wording). If a subagent report is incomplete or lacks evidence, re-check with targeted reads\u002Fgreps before finalizing.\n\n### Subagent Reporting Contract (MANDATORY)\n\nEach subagent response must include:\n1. Sources consulted (files\u002FURLs) and what was read\n2. Concrete findings (exact API names\u002Fsignatures; exact file paths\u002Flocations)\n3. Copy-ready snippet locations (example files\u002Fsections to copy)\n4. \"Confidence\" note + known gaps (what might still be missing)\n\nReject and redeploy the subagent if it reports conclusions without sources.\n\n## Plan Structure\n\n### Phase 0: Documentation Discovery (ALWAYS FIRST)\n\nBefore planning implementation, deploy \"Documentation Discovery\" subagents to:\n1. Search for and read relevant documentation, examples, and existing patterns\n2. Identify the actual APIs, methods, and signatures available (not assumed)\n3. Create a brief \"Allowed APIs\" list citing specific documentation sources\n4. Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)\n\nThe orchestrator consolidates findings into a single Phase 0 output.\n\n### Each Implementation Phase Must Include\n\n1. **What to implement** — Frame tasks to COPY from docs, not transform existing code\n   - Good: \"Copy the V2 session pattern from docs\u002Fexamples.ts:45-60\"\n   - Bad: \"Migrate the existing code to V2\"\n2. **Documentation references** — Cite specific files\u002Flines for patterns to follow\n3. **Verification checklist** — How to prove this phase worked (tests, grep checks)\n4. **Anti-pattern guards** — What NOT to do (invented APIs, undocumented params)\n\n### Final Phase: Verification\n\n1. Verify all implementations match documentation\n2. Check for anti-patterns (grep for known bad patterns)\n3. Run tests to confirm functionality\n\n## Key Principles\n\n- Documentation Availability ≠ Usage: Explicitly require reading docs\n- Task Framing Matters: Direct agents to docs, not just outcomes\n- Verify > Assume: Require proof, not assumptions about APIs\n- Session Boundaries: Each phase should be self-contained with its own doc references\n\n## Anti-Patterns to Prevent\n\n- Inventing API methods that \"should\" exist\n- Adding parameters not in documentation\n- Skipping verification steps\n- Assuming structure without checking examples\n\n## See Also\n\n- `oh-my-issues` — the issue-side sibling. When the plan you're being asked to make is rooted in a bug or feature backlog rather than a fresh idea, route through `oh-my-issues` first to cluster issues by root cause into plan masters and `plans\u002F0X-*.md` design docs. `make-plan` then operates on the design doc for one plan slice.\n",{"name":5,"description":7},"main","f267d1d43b9b6652831c7ceff8084a556a25480e","plugin\u002Fskills\u002Fmake-plan","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem","https:\u002F\u002Fclaude-mem.ai","https:\u002F\u002Fgithub.com\u002FArmy161","2026-06-08 09:47:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Army161\u002Fclaude-mem --skill make-plan",{"tool":37,"command":38},"bunx","bunx skills add Army161\u002Fclaude-mem --skill make-plan",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Army161\u002Fclaude-mem --skill make-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmake-plan\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":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M75EBRGWMKS32YFREXFJ623A","wowerpoint","Turn one document into a kawaii NotebookLM slide-deck PDF. Use for \"wowerpoint this\", \"make a deck about \u003Cfile>\", \"turn this report into slides\", or any request to render a single document as shareable narrative slides.","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwowerpoint\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M75EBKGD69FA93DCRGSCC8R8","weekly-digests","Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for \"weekly digests\", \"week-by-week story\", \"serial timeline\", or \"narrative chapters\" of a project's history.","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fweekly-digests\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75EBFK435Q3VB3CYJW680FQ","claude-code-plugin-release","Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, npm publishing (so `npx claude-mem@X.Y.Z` resolves), build verification, git tagging, GitHub releases, and changelog generation.","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fversion-bump\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75EBBSB42HSSEHMM4X6N5S7","timeline-report","Generate a \"Journey Into [Project]\" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Ftimeline-report\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75EB2GS174TBH3CDJ1DQCAT","standup","Convene the recently-active git worktrees as named agents in a markdown group\nchat, have them reconcile what each changed, and converge on ONE consolidated\nworktree. Each branch is an agent that posts to a shared STANDUP.md (YAML front\nmatter holds the GOAL + PROMPT; the body is the chat log), then the room agrees\non a merge order and a single consolidation plan in the SUMMATION. The room is\nfilled either by time window (past 1h \u002F 4h \u002F 24h \u002F 7d \u002F all — only worktrees\nactive in it join, so a 40-worktree machine collapses to the handful you\nactually touched) or by hand-picking specific worktrees and\u002For open GitHub PRs\nfrom a checkbox-style list. Use this skill whenever the user says \"standup\",\n\"run the standup\", \"reconcile my worktrees\", \"consolidate worktrees\", \"merge\nthese branches together\", \"merge these PRs\", \"combine these worktrees and pull\nrequests\", \"what's everyone at\", \"have my worktrees check in\", or wants several\nbranch-named agents to coordinate \u002F resolve overlapping work into one\ndeliverable through a shared chat file — even if they don't say the word\n\"standup\".","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fstandup\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75EAZK62HZ4YEAN5Q919XXA","smart-explore","Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.","https:\u002F\u002Fgithub.com\u002FArmy161\u002Fclaude-mem\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fsmart-explore\u002FSKILL.md",[],[]]