[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGJK5ZBP4R9S0809G262SD":3,"skill-same:01M6MGJK5ZBP4R9S0809G262SD":82},{"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":28,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6MGJK5ZBP4R9S0809G262SD","sdlc-design",null,"Turn an accepted .sdlc\u002Ffeature-slug\u002Fintent.md into a policy-constrained, reviewer-approved spec.md when asked to design or specify an approved feature. Do NOT use for raw idea discovery, coding, test execution, PR review, deployment, or production monitoring.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fghiaog123\u002Fai-native-sdlc\u002Fskills\u002Fsdlc-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"sdlc design","sdlc","design","reviewer","when","for","idea discovery","test execution","feature","do","idea","intent","use","coding","discovery","execution","specify","monitoring","deployment","pr","pr review","test","policy","review","2026-11-10 10:12:30",false,"---\nname: sdlc-design\ndescription: Turn an accepted .sdlc\u002Ffeature-slug\u002Fintent.md into a policy-constrained, reviewer-approved spec.md when asked to design or specify an approved feature. Do NOT use for raw idea discovery, coding, test execution, PR review, deployment, or production monitoring.\n---\n\n# SDLC Design\n\nRun Stage 2 of 6 in the AI-Native SDLC playbook described in `docs\u002FPLAYBOOK.md`.\n\n## Purpose\n\nGenerate a testable specification from accepted intent while making policy\ncollisions and unresolved decisions visible.\n\nThe primary value of this stage is the **Flagged concerns** section. Never solve\nor hide a concern silently.\n\n## Entry gate\n\nLocate `.sdlc\u002F\u003Cslug>\u002Fintent.md`.\n\nProceed only if it exists and declares `Status: accepted`.\n\nIf the artifact is missing, still draft, or lacks explicit acceptance, route the\nwork back to `sdlc-plan` and stop.\n\nRead the entire accepted intent before generating requirements or a design.\n\n## Discover governing policy\n\nDiscover available organization skills and relevant project instructions before\ndesigning. Look specifically for brand, security, compliance, and data-handling\nskills or policies.\n\nList each discovered skill or policy that constrains the design.\n\nIf none are found, log that no organization skills were available. Do not pretend\nthat an undiscovered policy has been applied.\n\nRead the applicable guidance and constrain the proposed design by it.\n\n## Procedure\n\n1. Read the accepted `intent.md` in full.\n2. Discover and read applicable organization skills and project policies.\n3. Log the skills or policies found, or log that none were found.\n4. Convert desired outcomes into numbered requirements that can be verified.\n5. State clear non-goals to protect the accepted scope.\n6. Design the architecture, flow, data model, and interfaces within policy.\n7. Describe API, schema, persistence, and contract changes when applicable.\n8. Identify every collision among intent, policy, constraints, and open questions.\n9. Mark every concern as `blocking` or `non-blocking` and explain why.\n10. Describe how the final implementation will be verified.\n11. Write `.sdlc\u002F\u003Cslug>\u002Fspec.md` and show the complete draft to the user.\n\nUse plain language. Do not replace a requirement with an implementation preference.\n\n## Required artifact\n\nStart with this contract structure. Add `Status: draft` directly below the title\nwhile the document awaits review, then change it to `Status: accepted` only after\nexplicit approval.\n\n```markdown\n# Spec: [feature name] (from intent.md [date])\n\n## Source intent\n[one-line link to or quote from the accepted intent.md]\n\n## Requirements\n1. [testable requirement]\n2. [testable requirement]\n[etc.]\n\n## Non-goals\n[explicitly what this change does NOT do]\n\n## Design\n[architecture, flow, data model, interfaces]\n\n## Data and interfaces\n[API\u002Fschema changes, persistence, contracts]\n\n## Flagged concerns\n[CRITICAL: each blocking\u002Fnon-blocking issue, never silently resolved]\n- [concern]: [why it matters], [blocking|non-blocking]\n\n## Verification strategy\n[how we'll prove the spec worked]\n```\n\nKeep the contract headings and the concern format unchanged.\n\n## Flagged concerns rules\n\nA concern is blocking when the specification cannot safely proceed without a\ndecision or approval. Example: a new database table requires operations approval.\n\nA concern is non-blocking when it is valuable to resolve but the scoped change can\nship without it. Example: the first release does not cover every locale.\n\nFlag both kinds. Do not downgrade a blocker because a workaround seems likely.\n\nDo not silently resolve an open question, policy collision, exception, or risk.\n\nWhen a concern needs a decision, state the decision needed and its owner if known.\n\n## Exit gate\n\nShow the entire spec, including every flagged concern, then stop and ask exactly:\n\n> Reviewer, do you accept this scope and the flagged concerns?\n\nAccept only explicit human approval. Do not code, reinterpret approval, or proceed\nfrom an implied response.\n\nAfter explicit approval, change the status to `accepted` in `spec.md` and commit\nwith `Status: accepted` in the commit message.\n\nIf the reviewer requests changes, revise the draft, preserve or update concerns,\nand repeat the exit gate.\n\n## Handoff\n\nHand off the accepted `.sdlc\u002F\u003Cslug>\u002Fspec.md` to `sdlc-build`.\n\nInclude the policy sources consulted and every unresolved non-blocking concern.\n\nDo not decide a blocker on behalf of the reviewer or organization.\n","# SDLC Design\n\nRun Stage 2 of 6 in the AI-Native SDLC playbook described in `docs\u002FPLAYBOOK.md`.\n\n## Purpose\n\nGenerate a testable specification from accepted intent while making policy\ncollisions and unresolved decisions visible.\n\nThe primary value of this stage is the **Flagged concerns** section. Never solve\nor hide a concern silently.\n\n## Entry gate\n\nLocate `.sdlc\u002F\u003Cslug>\u002Fintent.md`.\n\nProceed only if it exists and declares `Status: accepted`.\n\nIf the artifact is missing, still draft, or lacks explicit acceptance, route the\nwork back to `sdlc-plan` and stop.\n\nRead the entire accepted intent before generating requirements or a design.\n\n## Discover governing policy\n\nDiscover available organization skills and relevant project instructions before\ndesigning. Look specifically for brand, security, compliance, and data-handling\nskills or policies.\n\nList each discovered skill or policy that constrains the design.\n\nIf none are found, log that no organization skills were available. Do not pretend\nthat an undiscovered policy has been applied.\n\nRead the applicable guidance and constrain the proposed design by it.\n\n## Procedure\n\n1. Read the accepted `intent.md` in full.\n2. Discover and read applicable organization skills and project policies.\n3. Log the skills or policies found, or log that none were found.\n4. Convert desired outcomes into numbered requirements that can be verified.\n5. State clear non-goals to protect the accepted scope.\n6. Design the architecture, flow, data model, and interfaces within policy.\n7. Describe API, schema, persistence, and contract changes when applicable.\n8. Identify every collision among intent, policy, constraints, and open questions.\n9. Mark every concern as `blocking` or `non-blocking` and explain why.\n10. Describe how the final implementation will be verified.\n11. Write `.sdlc\u002F\u003Cslug>\u002Fspec.md` and show the complete draft to the user.\n\nUse plain language. Do not replace a requirement with an implementation preference.\n\n## Required artifact\n\nStart with this contract structure. Add `Status: draft` directly below the title\nwhile the document awaits review, then change it to `Status: accepted` only after\nexplicit approval.\n\n```markdown\n# Spec: [feature name] (from intent.md [date])\n\n## Source intent\n[one-line link to or quote from the accepted intent.md]\n\n## Requirements\n1. [testable requirement]\n2. [testable requirement]\n[etc.]\n\n## Non-goals\n[explicitly what this change does NOT do]\n\n## Design\n[architecture, flow, data model, interfaces]\n\n## Data and interfaces\n[API\u002Fschema changes, persistence, contracts]\n\n## Flagged concerns\n[CRITICAL: each blocking\u002Fnon-blocking issue, never silently resolved]\n- [concern]: [why it matters], [blocking|non-blocking]\n\n## Verification strategy\n[how we'll prove the spec worked]\n```\n\nKeep the contract headings and the concern format unchanged.\n\n## Flagged concerns rules\n\nA concern is blocking when the specification cannot safely proceed without a\ndecision or approval. Example: a new database table requires operations approval.\n\nA concern is non-blocking when it is valuable to resolve but the scoped change can\nship without it. Example: the first release does not cover every locale.\n\nFlag both kinds. Do not downgrade a blocker because a workaround seems likely.\n\nDo not silently resolve an open question, policy collision, exception, or risk.\n\nWhen a concern needs a decision, state the decision needed and its owner if known.\n\n## Exit gate\n\nShow the entire spec, including every flagged concern, then stop and ask exactly:\n\n> Reviewer, do you accept this scope and the flagged concerns?\n\nAccept only explicit human approval. Do not code, reinterpret approval, or proceed\nfrom an implied response.\n\nAfter explicit approval, change the status to `accepted` in `spec.md` and commit\nwith `Status: accepted` in the commit message.\n\nIf the reviewer requests changes, revise the draft, preserve or update concerns,\nand repeat the exit gate.\n\n## Handoff\n\nHand off the accepted `.sdlc\u002F\u003Cslug>\u002Fspec.md` to `sdlc-build`.\n\nInclude the policy sources consulted and every unresolved non-blocking concern.\n\nDo not decide a blocker on behalf of the reviewer or organization.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fghiaog123\u002Fai-native-sdlc\u002Fskills\u002Fsdlc-design",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sdlc-design",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sdlc-design",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sdlc-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fghiaog123\u002Fai-native-sdlc\u002Fskills\u002Fsdlc-design\u002FSKILL.md",true,[],[83,93,101,109,117,125],{"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":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":92},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":92},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":92},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":92},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":92},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]