[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757CXSDPE8N6M2FSJ9812X9":3,"skill-same:01M757CXSDPE8N6M2FSJ9812X9":46},{"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":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M757CXSDPE8N6M2FSJ9812X9","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.","chicago-joe\u002Fmanymems","chicago-joe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28772631?v=4","01M757BH8BAJCECP10RF770KGX","Joseph Loss","01M757BH9GKTF48WY2ZDYSQYF1",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fchicago-joe\u002Fmanymems\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","9351205c08d659f36c13c5930b2ce612ff448bbe","plugin\u002Fskills\u002Fmake-plan","https:\u002F\u002Fgithub.com\u002Fchicago-joe\u002Fmanymems","https:\u002F\u002Fgithub.com\u002Fchicago-joe","https:\u002F\u002Fchicagojoe.dev","M.S. Financial Engineering 2019\r\nUniversity of Illinois at Urbana-Champaign","2026-06-10 05:58:26",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add chicago-joe\u002Fmanymems --skill make-plan",{"tool":38,"command":39},"bunx","bunx skills add chicago-joe\u002Fmanymems --skill make-plan",{"tool":41,"command":42},"pnpm","pnpm dlx skills add chicago-joe\u002Fmanymems --skill make-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fchicago-joe\u002Fmanymems\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fmake-plan\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M76TW5JVMBEGA7V98MC16WKH","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\u002Fchicago-joe\u002Fmanymems\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwowerpoint\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M76TW3G047YPZRM2DK0YRBXR","what-happened","Investigate why a code block changed using provenance and observations. Use when the user asks \"why did this change\", \"what broke here\", \"what session produced this commit\".","https:\u002F\u002Fgithub.com\u002Fchicago-joe\u002Fmanymems\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fwhat-happened\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M76TVXD5JVZ6Q1MFA68JSZ04","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\u002Fchicago-joe\u002Fmanymems\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fweekly-digests\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M76TVT491VCH2YDQA4XVVFFM","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\u002Fchicago-joe\u002Fmanymems\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fversion-bump\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M757DSBWAR27JRAX6QPGDAP6","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\u002Fchicago-joe\u002Fmanymems\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Ftimeline-report\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M757DNBBDV4NTAPJ9HNQHSTE","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\u002Fchicago-joe\u002Fmanymems\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fsmart-explore\u002FSKILL.md",[],[]]