[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AAR31BDYXGEMAXB6CE6KXG":3,"skill-same:01M7AAR31BDYXGEMAXB6CE6KXG":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},"01M7AAR31BDYXGEMAXB6CE6KXG","openspec-propose",null,"Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.","Sdju\u002Fbapm","Sdju","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11253427?v=4","01M7AAQKDD4TGWMN4VD9ME1FFG","Denis Chernov","01M7AAQKEF1YGP98ZDRDS3EHTD",7,"MIT","https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002F.apm\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: openspec-propose\ndescription: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.\nallowed-tools: Bash(openspec:*)\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.7.0\"\n---\n\nPropose a new change - create the change and generate all artifacts in one step.\n\nI'll create a change with the artifacts your schema defines. With the default spec-driven schema that is:\n\n- proposal.md (what & why)\n- `specs\u002F\u003Ccapability>\u002Fspec.md` (what the system must do - a delta, not the main spec)\n- design.md (how)\n- tasks.md (implementation steps)\n\nWhen ready to implement, run \u002Fopsx-apply\n\n---\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`). 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**: 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   Ask the user (open-ended, no preset options):\n\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. **Create the change directory**\n\n   ```bash\n   openspec new change \"\u003Cname>\"\n   ```\n\n   This creates a scaffolded change in the planning home resolved by the CLI with `.openspec.yaml`.\n\n3. **Get the artifact build order**\n\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n\n   Parse the JSON to get:\n   - `applyRequires`: array of artifact IDs needed before implementation (e.g., `[\"tasks\"]`)\n   - `artifacts`: list of all artifacts, each with its `status` and its `requires` edges (the artifact IDs it directly depends on)\n   - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.\n\n4. **Create every artifact in the required set**\n\n   Use a todo list to track progress through the artifacts.\n\n   Loop through artifacts in dependency order (artifacts with no pending dependencies first):\n\n   a. **For each artifact that is `ready` (dependencies satisfied)**:\n   - Get instructions:\n     ```bash\n     openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json\n     ```\n   - The instructions JSON includes:\n     - `context`: Project background (constraints for you - do NOT include in output)\n     - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)\n     - `template`: The structure to use for your output file\n     - `instruction`: Schema-specific guidance for this artifact type\n     - `skipped`\u002F`warning`: present when the change declares skip_specs and this artifact must NOT be created - stop and pick another artifact\n     - `resolvedOutputPath`: Resolved path or pattern to write the artifact\n     - `dependencies`: Completed artifacts to read for context\n   - Read any completed dependency files for context - always re-read them from disk, even if you saw them earlier in the conversation (the user may have edited them)\n   - If the `instruction` field delegates creation to a specific skill or command, invoke it to produce the artifact instead of writing the file yourself, then verify the artifact file exists at `resolvedOutputPath`\n   - Otherwise create the artifact file using `template` as the structure and write it to `resolvedOutputPath`. If `resolvedOutputPath` is a glob, follow `instruction` to choose the concrete file path\n   - Apply `context` and `rules` as constraints - but do NOT copy them into the file\n   - Show brief progress: \"Created \u003Cartifact-id>\"\n\n   b. **Continue until every artifact in the required set exists (not just `apply.requires`)**\n   - After creating each artifact, re-run `openspec status --change \"\u003Cname>\" --json`\n   - The required set is `applyRequires` plus every artifact reachable from those by following the `requires` edges in `status --json` - walk them transitively (spec-driven closes over proposal, specs, design, tasks). Leave artifacts outside that set alone\n   - `status` is file-existence only, so an `applyRequires` artifact reading `done` does NOT mean its dependencies exist - writing `tasks.md` early marks `tasks` done while `specs` was never written. Use each artifact's `requires` edges, not its `status`, to build the required set: a `done` artifact still lists what it depends on\n   - An artifact already reading `status: \"skipped\"` is satisfied: the change declares `skip_specs` in `.openspec.yaml`, so its files must NOT exist. Never try to create one\n   - Create every artifact in the required set that is missing, then re-check - creating one can unblock others\n   - Skip one only when `status` already reports it `skipped`, or when its own `instruction` says it is conditional: run `openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json` and skip only if its `instruction` field marks it optional (e.g. \"create only if...\"). Spec-driven's `design.md` qualifies; `specs` qualifies only via the `skipped` status above, never by your own judgment. Tell the user, and do not reconsider it\n   - Dependencies are enablers, not gates: if a required artifact is still `blocked` only because you skipped a conditional dependency, write it anyway\n   - Stop when every artifact in the required set is `done`, `skipped`, or was deliberately skipped\n\n   c. **If an artifact requires user input** (unclear context):\n   - Ask the user to clarify\n   - Then continue with creation\n\n5. **Show final status**\n   ```bash\n   openspec status --change \"\u003Cname>\"\n   ```\n\n**Output**\n\nAfter completing all artifacts, summarize:\n\n- Change name and location\n- List of artifacts created with brief descriptions, plus any conditional artifact you skipped and why\n- What's ready: \"All artifacts needed for implementation are ready.\"\n- Prompt: \"Run `\u002Fopsx-apply` or ask me to implement to start working on the tasks.\"\n\n**Artifact Creation Guidelines**\n\n- Follow the `instruction` field from `openspec instructions` for each artifact type - it is the authoritative guidance, even for familiar artifact names\n- If the `instruction` field directs you to use a specific skill or command to create the artifact, invoke it instead of writing the artifact directly\n- The schema defines what each artifact should contain - follow it\n- Read dependency artifacts for context before creating new ones\n- Use `template` as the structure for your output file - fill in its sections\n- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file\n  - Do NOT copy `\u003Ccontext>`, `\u003Crules>`, `\u003Cproject_context>` blocks into the artifact\n  - These guide what you write, but should never appear in the output\n\n**Guardrails**\n\n- Create every artifact the apply phase transitively depends on, not just the ids listed in `apply.requires`\n- Always read dependency artifacts before creating a new one - re-read from disk, not from conversation memory (files may have changed since you last saw them)\n- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum\n- If a change with that name already exists, ask if user wants to continue it or create a new one\n- Verify each artifact file exists after writing before proceeding to next\n","Propose a new change - create the change and generate all artifacts in one step.\n\nI'll create a change with the artifacts your schema defines. With the default spec-driven schema that is:\n\n- proposal.md (what & why)\n- `specs\u002F\u003Ccapability>\u002Fspec.md` (what the system must do - a delta, not the main spec)\n- design.md (how)\n- tasks.md (implementation steps)\n\nWhen ready to implement, run \u002Fopsx-apply\n\n---\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`). 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**: 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   Ask the user (open-ended, no preset options):\n\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. **Create the change directory**\n\n   ```bash\n   openspec new change \"\u003Cname>\"\n   ```\n\n   This creates a scaffolded change in the planning home resolved by the CLI with `.openspec.yaml`.\n\n3. **Get the artifact build order**\n\n   ```bash\n   openspec status --change \"\u003Cname>\" --json\n   ```\n\n   Parse the JSON to get:\n   - `applyRequires`: array of artifact IDs needed before implementation (e.g., `[\"tasks\"]`)\n   - `artifacts`: list of all artifacts, each with its `status` and its `requires` edges (the artifact IDs it directly depends on)\n   - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.\n\n4. **Create every artifact in the required set**\n\n   Use a todo list to track progress through the artifacts.\n\n   Loop through artifacts in dependency order (artifacts with no pending dependencies first):\n\n   a. **For each artifact that is `ready` (dependencies satisfied)**:\n   - Get instructions:\n     ```bash\n     openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json\n     ```\n   - The instructions JSON includes:\n     - `context`: Project background (constraints for you - do NOT include in output)\n     - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)\n     - `template`: The structure to use for your output file\n     - `instruction`: Schema-specific guidance for this artifact type\n     - `skipped`\u002F`warning`: present when the change declares skip_specs and this artifact must NOT be created - stop and pick another artifact\n     - `resolvedOutputPath`: Resolved path or pattern to write the artifact\n     - `dependencies`: Completed artifacts to read for context\n   - Read any completed dependency files for context - always re-read them from disk, even if you saw them earlier in the conversation (the user may have edited them)\n   - If the `instruction` field delegates creation to a specific skill or command, invoke it to produce the artifact instead of writing the file yourself, then verify the artifact file exists at `resolvedOutputPath`\n   - Otherwise create the artifact file using `template` as the structure and write it to `resolvedOutputPath`. If `resolvedOutputPath` is a glob, follow `instruction` to choose the concrete file path\n   - Apply `context` and `rules` as constraints - but do NOT copy them into the file\n   - Show brief progress: \"Created \u003Cartifact-id>\"\n\n   b. **Continue until every artifact in the required set exists (not just `apply.requires`)**\n   - After creating each artifact, re-run `openspec status --change \"\u003Cname>\" --json`\n   - The required set is `applyRequires` plus every artifact reachable from those by following the `requires` edges in `status --json` - walk them transitively (spec-driven closes over proposal, specs, design, tasks). Leave artifacts outside that set alone\n   - `status` is file-existence only, so an `applyRequires` artifact reading `done` does NOT mean its dependencies exist - writing `tasks.md` early marks `tasks` done while `specs` was never written. Use each artifact's `requires` edges, not its `status`, to build the required set: a `done` artifact still lists what it depends on\n   - An artifact already reading `status: \"skipped\"` is satisfied: the change declares `skip_specs` in `.openspec.yaml`, so its files must NOT exist. Never try to create one\n   - Create every artifact in the required set that is missing, then re-check - creating one can unblock others\n   - Skip one only when `status` already reports it `skipped`, or when its own `instruction` says it is conditional: run `openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json` and skip only if its `instruction` field marks it optional (e.g. \"create only if...\"). Spec-driven's `design.md` qualifies; `specs` qualifies only via the `skipped` status above, never by your own judgment. Tell the user, and do not reconsider it\n   - Dependencies are enablers, not gates: if a required artifact is still `blocked` only because you skipped a conditional dependency, write it anyway\n   - Stop when every artifact in the required set is `done`, `skipped`, or was deliberately skipped\n\n   c. **If an artifact requires user input** (unclear context):\n   - Ask the user to clarify\n   - Then continue with creation\n\n5. **Show final status**\n   ```bash\n   openspec status --change \"\u003Cname>\"\n   ```\n\n**Output**\n\nAfter completing all artifacts, summarize:\n\n- Change name and location\n- List of artifacts created with brief descriptions, plus any conditional artifact you skipped and why\n- What's ready: \"All artifacts needed for implementation are ready.\"\n- Prompt: \"Run `\u002Fopsx-apply` or ask me to implement to start working on the tasks.\"\n\n**Artifact Creation Guidelines**\n\n- Follow the `instruction` field from `openspec instructions` for each artifact type - it is the authoritative guidance, even for familiar artifact names\n- If the `instruction` field directs you to use a specific skill or command to create the artifact, invoke it instead of writing the artifact directly\n- The schema defines what each artifact should contain - follow it\n- Read dependency artifacts for context before creating new ones\n- Use `template` as the structure for your output file - fill in its sections\n- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file\n  - Do NOT copy `\u003Ccontext>`, `\u003Crules>`, `\u003Cproject_context>` blocks into the artifact\n  - These guide what you write, but should never appear in the output\n\n**Guardrails**\n\n- Create every artifact the apply phase transitively depends on, not just the ids listed in `apply.requires`\n- Always read dependency artifacts before creating a new one - re-read from disk, not from conversation memory (files may have changed since you last saw them)\n- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum\n- If a change with that name already exists, ask if user wants to continue it or create a new one\n- Verify each artifact file exists after writing before proceeding to next\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":28,"compatibility":29},{"author":25,"version":26,"generatedBy":27},"openspec","1.0","1.7.0","Bash(openspec:*)","Requires openspec CLI.","master","56d93e1453785271050d58b4c9ea9b4f492c7112",".apm\u002Fskills\u002Fopenspec-propose",1,"https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm","https:\u002F\u002Fgithub.com\u002FSdju","Vue evangelist","2026-11-13 07:24:45",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Sdju\u002Fbapm --skill openspec-propose",{"tool":44,"command":45},"bunx","bunx skills add Sdju\u002Fbapm --skill openspec-propose",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Sdju\u002Fbapm --skill openspec-propose","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002F.apm\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",true,[],[53,59,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7AARJS3QZV05SCRMXDY8P53","fixture-skill","https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fagent-plugins\u002Fv1-portable\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"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":19},"01M7AAREWYRERZ3234529S99BJ","pnpm-dependencies","Manage npm\u002Fpnpm dependencies via CLI and pnpm catalogs only—never hand-edit manifests or invent versions. Use when adding, updating, removing, or pinning packages; editing package.json or pnpm-workspace.yaml dependencies; or when the user mentions pnpm, catalog, install, or deps.","https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002F.apm\u002Fskills\u002Fpnpm-dependencies\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":19},"01M7AARBDMFV690C0HDT4FTY2X","orchestrate","Оркестратор реализации только через субагентов orch-*: OpenSpec plan, acceptance RED, apply GREEN, accept, promote, merge+ship (ветка\u002FPR); self-commit внутри фазы. Использовать при \u002Forchestrate, «оркестратор», «через субагентов».","https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002F.apm\u002Fskills\u002Forchestrate\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":19},"01M7AAR846375JEW25MM1H8W0A","openspec-update-change","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.","https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002F.apm\u002Fskills\u002Fopenspec-update-change\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":19},"01M7AAR5QYCVAA8DB789AD1X79","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\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002F.apm\u002Fskills\u002Fopenspec-sync-specs\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":19},"01M7AAQZHT9QBEJC4K3XXBCTS1","openspec-explore","Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.","https:\u002F\u002Fgithub.com\u002FSdju\u002Fbapm\u002Fblob\u002Fmaster\u002F.apm\u002Fskills\u002Fopenspec-explore\u002FSKILL.md",[],[]]