[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EP9YHD2ZCCRBA7ZSW87QD8":3,"skill-same:01M7EP9YHD2ZCCRBA7ZSW87QD8":52},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7EP9YHD2ZCCRBA7ZSW87QD8","openspec-update-change",null,"Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fopenspec-update-change-vanehub-ai\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: openspec-update-change\ndescription: Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.\nallowed-tools: Bash(openspec:*)\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.8.0\"\n---\n\nRevise a change's existing planning artifacts and keep them coherent. Never edit code.\n\n**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store \u003Cid>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store \u003Cid>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change \"\u003Cname>\" --json --store \"\u003Cid>\"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec\u002F` root.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n`\u002Fopsx:continue` is an expanded-profile workflow and may not be installed. Before suggesting it anywhere below, verify that it is available. If it is unavailable, `openspec status --change \"\u003Cname>\" --json` shows the next artifact and `openspec instructions \"\u003Cartifact-id>\" --change \"\u003Cname>\" --json` explains how to create it.\n\n**Steps**\n\n1. **Select the change**\n\n   If a name is provided, use it. Otherwise:\n   - Infer from conversation context if the user mentioned a change\n   - Auto-select if only one active change exists\n   - If ambiguous, run `openspec list --json` to get available changes sorted by most recently modified, and ask the user to select one\n\n   When prompting, present the top 3-4 most recently modified changes as options, showing:\n   - Change name\n   - Schema (from `schema` field if present, otherwise \"spec-driven\")\n   - Status (e.g., \"0\u002F5 tasks\", \"complete\", \"no tasks\")\n   - How recently it was modified (from `lastModified` field)\n\n   Mark the most recently modified change as \"(Recommended)\" since it's likely what the user wants to update.\n\n   Always announce: \"Using change: \u003Cname>\" and how to override (e.g., `\u002Fopsx:update \u003Cother>`).\n\n2. **Get the change's artifacts**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand current state. The response includes:\n   - `schemaName`: The workflow schema being used (e.g., \"spec-driven\")\n   - `artifacts`: Array of artifacts with their status (\"done\", \"skipped\", \"ready\", \"blocked\")\n   - `isPlanningComplete`: Boolean indicating if all planning artifacts are complete. Older CLI versions expose the same value as `isComplete`.\n   - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.\n\n   The artifact ids and paths come from the active schema - do NOT assume them, and do NOT branch on hardcoded artifact names. Custom schemas must work unchanged.\n\n   The files to edit are `artifactPaths.\u003Cid>.existingOutputPaths` - the concrete files that exist on disk, already glob-expanded for glob artifacts (e.g. `specs\u002F**\u002F*.md`). Do NOT write to `resolvedOutputPath`: for a glob artifact it is still the glob pattern, not a real file.\n\n3. **Understand the request**\n   - If the user asked for a specific revision (\"the design now uses X\"), that is the starting edit.\n   - If they only said \"update\" \u002F \"make this coherent\", treat it as a coherence review: read the existing artifacts and check them against each other for contradictions, gaps, and duplication.\n\n4. **Read and reconcile**\n   - Read the artifact(s) the request touches and the change's other existing artifacts.\n   - Apply the requested edit. Then check every other existing artifact against it - in ANY direction: an edit to a later artifact may require revising an earlier one, not only the other way around. Build order is a useful reading order, not a constraint on which artifacts may be revised.\n   - Note everything that is now inconsistent, missing, or contradictory.\n   - Revise only files that already exist (`existingOutputPaths`). Do NOT create artifacts that don't exist yet, and do NOT invent new files under a glob artifact - note them and point the user to `\u002Fopsx:continue` to create them.\n   - If the change is already coherent, say so and make no edits.\n\n5. **Confirm and apply, one artifact at a time**\n   - Show each proposed revision and why. Write only after the user confirms.\n   - If the user rejects a revision, do not write it - leave that artifact unchanged.\n   - When a substantial rewrite is needed, get that artifact's rules and template first:\n     ```bash\n     openspec instructions \"\u003Cartifact-id>\" --change \"\u003Cname>\" --json\n     ```\n\n6. **Point to the next step (guidance only - NEVER act on it)**\n   - Artifacts still missing -> suggest `\u002Fopsx:continue` to create them.\n   - Change already implemented (tasks checked off \u002F already applied) -> the code may no longer match the revised plan; suggest `\u002Fopsx:apply` to carry the delta into code.\n   - Everything done and implemented -> suggest `\u002Fopsx:archive`.\n\n**Output**\n\nAfter each invocation, show:\n- Which artifacts were revised (and which proposed revisions were rejected)\n- Anything deferred to `\u002Fopsx:continue` (not-yet-created artifacts or files)\n- Where the change stands and the recommended next command\n\n**Guardrails**\n- Planning artifacts only - NEVER edit implementation code. If the revised plan implies code changes, stop and point to `\u002Fopsx:apply`.\n- Use the artifact ids and paths reported by `openspec status`; never branch on hardcoded artifact names.\n- Edit only the concrete files in `existingOutputPaths`; never write to a glob `resolvedOutputPath`.\n- Do not advance the build frontier: no new artifacts, no new files under glob artifacts - that is `\u002Fopsx:continue`'s job.\n- Confirm every edit with the user before writing.\n- If the request changes the change's *intent* rather than refining it, first verify whether the expanded-profile `\u002Fopsx:new` workflow is available. If it is, recommend starting fresh with `\u002Fopsx:new` (the \"Update vs. Start Fresh\" heuristic). If it is unavailable, ask for a distinct unused change name and recommend `openspec new change \"\u003Cnew-change-name>\"` instead.\n","Revise a change's existing planning artifacts and keep them coherent. Never edit code.\n\n**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store \u003Cid>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`, `view`). Once selected, treat `--store \u003Cid>` as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run `openspec status --change \"\u003Cname>\" --json --store \"\u003Cid>\"`, not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec\u002F` root.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n`\u002Fopsx:continue` is an expanded-profile workflow and may not be installed. Before suggesting it anywhere below, verify that it is available. If it is unavailable, `openspec status --change \"\u003Cname>\" --json` shows the next artifact and `openspec instructions \"\u003Cartifact-id>\" --change \"\u003Cname>\" --json` explains how to create it.\n\n**Steps**\n\n1. **Select the change**\n\n   If a name is provided, use it. Otherwise:\n   - Infer from conversation context if the user mentioned a change\n   - Auto-select if only one active change exists\n   - If ambiguous, run `openspec list --json` to get available changes sorted by most recently modified, and ask the user to select one\n\n   When prompting, present the top 3-4 most recently modified changes as options, showing:\n   - Change name\n   - Schema (from `schema` field if present, otherwise \"spec-driven\")\n   - Status (e.g., \"0\u002F5 tasks\", \"complete\", \"no tasks\")\n   - How recently it was modified (from `lastModified` field)\n\n   Mark the most recently modified change as \"(Recommended)\" since it's likely what the user wants to update.\n\n   Always announce: \"Using change: \u003Cname>\" and how to override (e.g., `\u002Fopsx:update \u003Cother>`).\n\n2. **Get the change's artifacts**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Parse the JSON to understand current state. The response includes:\n   - `schemaName`: The workflow schema being used (e.g., \"spec-driven\")\n   - `artifacts`: Array of artifacts with their status (\"done\", \"skipped\", \"ready\", \"blocked\")\n   - `isPlanningComplete`: Boolean indicating if all planning artifacts are complete. Older CLI versions expose the same value as `isComplete`.\n   - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.\n\n   The artifact ids and paths come from the active schema - do NOT assume them, and do NOT branch on hardcoded artifact names. Custom schemas must work unchanged.\n\n   The files to edit are `artifactPaths.\u003Cid>.existingOutputPaths` - the concrete files that exist on disk, already glob-expanded for glob artifacts (e.g. `specs\u002F**\u002F*.md`). Do NOT write to `resolvedOutputPath`: for a glob artifact it is still the glob pattern, not a real file.\n\n3. **Understand the request**\n   - If the user asked for a specific revision (\"the design now uses X\"), that is the starting edit.\n   - If they only said \"update\" \u002F \"make this coherent\", treat it as a coherence review: read the existing artifacts and check them against each other for contradictions, gaps, and duplication.\n\n4. **Read and reconcile**\n   - Read the artifact(s) the request touches and the change's other existing artifacts.\n   - Apply the requested edit. Then check every other existing artifact against it - in ANY direction: an edit to a later artifact may require revising an earlier one, not only the other way around. Build order is a useful reading order, not a constraint on which artifacts may be revised.\n   - Note everything that is now inconsistent, missing, or contradictory.\n   - Revise only files that already exist (`existingOutputPaths`). Do NOT create artifacts that don't exist yet, and do NOT invent new files under a glob artifact - note them and point the user to `\u002Fopsx:continue` to create them.\n   - If the change is already coherent, say so and make no edits.\n\n5. **Confirm and apply, one artifact at a time**\n   - Show each proposed revision and why. Write only after the user confirms.\n   - If the user rejects a revision, do not write it - leave that artifact unchanged.\n   - When a substantial rewrite is needed, get that artifact's rules and template first:\n     ```bash\n     openspec instructions \"\u003Cartifact-id>\" --change \"\u003Cname>\" --json\n     ```\n\n6. **Point to the next step (guidance only - NEVER act on it)**\n   - Artifacts still missing -> suggest `\u002Fopsx:continue` to create them.\n   - Change already implemented (tasks checked off \u002F already applied) -> the code may no longer match the revised plan; suggest `\u002Fopsx:apply` to carry the delta into code.\n   - Everything done and implemented -> suggest `\u002Fopsx:archive`.\n\n**Output**\n\nAfter each invocation, show:\n- Which artifacts were revised (and which proposed revisions were rejected)\n- Anything deferred to `\u002Fopsx:continue` (not-yet-created artifacts or files)\n- Where the change stands and the recommended next command\n\n**Guardrails**\n- Planning artifacts only - NEVER edit implementation code. If the revised plan implies code changes, stop and point to `\u002Fopsx:apply`.\n- Use the artifact ids and paths reported by `openspec status`; never branch on hardcoded artifact names.\n- Edit only the concrete files in `existingOutputPaths`; never write to a glob `resolvedOutputPath`.\n- Do not advance the build frontier: no new artifacts, no new files under glob artifacts - that is `\u002Fopsx:continue`'s job.\n- Confirm every edit with the user before writing.\n- If the request changes the change's *intent* rather than refining it, first verify whether the expanded-profile `\u002Fopsx:new` workflow is available. If it is, recommend starting fresh with `\u002Fopsx:new` (the \"Update vs. Start Fresh\" heuristic). If it is unavailable, ask for a distinct unused change name and recommend `openspec new change \"\u003Cnew-change-name>\"` instead.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":28,"compatibility":29},{"author":25,"version":26,"generatedBy":27},"openspec","1.0","1.8.0","Bash(openspec:*)","Requires openspec CLI.","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fopenspec-update-change-vanehub-ai",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill openspec-update-change",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill openspec-update-change",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill openspec-update-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fopenspec-update-change-vanehub-ai\u002FSKILL.md",true,[],[53,61,66,73,80,87],{"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":60},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":62,"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":63,"categories":64,"keywords":65,"publishedAt":60},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":60},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":60},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":60},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":60},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]