[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C8RKJ90QCVE2HAFYVRXP95":3,"skill-same:01M7C8RKJ90QCVE2HAFYVRXP95":56},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7C8RKJ90QCVE2HAFYVRXP95","write-openspec-docs",null,"Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable). Use when writing or editing pages in the OpenSpec docs tree.","sung1-labs\u002Fsddx","sung1-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F325716214?v=4","01M7C7MDYAWVBFW42T3YCQYG7N","SunG1 Labs","01M7C7MDYZYBYQ5FNSK0XN0YY2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Flibrary\u002Fopenspec\u002Fsddx-openspec-agent-write-openspec-docs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: write-openspec-docs\ndescription: Switches into OpenSpec docs-writing mode; loads the house style guide and drafts or revises pages in its voice (action-first, no preamble, scannable). Use when writing or editing pages in the OpenSpec docs tree.\nargument-hint: page or section\n---\n\n# Write OpenSpec docs\n\nYou are now writing OpenSpec's user docs. Read [writing.md](writing.md); it is the style authority for everything drafted here. The short version, in effect immediately:\n\n- A page is a retrieval surface, not an essay. Structure decides whether the reader finds the answer; prose only decides how it reads. Open every section with the answer, never a running story.\n- Choose the page type before the outline. Guides follow the reader's task; reference mirrors the product's structure and uses exact field, command, and file names as scan anchors. Reference needs complete coverage without compressing several facts into one sentence, cell, or paragraph.\n- Draft the shortest version that answers; expanding a spare page is cheap, cutting a bloated one is a rewrite. Plain words, the fewest of them: an idea that fits in one line takes one line. Depth most readers skip goes behind a link, and the payload (commands, real output, failures and fixes) stays whole.\n- Dumb sentences, smart structure. Write the obvious sentence (actor, verb, object, stating the literal event); never compress extra facts in or take an angle. No hype adjectives, no preamble, no em dashes.\n- One job per slot: one fact per sentence, list intros only announce the list, one reader question or lookup target per section. A related fact gets its own slot, never a ride in someone else's.\n- Ground items in what the reader can verify: path or folder first, concept as the gloss, real output shown honestly.\n- No house template. Inventories open with a list naming every item, then expand each in its own unit after the list, never inline. Sequences take numbered steps (numbers mean order; inventories take bullets). Single ideas and reasoning stay in short prose.\n- Every load-bearing fact sits on a scan anchor: code fence, numbered bold lead-in, `**Term**: fact` bullet, table, file tree. Never only mid-paragraph.\n- Before finishing, run two backstop tests. Retrievability: can each question or exact product name be found by scanning alone? The glance: inspect the rendered page as shapes; does it look finishable, or like work? Check table-heavy changes at desktop and narrow widths. A failure means a slot got written without being earned; fix it now, don't leave it for review.\n\n## Ground rules\n\n- Load the `no-ai-slop` skill before drafting; it owns the generic slop patterns, while [writing.md](writing.md) owns what OpenSpec's docs specifically look and sound like.\n- Read the target page in full before editing it.\n- Real facts only: flags, paths, and output as they exist in source. If a claim can't be checked cheaply, still write it, but name it as unchecked when you show the work; never bridge a gap with a plausible-sounding sentence.\n- A fact lives on one page; everywhere else links to it. The docs tree's README owns the page map and structural invariants; check it before restructuring or adding pages.\n- For reference pages, inventory the contract from source before drafting prose. Follow the reference process in [writing.md](writing.md#reference-pages).\n- When unsure how something should scan or sound, match the exemplars: `docs-lab\u002Fstart\u002Fsetup.md` for section shape and inventories, `docs-lab\u002Fstart\u002Finstallation.md` (Uninstalling) for multi-step tasks.\n\n## When done\n\nShow the user what changed and name any unchecked claims.\n\nIf the user asks for the deep, evidence-first drafting session (run every command, one section per sitting, formal checkpoints), follow [full-process.md](full-process.md).\n","# Write OpenSpec docs\n\nYou are now writing OpenSpec's user docs. Read [writing.md](writing.md); it is the style authority for everything drafted here. The short version, in effect immediately:\n\n- A page is a retrieval surface, not an essay. Structure decides whether the reader finds the answer; prose only decides how it reads. Open every section with the answer, never a running story.\n- Choose the page type before the outline. Guides follow the reader's task; reference mirrors the product's structure and uses exact field, command, and file names as scan anchors. Reference needs complete coverage without compressing several facts into one sentence, cell, or paragraph.\n- Draft the shortest version that answers; expanding a spare page is cheap, cutting a bloated one is a rewrite. Plain words, the fewest of them: an idea that fits in one line takes one line. Depth most readers skip goes behind a link, and the payload (commands, real output, failures and fixes) stays whole.\n- Dumb sentences, smart structure. Write the obvious sentence (actor, verb, object, stating the literal event); never compress extra facts in or take an angle. No hype adjectives, no preamble, no em dashes.\n- One job per slot: one fact per sentence, list intros only announce the list, one reader question or lookup target per section. A related fact gets its own slot, never a ride in someone else's.\n- Ground items in what the reader can verify: path or folder first, concept as the gloss, real output shown honestly.\n- No house template. Inventories open with a list naming every item, then expand each in its own unit after the list, never inline. Sequences take numbered steps (numbers mean order; inventories take bullets). Single ideas and reasoning stay in short prose.\n- Every load-bearing fact sits on a scan anchor: code fence, numbered bold lead-in, `**Term**: fact` bullet, table, file tree. Never only mid-paragraph.\n- Before finishing, run two backstop tests. Retrievability: can each question or exact product name be found by scanning alone? The glance: inspect the rendered page as shapes; does it look finishable, or like work? Check table-heavy changes at desktop and narrow widths. A failure means a slot got written without being earned; fix it now, don't leave it for review.\n\n## Ground rules\n\n- Load the `no-ai-slop` skill before drafting; it owns the generic slop patterns, while [writing.md](writing.md) owns what OpenSpec's docs specifically look and sound like.\n- Read the target page in full before editing it.\n- Real facts only: flags, paths, and output as they exist in source. If a claim can't be checked cheaply, still write it, but name it as unchecked when you show the work; never bridge a gap with a plausible-sounding sentence.\n- A fact lives on one page; everywhere else links to it. The docs tree's README owns the page map and structural invariants; check it before restructuring or adding pages.\n- For reference pages, inventory the contract from source before drafting prose. Follow the reference process in [writing.md](writing.md#reference-pages).\n- When unsure how something should scan or sound, match the exemplars: `docs-lab\u002Fstart\u002Fsetup.md` for section shape and inventories, `docs-lab\u002Fstart\u002Finstallation.md` (Uninstalling) for multi-step tasks.\n\n## When done\n\nShow the user what changed and name any unchecked claims.\n\nIf the user asks for the deep, evidence-first drafting session (run every command, one section per sitting, formal checkpoints), follow [full-process.md](full-process.md).\n",{"name":5,"description":7,"argument-hint":24},"page or section","main","7d9c45c72ac89da53a28423808dabd6dc0be6795","skills\u002Flibrary\u002Fopenspec\u002Fsddx-openspec-agent-write-openspec-docs","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx","https:\u002F\u002Fgithub.com\u002Fsung1-labs","Building open-source tools for AI-assisted software development, spec-driven engineering, and reliable developer workflows.","2026-09-07 02:51:20",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add sung1-labs\u002Fsddx --skill write-openspec-docs",{"tool":38,"command":39},"bunx","bunx skills add sung1-labs\u002Fsddx --skill write-openspec-docs",{"tool":41,"command":42},"pnpm","pnpm dlx skills add sung1-labs\u002Fsddx --skill write-openspec-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Flibrary\u002Fopenspec\u002Fsddx-openspec-agent-write-openspec-docs\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"full-process.md","REFERENCE","参考文档",3196,"https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Flibrary\u002Fopenspec\u002Fsddx-openspec-agent-write-openspec-docs\u002Ffull-process.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"writing.md",17618,"https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Flibrary\u002Fopenspec\u002Fsddx-openspec-agent-write-openspec-docs\u002Fwriting.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7C8TCN2HNT036445CS1VBHT","sddx-verify","Verify the complete SDDx change against its specifications, architecture, implementation, tests, security, operations, and deployment expectations.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-verify\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7C8T9FQKTSN971MP6RSV0GK","sddx-quick","Handle a small, bounded change with minimal durable artifacts while preserving verification and automatic escalation when scope grows.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-quick\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7C8T6C21FE8ZX8XDSJ5VJ5R","sddx-propose","Turn a resolved SDDx exploration into durable proposal, requirements, design, tasks, and optional RFC artifacts.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-propose\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7C8T2QDGTK9PPG4A3JXXS28","sddx-explore","Explore a change before implementation, resolve the applicable product, UX, architecture, security, testing, deployment, and operational questions, and recommend the next SDDx workflow.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-explore\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7C8SZ9GTETBRKEXT43EZ9G9","sddx-debug","Diagnose and fix a defect through reproduction, evidence-based hypotheses, a minimal fix, regression coverage, and verification.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-debug\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7C8SW14B7XG3TSQGGWZ0ZCH","sddx-archive","Complete a verified SDDx change, preserve its durable record, synchronize specifications, and recommend the next workflow.","https:\u002F\u002Fgithub.com\u002Fsung1-labs\u002Fsddx\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fsddx-archive\u002FSKILL.md",[],[]]