[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DWV8KCEF0H0DVH5TA47VR":3,"skill-same:01M79DWV8KCEF0H0DVH5TA47VR":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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79DWV8KCEF0H0DVH5TA47VR","executing-plans",null,"Use when you have a written implementation plan to execute in a separate session with review checkpoints","spectroscope\u002Fspectroscope","spectroscope","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F306844128?v=4","01M79DQ3TDVZFVMDAQXV630F1E","Christopher Ezell","01M79DQ3V1TGB9HT87FJG4Y06A",2,"MIT","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Fmain\u002Fresources\u002Fbundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fexecuting-plans\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: executing-plans\ndescription: Use when you have a written implementation plan to execute in a separate session with review checkpoints\n---\n\n# Executing Plans\n\n## Overview\n\nLoad plan, review critically, execute all tasks, report when complete.\n\n**Announce at start:** \"I'm using the executing-plans skill to implement this plan.\"\n\n**Note:** Tell your human partner that spectropowers works much better with access to subagents (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in `..\u002Fusing-spectropowers\u002Freferences\u002F`). If subagents are available, use spectropowers:subagent-driven-development instead of this skill.\n\n## The Process\n\n### Step 1: Load and Review Plan\n1. Ensure an isolated workspace: use spectropowers:using-git-worktrees to create one or verify the existing one\n2. Read plan file\n3. Review critically: identify any questions or concerns about the plan\n4. If concerns: Raise them with your human partner before starting\n5. If no concerns: Create todos for the plan items and proceed\n\n### Step 2: Execute Tasks\n\nFor each task:\n1. Mark as in_progress\n2. Follow each step exactly (plan has bite-sized steps)\n3. Run verifications as specified\n4. Mark as completed; progress goes into TASKS.md after every task\n\n### Step 3: Complete Development\n\nAfter all tasks complete and verified:\n- Announce: \"I'm using the finishing-a-development-branch skill to complete this work.\"\n- **REQUIRED SUB-SKILL:** Use spectropowers:finishing-a-development-branch\n- Follow that skill to verify tests, present options, execute choice\n\n## When to Stop and Ask for Help\n\n**STOP executing immediately when:**\n- Hit a blocker (missing dependency, test fails, instruction unclear)\n- Plan has critical gaps preventing starting\n- You don't understand an instruction\n- Verification fails repeatedly\n- A plan conflict that touches architecture, language, repository or scope: stop and ask the owner; never rule on it.\n\n**Ask for clarification rather than guessing.**\n\n## When to Revisit Earlier Steps\n\n**Return to Review (Step 1) when:**\n- Partner updates the plan based on your feedback\n- Fundamental approach needs rethinking\n\n**Don't force through blockers**: stop and ask.\n\n## Remember\n- Review plan critically first\n- Follow plan steps exactly\n- Don't skip verifications\n- Reference skills when plan says to\n- Stop when blocked, don't guess\n- Never start implementation on main\u002Fmaster branch without explicit user consent\n","# Executing Plans\n\n## Overview\n\nLoad plan, review critically, execute all tasks, report when complete.\n\n**Announce at start:** \"I'm using the executing-plans skill to implement this plan.\"\n\n**Note:** Tell your human partner that spectropowers works much better with access to subagents (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in `..\u002Fusing-spectropowers\u002Freferences\u002F`). If subagents are available, use spectropowers:subagent-driven-development instead of this skill.\n\n## The Process\n\n### Step 1: Load and Review Plan\n1. Ensure an isolated workspace: use spectropowers:using-git-worktrees to create one or verify the existing one\n2. Read plan file\n3. Review critically: identify any questions or concerns about the plan\n4. If concerns: Raise them with your human partner before starting\n5. If no concerns: Create todos for the plan items and proceed\n\n### Step 2: Execute Tasks\n\nFor each task:\n1. Mark as in_progress\n2. Follow each step exactly (plan has bite-sized steps)\n3. Run verifications as specified\n4. Mark as completed; progress goes into TASKS.md after every task\n\n### Step 3: Complete Development\n\nAfter all tasks complete and verified:\n- Announce: \"I'm using the finishing-a-development-branch skill to complete this work.\"\n- **REQUIRED SUB-SKILL:** Use spectropowers:finishing-a-development-branch\n- Follow that skill to verify tests, present options, execute choice\n\n## When to Stop and Ask for Help\n\n**STOP executing immediately when:**\n- Hit a blocker (missing dependency, test fails, instruction unclear)\n- Plan has critical gaps preventing starting\n- You don't understand an instruction\n- Verification fails repeatedly\n- A plan conflict that touches architecture, language, repository or scope: stop and ask the owner; never rule on it.\n\n**Ask for clarification rather than guessing.**\n\n## When to Revisit Earlier Steps\n\n**Return to Review (Step 1) when:**\n- Partner updates the plan based on your feedback\n- Fundamental approach needs rethinking\n\n**Don't force through blockers**: stop and ask.\n\n## Remember\n- Review plan critically first\n- Follow plan steps exactly\n- Don't skip verifications\n- Reference skills when plan says to\n- Stop when blocked, don't guess\n- Never start implementation on main\u002Fmaster branch without explicit user consent\n",{"name":5,"description":7},"main","4ee98acbdee77bbc9d0b989ac8c3d7421963b1c2","spectro-server\u002Fsrc\u002Fmain\u002Fresources\u002Fbundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fexecuting-plans",1,"https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope","https:\u002F\u002Fspectroscope.ai","https:\u002F\u002Fgithub.com\u002Fspectroscope","2026-11-11 07:30:30",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add spectroscope\u002Fspectroscope --skill executing-plans",{"tool":38,"command":39},"bunx","bunx skills add spectroscope\u002Fspectroscope --skill executing-plans",{"tool":41,"command":42},"pnpm","pnpm dlx skills add spectroscope\u002Fspectroscope --skill executing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Fmain\u002Fresources\u002Fbundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fexecuting-plans\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},"01M79DY61ZW6AS4ZXPGPK8CYQM","brainstorming","Test fixture skill.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Ftest-bundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fbrainstorming\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},"01M79DY3K5E2S4F9CK4QA4V1VD","s","A fixture skill.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Fspectrolyzr-fixture\u002Fbundle\u002Fskills\u002Fs\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},"01M79DY2H81J251GQT8M9SYXJ2","beta","The second skill of the fixture plugin.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Fplugin-fixture\u002Ffixture\u002Fskills\u002Fbeta\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},"01M79DY1CTTH4EH1WTKDH8379N","alpha","The first skill of the fixture plugin.","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Ftest\u002Fresources\u002Fplugin-fixture\u002Ffixture\u002Fskills\u002Falpha\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},"01M79DXWTRCQD2XM27K0V8MY50","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Fmain\u002Fresources\u002Fbundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fwriting-skills\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},"01M79DXTXR39NVJX3KBX8ZE44P","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fspectroscope\u002Fspectroscope\u002Fblob\u002Fmain\u002Fspectro-server\u002Fsrc\u002Fmain\u002Fresources\u002Fbundled-playbooks\u002Fspectro\u002Fskills\u002Fspectropowers\u002Fwriting-plans\u002FSKILL.md",[],[]]