[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C32DWWF3ZHEWWEYC3TSRW":3,"skill-same:01M75C32DWWF3ZHEWWEYC3TSRW":49},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M75C32DWWF3ZHEWWEYC3TSRW","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.","cp-yu\u002Federa","cp-yu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68734436?v=4","01M75C1ERG2CGRZWJW3N60H5MM","01M75C1ESMHKGRE9NMZDS6Q8XW",2,"MIT","https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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.\"\nlicense: \"MIT\"\ncompatibility: \"Requires openspec CLI.\"\nmetadata:\n  author: \"openspec\"\n  version: \"1.0\"\n  generatedBy: \"1.4.1-cpyu.1\"\n---\n\nPropose a new change and generate all artifacts needed for implementation.\n\n## Flow\n\n1. Input must identify a kebab-case change name or enough description to derive one. If unclear, ask what to build or fix.\n2. Apply smart routing before creating files: inspect the current conversation for an explore-generated `Design Summary`; if no summary exists, respect `propose.smartRouting: false` and `propose.requireExplore: false`, otherwise score the user's input across 5 dimensions. Detect multi-subsystem scope. Outcomes include: \"Design Summary found: proceed and show that Design Summary is being used\", \"Input is sufficiently detailed. Skipping explore; generating artifacts directly.\", and \"This request spans multiple independent subsystems. Consider running `$openspec-explore` to decompose it first.\". Show input length, detail score, multi-subsystem result, and final decision.\n3. Run `openspec new change \"\u003Cname>\"`, then `openspec status --change \"\u003Cname>\" --json` to read `applyRequires`, artifact order, dependencies, and schema.\n4. Load shared OPSX context before artifact generation.\nBefore reading other context files, check whether `openspec\u002Fproject.opsx.yaml` exists.\n- If it exists, read it first for domains → capabilities structure\n- Read the `project:` block for project intent and scope\n- Treat it as navigation context, not as a replacement for change artifacts\n5. Before specs, run `openspec list --specs --json`; compare proposed capabilities to each spec's `capabilities` string array. Specs without frontmatter return `capabilities: []`. Reuse or modify existing coverage instead of duplicating specs.\n6. Use CLI-backed OPSX navigation after shared context.\nAfter reading shared `project.opsx.yaml` context, use OpenSpec CLI query surfaces for node details.\n- Run `openspec list --specs --json` to get specs and their `capabilities` string arrays; specs without frontmatter return `capabilities: []`.\n- For known or affected OPSX node IDs, run `openspec opsx query \u003Cnode-id...> --json` to get node details, relations and code-map refs in one batch; add `--depth 2` when broader related context is needed.\n- Treat CLI output as navigation context, not as a replacement for change artifacts.\n7. For each ready artifact, run `openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json`; read `configProjection` (especially `configProjection.normalized.proseLanguage` and `configProjection.prompt.fragments`), dependencies, `template`, `instruction`, and `outputPath`; follow the template exactly and do not copy `context`, `rules`, or `configProjection` into artifact files. When creating `specs`, apply the returned `Spec content boundary`: route non-behavior content to design\u002Ftasks\u002Fproposal\u002Fopsx-delta instead of requirements.\n8. Continue until all `applyRequires` artifacts are `done`. If an artifact is unclear, ask one focused question and continue.\n9. After spec-driven specs are complete, generate `opsx-delta.yaml` from `openspec instructions opsx-delta --change \"\u003Cname>\" --json`; use `schema_version: 1`, `ADDED:`, `MODIFIED:`, and `REMOVED:` YAML keys and query existing nodes when needed.\n10. Run warning-only post-propose validation: This validation is warning-only. Do NOT turn `$openspec-propose` into a blocking gate. Prefer `openspec validate \"\u003Cname>\" --type change --json`; align with `Validator.validateChangeDeltaSpecs()`, SHALL\u002FMUST requirement text, required `#### Scenario:` blocks, `Validator.validateOpsxDelta()`, `applyOpsxDelta()`, referential integrity, and code-map integrity. Do NOT run `openspec sync`; report when validation skips this check. For structure checks, read `openspec instructions proposal --change \"\u003Cname>\" --json`, `openspec instructions design --change \"\u003Cname>\" --json`, and `openspec instructions tasks --change \"\u003Cname>\" --json`; use `validateTaskStructure`, support Actions and coarse `### Task N:` with Goal, Files, Requirements, Checks, Covers:, Verifies:, change-local `Verifies:` spec paths, Requirement\u002FScenario references, Command:, Evidence:, and Expect:. Do NOT invent semantic lint rules beyond the current templates. Do NOT judge whether a check is semantically sufficient. If warnings appear, do exactly one repair pass, re-check once, and summarize remaining warnings.\n11. Finish with `openspec status --change \"\u003Cname>\"` and report artifacts created plus readiness for `$openspec-apply-change`.\n\n## Artifact Contract\n\n**Document Language Contract**:\n- Treat `openspec\u002Fconfig.yaml` as the compact source of truth, but consume its compiled prompt projection rather than reinterpreting raw keys ad hoc\n- If the compiled projection includes `proseLanguage`, apply it to natural-language prose you write or revise in the artifact body\n- Natural-language prose includes task titles, check names, Requirement titles, Scenario titles, bullet descriptions, Expect\u002FEvidence descriptions, rationale, goals, risks, and summaries\n- Follow the existing template structure exactly; do not invent a different layout because the prose language changes\n- Keep template headings, normative keywords, BDD keywords, IDs, schema keys, relation types, file paths, commands, and code identifiers in their canonical form\n- Preserve exact existing Requirement titles required for MODIFIED matching\n- English project terminology may remain embedded in prose, but ordinary English sentences and titles still follow `proseLanguage`\n- If no `proseLanguage` projection is present, keep the default writing behavior for prose\n\nKeep generated tasks coarse: `### Task N:`, `Goal`, `Files`, `Requirements`, and nested Checks. Keep each task to at most 5 Requirements. Preserve template structure, canonical headings, IDs, schema keys, paths, commands, BDD keywords, and code identifiers.\n","Propose a new change and generate all artifacts needed for implementation.\n\n## Flow\n\n1. Input must identify a kebab-case change name or enough description to derive one. If unclear, ask what to build or fix.\n2. Apply smart routing before creating files: inspect the current conversation for an explore-generated `Design Summary`; if no summary exists, respect `propose.smartRouting: false` and `propose.requireExplore: false`, otherwise score the user's input across 5 dimensions. Detect multi-subsystem scope. Outcomes include: \"Design Summary found: proceed and show that Design Summary is being used\", \"Input is sufficiently detailed. Skipping explore; generating artifacts directly.\", and \"This request spans multiple independent subsystems. Consider running `$openspec-explore` to decompose it first.\". Show input length, detail score, multi-subsystem result, and final decision.\n3. Run `openspec new change \"\u003Cname>\"`, then `openspec status --change \"\u003Cname>\" --json` to read `applyRequires`, artifact order, dependencies, and schema.\n4. Load shared OPSX context before artifact generation.\nBefore reading other context files, check whether `openspec\u002Fproject.opsx.yaml` exists.\n- If it exists, read it first for domains → capabilities structure\n- Read the `project:` block for project intent and scope\n- Treat it as navigation context, not as a replacement for change artifacts\n5. Before specs, run `openspec list --specs --json`; compare proposed capabilities to each spec's `capabilities` string array. Specs without frontmatter return `capabilities: []`. Reuse or modify existing coverage instead of duplicating specs.\n6. Use CLI-backed OPSX navigation after shared context.\nAfter reading shared `project.opsx.yaml` context, use OpenSpec CLI query surfaces for node details.\n- Run `openspec list --specs --json` to get specs and their `capabilities` string arrays; specs without frontmatter return `capabilities: []`.\n- For known or affected OPSX node IDs, run `openspec opsx query \u003Cnode-id...> --json` to get node details, relations and code-map refs in one batch; add `--depth 2` when broader related context is needed.\n- Treat CLI output as navigation context, not as a replacement for change artifacts.\n7. For each ready artifact, run `openspec instructions \u003Cartifact-id> --change \"\u003Cname>\" --json`; read `configProjection` (especially `configProjection.normalized.proseLanguage` and `configProjection.prompt.fragments`), dependencies, `template`, `instruction`, and `outputPath`; follow the template exactly and do not copy `context`, `rules`, or `configProjection` into artifact files. When creating `specs`, apply the returned `Spec content boundary`: route non-behavior content to design\u002Ftasks\u002Fproposal\u002Fopsx-delta instead of requirements.\n8. Continue until all `applyRequires` artifacts are `done`. If an artifact is unclear, ask one focused question and continue.\n9. After spec-driven specs are complete, generate `opsx-delta.yaml` from `openspec instructions opsx-delta --change \"\u003Cname>\" --json`; use `schema_version: 1`, `ADDED:`, `MODIFIED:`, and `REMOVED:` YAML keys and query existing nodes when needed.\n10. Run warning-only post-propose validation: This validation is warning-only. Do NOT turn `$openspec-propose` into a blocking gate. Prefer `openspec validate \"\u003Cname>\" --type change --json`; align with `Validator.validateChangeDeltaSpecs()`, SHALL\u002FMUST requirement text, required `#### Scenario:` blocks, `Validator.validateOpsxDelta()`, `applyOpsxDelta()`, referential integrity, and code-map integrity. Do NOT run `openspec sync`; report when validation skips this check. For structure checks, read `openspec instructions proposal --change \"\u003Cname>\" --json`, `openspec instructions design --change \"\u003Cname>\" --json`, and `openspec instructions tasks --change \"\u003Cname>\" --json`; use `validateTaskStructure`, support Actions and coarse `### Task N:` with Goal, Files, Requirements, Checks, Covers:, Verifies:, change-local `Verifies:` spec paths, Requirement\u002FScenario references, Command:, Evidence:, and Expect:. Do NOT invent semantic lint rules beyond the current templates. Do NOT judge whether a check is semantically sufficient. If warnings appear, do exactly one repair pass, re-check once, and summarize remaining warnings.\n11. Finish with `openspec status --change \"\u003Cname>\"` and report artifacts created plus readiness for `$openspec-apply-change`.\n\n## Artifact Contract\n\n**Document Language Contract**:\n- Treat `openspec\u002Fconfig.yaml` as the compact source of truth, but consume its compiled prompt projection rather than reinterpreting raw keys ad hoc\n- If the compiled projection includes `proseLanguage`, apply it to natural-language prose you write or revise in the artifact body\n- Natural-language prose includes task titles, check names, Requirement titles, Scenario titles, bullet descriptions, Expect\u002FEvidence descriptions, rationale, goals, risks, and summaries\n- Follow the existing template structure exactly; do not invent a different layout because the prose language changes\n- Keep template headings, normative keywords, BDD keywords, IDs, schema keys, relation types, file paths, commands, and code identifiers in their canonical form\n- Preserve exact existing Requirement titles required for MODIFIED matching\n- English project terminology may remain embedded in prose, but ordinary English sentences and titles still follow `proseLanguage`\n- If no `proseLanguage` projection is present, keep the default writing behavior for prose\n\nKeep generated tasks coarse: `### Task N:`, `Goal`, `Files`, `Requirements`, and nested Checks. Keep each task to at most 5 Requirements. Preserve template structure, canonical headings, IDs, schema keys, paths, commands, BDD keywords, and code identifiers.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"generatedBy":26},"openspec","1.0","1.4.1-cpyu.1","Requires openspec CLI.","master","c18be1fecd2d4509d809d31a9b40c8631b5a9abe",".codex\u002Fskills\u002Fopenspec-propose",0,"https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa","https:\u002F\u002Fgithub.com\u002Fcp-yu","2026-06-23 11:25:19",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add cp-yu\u002Federa --skill openspec-propose",{"tool":41,"command":42},"bunx","bunx skills add cp-yu\u002Federa --skill openspec-propose",{"tool":44,"command":45},"pnpm","pnpm dlx skills add cp-yu\u002Federa --skill openspec-propose","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.codex\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",true,[],[50,57,64,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M75C44N0S92N0JZWMS1DJXM3","openspec-snack","Quick code-first sync: generate or update proposal + specs + simplified design from git diff when the code is already written. Use after iterative coding to back-fill specs and OPSX delta without redoing propose→apply. Does not generate tasks.md.","https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.pi\u002Fskills\u002Fopenspec-snack\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M75C40VZPPCXCW80WEG7XXZX","openspec-reviewer","Internal clean-context Phase 1 verification reviewer. Judges implementation completeness, correctness, coherence, and cleanliness by reading files from changeName, changeDir, and projectRoot. Never accesses conversation history.","https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.pi\u002Fskills\u002Fopenspec-reviewer\u002FSKILL.md",[],[],{"skillNo":65,"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":66,"categories":67,"keywords":68,"publishedAt":18},"01M75C3WQ5C1BRECWPWEHYV3NR","https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.pi\u002Fskills\u002Fopenspec-propose\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M75C3T76A0MM8XVGQ6FDT77Q","openspec-optimizer","Internal clean-context Phase 2 optimization proposer. Analyzes implementation files and outputs behavior-preserving Search\u002FReplace blocks. Never modifies files directly. Reads failedDirections to avoid repeating broken strategies.","https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.pi\u002Fskills\u002Fopenspec-optimizer\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M75C3R32971RR1WXKB2XHD50","openspec-impact-sweeper","Generate a lightweight OPSX-grounded JSON impact report for one project concept. Use from explore before scope or proposal readiness claims.","https:\u002F\u002Fgithub.com\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.pi\u002Fskills\u002Fopenspec-impact-sweeper\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M75C3N8CCEV30P468SWY8ZE5","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\u002Fcp-yu\u002Federa\u002Fblob\u002Fmaster\u002F.pi\u002Fskills\u002Fopenspec-explore\u002FSKILL.md",[],[]]