[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75698PYAJ9XFC0TXJXWP545":3,"skill-same:01M75698PYAJ9XFC0TXJXWP545":53},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M75698PYAJ9XFC0TXJXWP545","openspec-new-change",null,"Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.","fushenguang\u002Fagentdock","fushenguang","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22734981?v=4","01M7567WS1R6V55QGFK7WWMEP2","fujia","01M7567WT0P6QXGHRG73B9RN0B",1,"MIT","https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002F.cline\u002Fskills\u002Fopenspec-new-change\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: openspec-new-change\ndescription: Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.4.1\"\n---\n\nStart a new change using the experimental artifact-driven approach.\n\n**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.\n\n**Steps**\n\n1. **If no clear input provided, ask what they want to build**\n\n   Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:\n   > \"What change do you want to work on? Describe what you want to build or fix.\"\n\n   From their description, derive a kebab-case name (e.g., \"add user authentication\" → `add-user-auth`).\n\n   **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.\n\n2. **Determine the workflow schema**\n\n   Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.\n\n   **Use a different schema only if the user mentions:**\n   - A specific schema name → use `--schema \u003Cname>`\n   - \"show workflows\" or \"what workflows\" → run `openspec schemas --json` and let them choose\n\n   **Otherwise**: Omit `--schema` to use the default.\n\n3. **Create the change directory**\n   ```bash\n   openspec new change \"\u003Cname>\"\n   ```\n   Add `--schema \u003Cname>` only if the user requested a specific workflow.\n   This creates a scaffolded change in the planning home resolved by the CLI.\n\n4. **Show the artifact status**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Use the returned `planningHome`, `changeRoot`, `artifactPaths`, and `nextSteps` instead of assuming repo-local paths.\n\n5. **Get instructions for the first artifact**\n   The first artifact depends on the schema (e.g., `proposal` for spec-driven).\n   Check the status output to find the first artifact with status \"ready\".\n   ```bash\n   openspec instructions \u003Cfirst-artifact-id> --change \"\u003Cname>\"\n   ```\n   This outputs the template and context for creating the first artifact.\n\n6. **STOP and wait for user direction**\n\n**Output**\n\nAfter completing the steps, summarize:\n- Change name and location\n- Schema\u002Fworkflow being used and its artifact sequence\n- Current status (0\u002FN artifacts complete)\n- The template for the first artifact\n- Prompt: \"Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue.\"\n\n**Guardrails**\n- Do NOT create any artifacts yet - just show the instructions\n- Do NOT advance beyond showing the first artifact template\n- If the name is invalid (not kebab-case), ask for a valid name\n- If a change with that name already exists, suggest continuing that change instead\n- Pass --schema if using a non-default workflow\n","Start a new change using the experimental artifact-driven approach.\n\n**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.\n\n**Steps**\n\n1. **If no clear input provided, ask what they want to build**\n\n   Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:\n   > \"What change do you want to work on? Describe what you want to build or fix.\"\n\n   From their description, derive a kebab-case name (e.g., \"add user authentication\" → `add-user-auth`).\n\n   **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.\n\n2. **Determine the workflow schema**\n\n   Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.\n\n   **Use a different schema only if the user mentions:**\n   - A specific schema name → use `--schema \u003Cname>`\n   - \"show workflows\" or \"what workflows\" → run `openspec schemas --json` and let them choose\n\n   **Otherwise**: Omit `--schema` to use the default.\n\n3. **Create the change directory**\n   ```bash\n   openspec new change \"\u003Cname>\"\n   ```\n   Add `--schema \u003Cname>` only if the user requested a specific workflow.\n   This creates a scaffolded change in the planning home resolved by the CLI.\n\n4. **Show the artifact status**\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n   Use the returned `planningHome`, `changeRoot`, `artifactPaths`, and `nextSteps` instead of assuming repo-local paths.\n\n5. **Get instructions for the first artifact**\n   The first artifact depends on the schema (e.g., `proposal` for spec-driven).\n   Check the status output to find the first artifact with status \"ready\".\n   ```bash\n   openspec instructions \u003Cfirst-artifact-id> --change \"\u003Cname>\"\n   ```\n   This outputs the template and context for creating the first artifact.\n\n6. **STOP and wait for user direction**\n\n**Output**\n\nAfter completing the steps, summarize:\n- Change name and location\n- Schema\u002Fworkflow being used and its artifact sequence\n- Current status (0\u002FN artifacts complete)\n- The template for the first artifact\n- Prompt: \"Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue.\"\n\n**Guardrails**\n- Do NOT create any artifacts yet - just show the instructions\n- Do NOT advance beyond showing the first artifact template\n- If the name is invalid (not kebab-case), ask for a valid name\n- If a change with that name already exists, suggest continuing that change instead\n- Pass --schema if using a non-default workflow\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"generatedBy":27},"openspec","1.0","1.4.1","Requires openspec CLI.","main","80dc803c0a3a8acf13523c1c35e9b502b531ae10",".cline\u002Fskills\u002Fopenspec-new-change",0,"https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock","https:\u002F\u002Ffushenguang.github.io\u002Fagentdock\u002Fzh\u002Fdocs\u002F","https:\u002F\u002Fgithub.com\u002Ffushenguang","www.fujia.site"," fujia - Software Engineer","2026-11-08 17:53:55",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add fushenguang\u002Fagentdock --skill openspec-new-change",{"tool":45,"command":46},"bunx","bunx skills add fushenguang\u002Fagentdock --skill openspec-new-change",{"tool":48,"command":49},"pnpm","pnpm dlx skills add fushenguang\u002Fagentdock --skill openspec-new-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002F.cline\u002Fskills\u002Fopenspec-new-change\u002FSKILL.md",true,[],[54,62,69,76,83,90],{"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":58,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M756E8ZRR95W3ZN8JFG4517A","impeccable","Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002Ftemplates\u002Fweb-tanstackstart-kids\u002F.github\u002Fskills\u002Fimpeccable\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M756DE7J6HY4V650Q7QPVXJM","example-skill","A minimal, valid example skill shipped with the skills-registry template so the three CI gates (validation, manifest freshness, public\u002Fprivate boundary) have something real to check from the moment a repo is created — replace or delete this once you add your own skills.","https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills-registry\u002Fskills\u002Fexample-skill\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M756BZ6THAFFDSZQGEC8WG0K","template-testing","Validate template changes by running automated tests (lint, type-check, build, dev server, HTTP endpoints) before merging to main.","https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002F.lingma\u002Fskills\u002Ftemplate-testing\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"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},"01M756BWGXKYTGFKBV8T24HZX4","openspec-verify-change","Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.","https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002F.lingma\u002Fskills\u002Fopenspec-verify-change\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},"01M756BS7EY6VDEZSGZY0XB6B5","openspec-sync-specs","Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.","https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002F.lingma\u002Fskills\u002Fopenspec-sync-specs\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},"01M756BP6700D27F0RG59DFHM8","openspec-onboard","Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.","https:\u002F\u002Fgithub.com\u002Ffushenguang\u002Fagentdock\u002Fblob\u002Fmain\u002F.lingma\u002Fskills\u002Fopenspec-onboard\u002FSKILL.md",[],[]]