[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7319W6CDGCB7YCC0RSF57VF":3,"skill-same:01M7319W6CDGCB7YCC0RSF57VF":62},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M7319W6CDGCB7YCC0RSF57VF","plan",null,"Plan mode: write markdown plan to .cogitum\u002Fplans\u002F, no exec.","StarryCod\u002Fcogitum","StarryCod","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F200964623?v=4","01M7311AM3RY259SYKGHWBEDN0","OpenReason","01M7311AMRC1PBSTYZWSD1AQFJ",12,"MIT","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: plan\ndescription: \"Plan mode: write markdown plan to .cogitum\u002Fplans\u002F, no exec.\"\nversion: 1.0.0\nauthor: Cogitum\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  cogitum:\n    tags: [planning, plan-mode, implementation, workflow]\n    related_skills: [writing-plans, subagent-driven-development]\n---\n\n# Plan Mode\n\nUse this skill when the user wants a plan instead of execution.\n\n## Core behavior\n\nFor this turn, you are planning only.\n\n- Do not implement code.\n- Do not edit project files except the plan markdown file.\n- Do not run mutating terminal commands, commit, push, or perform external actions.\n- You may inspect the repo or other context with read-only commands\u002Ftools when needed.\n- Your deliverable is a markdown plan saved inside the active workspace under `.cogitum\u002Fplans\u002F`.\n\n## Output requirements\n\nWrite a markdown plan that is concrete and actionable.\n\nInclude, when relevant:\n- Goal\n- Current context \u002F assumptions\n- Proposed approach\n- Step-by-step plan\n- Files likely to change\n- Tests \u002F validation\n- Risks, tradeoffs, and open questions\n\nIf the task is code-related, include exact file paths, likely test targets, and verification steps.\n\n## Save location\n\nSave the plan with `write_file` under:\n- `.cogitum\u002Fplans\u002FYYYY-MM-DD_HHMMSS-\u003Cslug>.md`\n\nTreat that as relative to the active working directory \u002F backend workspace. Cogitum file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.\n\nIf the runtime provides a specific target path, use that exact path.\nIf not, create a sensible timestamped filename yourself under `.cogitum\u002Fplans\u002F`.\n\n## Interaction style\n\n- If the request is clear enough, write the plan directly.\n- If no explicit instruction accompanies `\u002Fplan`, infer the task from the current conversation context.\n- If it is genuinely underspecified, ask a brief clarifying question instead of guessing.\n- After saving the plan, reply briefly with what you planned and the saved path.\n","# Plan Mode\n\nUse this skill when the user wants a plan instead of execution.\n\n## Core behavior\n\nFor this turn, you are planning only.\n\n- Do not implement code.\n- Do not edit project files except the plan markdown file.\n- Do not run mutating terminal commands, commit, push, or perform external actions.\n- You may inspect the repo or other context with read-only commands\u002Ftools when needed.\n- Your deliverable is a markdown plan saved inside the active workspace under `.cogitum\u002Fplans\u002F`.\n\n## Output requirements\n\nWrite a markdown plan that is concrete and actionable.\n\nInclude, when relevant:\n- Goal\n- Current context \u002F assumptions\n- Proposed approach\n- Step-by-step plan\n- Files likely to change\n- Tests \u002F validation\n- Risks, tradeoffs, and open questions\n\nIf the task is code-related, include exact file paths, likely test targets, and verification steps.\n\n## Save location\n\nSave the plan with `write_file` under:\n- `.cogitum\u002Fplans\u002FYYYY-MM-DD_HHMMSS-\u003Cslug>.md`\n\nTreat that as relative to the active working directory \u002F backend workspace. Cogitum file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.\n\nIf the runtime provides a specific target path, use that exact path.\nIf not, create a sensible timestamped filename yourself under `.cogitum\u002Fplans\u002F`.\n\n## Interaction style\n\n- If the request is clear enough, write the plan directly.\n- If no explicit instruction accompanies `\u002Fplan`, infer the task from the current conversation context.\n- If it is genuinely underspecified, ask a brief clarifying question instead of guessing.\n- After saving the plan, reply briefly with what you planned and the saved path.\n",{"name":5,"author":24,"license":15,"version":25,"metadata":26,"platforms":36,"description":7},"Cogitum","1.0.0",{"cogitum":27},{"tags":28,"related_skills":33},[29,30,31,32],"planning","plan-mode","implementation","workflow",[34,35],"writing-plans","subagent-driven-development",[37,38,39],"linux","macos","windows","master","a99de210a5d82a24b7aa5020afa1f904f595d14c","cogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fplan",0,"https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fcogitum","https:\u002F\u002Fgithub.com\u002FStarryCod","2026-05-25 23:49:07",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add StarryCod\u002Fcogitum --skill plan",{"tool":54,"command":55},"bunx","bunx skills add StarryCod\u002Fcogitum --skill plan",{"tool":57,"command":58},"pnpm","pnpm dlx skills add StarryCod\u002Fcogitum --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",true,[],[63,70,77,83,90,97],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M731AYJQFFAGEQ8T8NMPKM72","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M731AWAHBZQ4JG5HBRXSTEWP","tg-moderator","Telegram chat moderator\u002Fcompanion mode. No tools, conversational only.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Ftg-moderator\u002FSKILL.md",[],[],{"skillNo":78,"name":34,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M731AS9N89S2E50MSW2Y9QYY","Write implementation plans: bite-sized tasks, paths, code.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M731ANESTYGBFV3XSAT0AS8Q","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M731AG1KE7ZHM0P1R890ZVB0","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[],[],{"skillNo":98,"name":35,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M731ABWQ3DTCBY8E6WTYSBTT","Execute plans via delegate_task subagents (2-stage review).","https:\u002F\u002Fgithub.com\u002FStarryCod\u002Fcogitum\u002Fblob\u002Fmaster\u002Fcogitum\u002Fdata\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[],[]]