[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASSAM7A8V2YAPQR38MRBJP":3,"skill-same:01M7ASSAM7A8V2YAPQR38MRBJP":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":58},"01M7ASSAM7A8V2YAPQR38MRBJP","openspec",null,"Spec-driven development with OpenSpec. Use when the user mentions OpenSpec, OPSX, spec-driven development, SDD, change proposals, delta specs, \u002Fopsx commands, or wants structured planning for features, migrations, refactors, or bug fixes.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenspec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: openspec\ndescription: >\n  Spec-driven development with OpenSpec. Use when the user mentions OpenSpec, OPSX,\n  spec-driven development, SDD, change proposals, delta specs, \u002Fopsx commands,\n  or wants structured planning for features, migrations, refactors, or bug fixes.\nmetadata:\n  category: workflow-automation\n  pattern: pipeline\n  owner: engineering\n  status: active\n  review_cycle_days: 90\n  benchmark_after_model_update: true\n  outputs:\n    - change-proposal\n    - delta-spec\n    - design\n    - task-list\n    - implementation-verification\ncompatibility: Portable Agent Skills core; OpenSpec CLI is optional but preferred when installed.\n---\n\n# OpenSpec\n\nUse OpenSpec as the planning layer when work needs durable requirements, reviewable intent, or a multi-session implementation trail. Keep the repository's normal engineering rules active: start implementation with tests where applicable, work in small steps, and run the project's canonical checks.\n\n## Before You Start\n\n1. Check whether the current repository already has an `openspec\u002F` directory or `docs\u002Fopenspec\u002F`.\n2. Resolve and verify the CLI with the NVM-aware procedure below.\n3. If OpenSpec is missing and the user asked to adopt it, initialize it with the shared installer after confirming the target repository.\n4. If OpenSpec is present, read the relevant `openspec\u002Fspecs\u002F*\u002Fspec.md` and active `openspec\u002Fchanges\u002F\u003Cchange>\u002F` artifacts before proposing edits. If `openspec\u002F` is a symlink to `docs\u002Fopenspec\u002F`, keep using `openspec\u002F...` paths for CLI compatibility while recognizing that the physical files live under `docs\u002Fopenspec\u002F`.\n5. Treat OpenSpec artifacts as source files: update them with the same care as code, keep language precise, and include them in validation.\n\n## CLI Runtime Resolution\n\nNon-interactive clients such as Codex App may not inherit the shell that loads\nNVM. On this machine OpenSpec is managed by the NVM default Node installation;\nthe exact Node version is intentionally not hard-coded. Before reporting a\nmissing CLI, use this resolution sequence:\n\n```bash\nif ! openspec --version >\u002Fdev\u002Fnull 2>&1; then\n    if [ -s \"$HOME\u002F.nvm\u002Fnvm.sh\" ]; then\n        . \"$HOME\u002F.nvm\u002Fnvm.sh\"\n    fi\nfi\nopenspec --version\n```\n\nDo not conclude that OpenSpec is unavailable merely because it is absent from\nthe initial `PATH`, or because `~\u002F.agents\u002Fbin\u002Fopenspec` reports\n`env: node: No such file or directory`. Load NVM and retry first. Only treat it\nas missing when the post-NVM `openspec --version` still fails.\n\n## Shared Installer\n\nThis tooling repo exposes a portable installer through the shared `~\u002F.agents` symlink:\n\n```bash\n~\u002F.agents\u002Fskills\u002Fopenspec\u002Fscripts\u002Finstall-openspec\n~\u002F.agents\u002Fskills\u002Fopenspec\u002Fscripts\u002Finstall-openspec \u002Fpath\u002Fto\u002Frepo\n```\n\nThe installer uses this placement policy:\n\n- If the target repository already has `docs\u002F`, create `docs\u002Fopenspec\u002F` and a root `openspec -> docs\u002Fopenspec` symlink so `openspec` CLI commands work from the repo root.\n- If the target repository has `thoughts\u002F` but no `docs\u002F`, create `thoughts\u002Fopenspec\u002F` and a root `openspec -> thoughts\u002Fopenspec` symlink.\n- If the target repository does not have `docs\u002F` or `thoughts\u002F`, create the normal root `openspec\u002F` directory.\n- Do not move an existing real root `openspec\u002F` directory automatically; treat it as an existing installation.\n\n## Default Workflow\n\nUse the core OPSX path for most changes:\n\n1. Explore unclear requirements before creating artifacts.\n2. Propose the change and generate planning artifacts.\n3. Review and refine `proposal.md`, delta specs, `design.md`, and `tasks.md`.\n4. Apply tasks one at a time, checking off completed items in `tasks.md`.\n5. Verify implementation against the proposal, specs, design, and tasks.\n6. Sync and archive the change when the implementation is complete.\n\nIf slash commands are available in the active tool, prefer:\n\n- `\u002Fopsx:explore` for investigation before committing to a change.\n- `\u002Fopsx:propose \u003Cchange>` for the default proposal-to-tasks path.\n- `\u002Fopsx:apply \u003Cchange>` for implementation.\n- `\u002Fopsx:verify \u003Cchange>` when the expanded workflow is enabled.\n- `\u002Fopsx:sync \u003Cchange>` to merge delta specs into canonical specs when needed.\n- `\u002Fopsx:archive \u003Cchange>` to finalize completed work.\n\nIf the tool does not expose slash commands, perform the same workflow directly in files under `openspec\u002Fchanges\u002F\u003Cchange>\u002F`. In docs-first repositories, that path may resolve through the root symlink to `docs\u002Fopenspec\u002Fchanges\u002F\u003Cchange>\u002F`.\n\n## CLI Use\n\nPrefer CLI commands for repository state and validation when available:\n\n```bash\nopenspec list\nopenspec list --specs\nopenspec show \u003Cchange-or-spec>\nopenspec status \u003Cchange>\nopenspec validate --all\n```\n\nUse `--json` for agent-readable output when the command supports it. Do not build long-lived automation on beta workspace commands unless the user explicitly asks for experimental workspace setup.\n\n## Artifact Standards\n\n- Name change folders in kebab-case and avoid generic names like `update` or `wip`.\n- Write requirements with `SHALL` statements and concrete scenarios.\n- Keep scenarios in `GIVEN`, `WHEN`, `THEN`, and optional `AND` form.\n- Keep tasks small enough to implement and verify independently.\n- Update the design when implementation decisions change.\n- Run OpenSpec validation and the repository's canonical validation before claiming completion.\n\n## Brownfield Repositories\n\nOpenSpec works incrementally. Do not try to generate a full specification library upfront unless the user asks for a documentation pass. For mature codebases, create or update specs around the change being made, then let the spec library grow through real work.\n\n## Setup Guidance\n\nWhen initializing OpenSpec, choose the smallest tool scope that matches the user's request:\n\n```bash\n~\u002F.agents\u002Fskills\u002Fopenspec\u002Fscripts\u002Finstall-openspec\nopenspec update\n```\n\nAfter upgrading the CLI, run `openspec update` in initialized repositories so generated tool instructions stay current.\n","# OpenSpec\n\nUse OpenSpec as the planning layer when work needs durable requirements, reviewable intent, or a multi-session implementation trail. Keep the repository's normal engineering rules active: start implementation with tests where applicable, work in small steps, and run the project's canonical checks.\n\n## Before You Start\n\n1. Check whether the current repository already has an `openspec\u002F` directory or `docs\u002Fopenspec\u002F`.\n2. Resolve and verify the CLI with the NVM-aware procedure below.\n3. If OpenSpec is missing and the user asked to adopt it, initialize it with the shared installer after confirming the target repository.\n4. If OpenSpec is present, read the relevant `openspec\u002Fspecs\u002F*\u002Fspec.md` and active `openspec\u002Fchanges\u002F\u003Cchange>\u002F` artifacts before proposing edits. If `openspec\u002F` is a symlink to `docs\u002Fopenspec\u002F`, keep using `openspec\u002F...` paths for CLI compatibility while recognizing that the physical files live under `docs\u002Fopenspec\u002F`.\n5. Treat OpenSpec artifacts as source files: update them with the same care as code, keep language precise, and include them in validation.\n\n## CLI Runtime Resolution\n\nNon-interactive clients such as Codex App may not inherit the shell that loads\nNVM. On this machine OpenSpec is managed by the NVM default Node installation;\nthe exact Node version is intentionally not hard-coded. Before reporting a\nmissing CLI, use this resolution sequence:\n\n```bash\nif ! openspec --version >\u002Fdev\u002Fnull 2>&1; then\n    if [ -s \"$HOME\u002F.nvm\u002Fnvm.sh\" ]; then\n        . \"$HOME\u002F.nvm\u002Fnvm.sh\"\n    fi\nfi\nopenspec --version\n```\n\nDo not conclude that OpenSpec is unavailable merely because it is absent from\nthe initial `PATH`, or because `~\u002F.agents\u002Fbin\u002Fopenspec` reports\n`env: node: No such file or directory`. Load NVM and retry first. Only treat it\nas missing when the post-NVM `openspec --version` still fails.\n\n## Shared Installer\n\nThis tooling repo exposes a portable installer through the shared `~\u002F.agents` symlink:\n\n```bash\n~\u002F.agents\u002Fskills\u002Fopenspec\u002Fscripts\u002Finstall-openspec\n~\u002F.agents\u002Fskills\u002Fopenspec\u002Fscripts\u002Finstall-openspec \u002Fpath\u002Fto\u002Frepo\n```\n\nThe installer uses this placement policy:\n\n- If the target repository already has `docs\u002F`, create `docs\u002Fopenspec\u002F` and a root `openspec -> docs\u002Fopenspec` symlink so `openspec` CLI commands work from the repo root.\n- If the target repository has `thoughts\u002F` but no `docs\u002F`, create `thoughts\u002Fopenspec\u002F` and a root `openspec -> thoughts\u002Fopenspec` symlink.\n- If the target repository does not have `docs\u002F` or `thoughts\u002F`, create the normal root `openspec\u002F` directory.\n- Do not move an existing real root `openspec\u002F` directory automatically; treat it as an existing installation.\n\n## Default Workflow\n\nUse the core OPSX path for most changes:\n\n1. Explore unclear requirements before creating artifacts.\n2. Propose the change and generate planning artifacts.\n3. Review and refine `proposal.md`, delta specs, `design.md`, and `tasks.md`.\n4. Apply tasks one at a time, checking off completed items in `tasks.md`.\n5. Verify implementation against the proposal, specs, design, and tasks.\n6. Sync and archive the change when the implementation is complete.\n\nIf slash commands are available in the active tool, prefer:\n\n- `\u002Fopsx:explore` for investigation before committing to a change.\n- `\u002Fopsx:propose \u003Cchange>` for the default proposal-to-tasks path.\n- `\u002Fopsx:apply \u003Cchange>` for implementation.\n- `\u002Fopsx:verify \u003Cchange>` when the expanded workflow is enabled.\n- `\u002Fopsx:sync \u003Cchange>` to merge delta specs into canonical specs when needed.\n- `\u002Fopsx:archive \u003Cchange>` to finalize completed work.\n\nIf the tool does not expose slash commands, perform the same workflow directly in files under `openspec\u002Fchanges\u002F\u003Cchange>\u002F`. In docs-first repositories, that path may resolve through the root symlink to `docs\u002Fopenspec\u002Fchanges\u002F\u003Cchange>\u002F`.\n\n## CLI Use\n\nPrefer CLI commands for repository state and validation when available:\n\n```bash\nopenspec list\nopenspec list --specs\nopenspec show \u003Cchange-or-spec>\nopenspec status \u003Cchange>\nopenspec validate --all\n```\n\nUse `--json` for agent-readable output when the command supports it. Do not build long-lived automation on beta workspace commands unless the user explicitly asks for experimental workspace setup.\n\n## Artifact Standards\n\n- Name change folders in kebab-case and avoid generic names like `update` or `wip`.\n- Write requirements with `SHALL` statements and concrete scenarios.\n- Keep scenarios in `GIVEN`, `WHEN`, `THEN`, and optional `AND` form.\n- Keep tasks small enough to implement and verify independently.\n- Update the design when implementation decisions change.\n- Run OpenSpec validation and the repository's canonical validation before claiming completion.\n\n## Brownfield Repositories\n\nOpenSpec works incrementally. Do not try to generate a full specification library upfront unless the user asks for a documentation pass. For mature codebases, create or update specs around the change being made, then let the spec library grow through real work.\n\n## Setup Guidance\n\nWhen initializing OpenSpec, choose the smallest tool scope that matches the user's request:\n\n```bash\n~\u002F.agents\u002Fskills\u002Fopenspec\u002Fscripts\u002Finstall-openspec\nopenspec update\n```\n\nAfter upgrading the CLI, run `openspec update` in initialized repositories so generated tool instructions stay current.\n",{"name":5,"metadata":23,"description":36,"compatibility":37},{"owner":24,"status":25,"outputs":26,"pattern":32,"category":33,"review_cycle_days":34,"benchmark_after_model_update":35},"engineering","active",[27,28,29,30,31],"change-proposal","delta-spec","design","task-list","implementation-verification","pipeline","workflow-automation",90,true,"Spec-driven development with OpenSpec. Use when the user mentions OpenSpec, OPSX, spec-driven development, SDD, change proposals, delta specs, \u002Fopsx commands, or wants structured planning for features, migrations, refactors, or bug fixes.\n","Portable Agent Skills core; OpenSpec CLI is optional but preferred when installed.","main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fopenspec",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":35},[48,51,54],{"tool":49,"command":50},"npx","npx skills add saski\u002Farnesto --skill openspec",{"tool":52,"command":53},"bunx","bunx skills add saski\u002Farnesto --skill openspec",{"tool":55,"command":56},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill openspec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenspec\u002FSKILL.md",[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Finstall-openspec","SCRIPT","脚本",1574,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopenspec\u002Fscripts\u002Finstall-openspec",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]