[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EAWZFS738KX2BG3SMKCZN6":3,"skill-same:01M7EAWZFS738KX2BG3SMKCZN6":65},{"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":36,"ownerDescription":6,"updatedAt":37,"install":38,"resources":50},"01M7EAWZFS738KX2BG3SMKCZN6","speckit-checklist",null,"Generate a custom checklist for the current feature based on user requirements.","kevinglover\u002Fharnessmith","kevinglover","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2983582?v=4","01M7EAVR2H9P1CM9TAGYQPGKZ2","Kevin Glover","01M7EAVR3K9AR94YSGAPKRE3HH",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fevaluations\u002Fvariants\u002Fspeckit-checklist-router-v2\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"speckit-checklist\"\ndescription: \"Generate a custom checklist for the current feature based on user requirements.\"\nargument-hint: \"Domain or focus area for the checklist\"\ncompatibility: \"Requires spec-kit project structure with .specify\u002F directory\"\nmetadata:\n  author: \"github-spec-kit\"\n  source: \"templates\u002Fcommands\u002Fchecklist.md\"\nuser-invocable: true\ndisable-model-invocation: false\n---\n\n# Requirements-quality checklists\n\nEvaluate what the requirements document specifies: completeness, clarity,\nconsistency, measurability, and scenario coverage. Do not turn the task into\nimplementation testing. Respect the user's focus, audience, depth, and requested\noutput; do not invent requirement values or missing project facts.\n\n## Shared rules\n\n- Write questions about whether requirements are defined, quantified, consistent,\n  or complete. Cover relevant primary, alternate, exception, recovery, and\n  non-functional scenarios; flag missing requirements instead of inventing them.\n- For checklist items, use `- [ ] CHK###` with incrementing IDs, a question, and a\n  bracketed quality dimension. Reference existing requirements with `[Spec §ID]`;\n  use `[Gap]`, `[Ambiguity]`, `[Conflict]`, or `[Assumption]` as appropriate.\n  When a question identifies a missing policy or requirement, include `[Gap]`\n  even when it also cites a related existing spec section.\n  At least 80% of generated items must have a traceability reference or marker.\n- Custom checklists are reviewer-owned. Generate unchecked items only. `[x]`\n  means reviewer approval of requirements quality, not implementation completion.\n  Evaluate existing items only when the reviewer asks. The built-in\n  `checklists\u002Frequirements.md` maintained by specify\u002Fclarify is a separate case.\n- When writing a checklist file, preserve every existing byte, including notes\n  and checkbox states; append with IDs continuing after the last existing ID.\n  Never replace or reformat prior content.\n- Honor the user's requested count and allocation. When they ask for one question\n  per topic, assign a distinct question to each topic; do not combine topics or\n  fill the count with a question that repeats them. Consolidate duplicates only\n  within that allocation. Without an explicit allocation, prioritize by risk if\n  candidates exceed 40 and combine more than five low-impact edge cases.\n\n## Choose the relevant guidance\n\nFor a consultation using supplied context, answer directly using the shared rules.\nDo not initiate project generation just because this skill is selected. Clarify\nonly missing information that materially changes the requested result.\n\nFor creating or appending an actual project checklist, read\n[project-generation.md](references\u002Fproject-generation.md) before taking project\nactions. It contains prerequisite\u002Ftemplate discovery, constitution and feature\ncontext loading, clarification defaults, file structure, reporting, and the full\nbefore\u002Fafter extension-hook procedure. Follow its sequence, including enabled\nmandatory hooks and their completion, unless the user has explicitly limited scope.\n\nFor requests for domain sample questions, or when examples are needed to resolve\nan item-writing ambiguity, read\n[Example Checklist Types & Sample Items](references\u002Fexample-checklist-types-sample-items.md).\n\nFor requests for wrong\u002Fright examples or for correcting implementation-test wording,\nread [Anti-Examples: What NOT To Do](references\u002Fanti-examples-what-not-to-do.md).\n\nLoad only the guidance relevant to the task. A linked reference is not itself a\nreason to read it. When quoting an example, read its source and preserve its wording.\n","# Requirements-quality checklists\n\nEvaluate what the requirements document specifies: completeness, clarity,\nconsistency, measurability, and scenario coverage. Do not turn the task into\nimplementation testing. Respect the user's focus, audience, depth, and requested\noutput; do not invent requirement values or missing project facts.\n\n## Shared rules\n\n- Write questions about whether requirements are defined, quantified, consistent,\n  or complete. Cover relevant primary, alternate, exception, recovery, and\n  non-functional scenarios; flag missing requirements instead of inventing them.\n- For checklist items, use `- [ ] CHK###` with incrementing IDs, a question, and a\n  bracketed quality dimension. Reference existing requirements with `[Spec §ID]`;\n  use `[Gap]`, `[Ambiguity]`, `[Conflict]`, or `[Assumption]` as appropriate.\n  When a question identifies a missing policy or requirement, include `[Gap]`\n  even when it also cites a related existing spec section.\n  At least 80% of generated items must have a traceability reference or marker.\n- Custom checklists are reviewer-owned. Generate unchecked items only. `[x]`\n  means reviewer approval of requirements quality, not implementation completion.\n  Evaluate existing items only when the reviewer asks. The built-in\n  `checklists\u002Frequirements.md` maintained by specify\u002Fclarify is a separate case.\n- When writing a checklist file, preserve every existing byte, including notes\n  and checkbox states; append with IDs continuing after the last existing ID.\n  Never replace or reformat prior content.\n- Honor the user's requested count and allocation. When they ask for one question\n  per topic, assign a distinct question to each topic; do not combine topics or\n  fill the count with a question that repeats them. Consolidate duplicates only\n  within that allocation. Without an explicit allocation, prioritize by risk if\n  candidates exceed 40 and combine more than five low-impact edge cases.\n\n## Choose the relevant guidance\n\nFor a consultation using supplied context, answer directly using the shared rules.\nDo not initiate project generation just because this skill is selected. Clarify\nonly missing information that materially changes the requested result.\n\nFor creating or appending an actual project checklist, read\n[project-generation.md](references\u002Fproject-generation.md) before taking project\nactions. It contains prerequisite\u002Ftemplate discovery, constitution and feature\ncontext loading, clarification defaults, file structure, reporting, and the full\nbefore\u002Fafter extension-hook procedure. Follow its sequence, including enabled\nmandatory hooks and their completion, unless the user has explicitly limited scope.\n\nFor requests for domain sample questions, or when examples are needed to resolve\nan item-writing ambiguity, read\n[Example Checklist Types & Sample Items](references\u002Fexample-checklist-types-sample-items.md).\n\nFor requests for wrong\u002Fright examples or for correcting implementation-test wording,\nread [Anti-Examples: What NOT To Do](references\u002Fanti-examples-what-not-to-do.md).\n\nLoad only the guidance relevant to the task. A linked reference is not itself a\nreason to read it. When quoting an example, read its source and preserve its wording.\n",{"name":5,"metadata":24,"description":7,"argument-hint":27,"compatibility":28,"user-invocable":29,"disable-model-invocation":20},{"author":25,"source":26},"github-spec-kit","templates\u002Fcommands\u002Fchecklist.md","Domain or focus area for the checklist","Requires spec-kit project structure with .specify\u002F directory",true,"main","478cfb7e4e53b8612d635c13c7f8654031badcbd","evaluations\u002Fvariants\u002Fspeckit-checklist-router-v2",0,"https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith","https:\u002F\u002Fgithub.com\u002Fkevinglover","http:\u002F\u002Fglover.io","2026-11-05 04:44:54",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":29},[40,43,46],{"tool":41,"command":42},"npx","npx skills add kevinglover\u002Fharnessmith --skill speckit-checklist",{"tool":44,"command":45},"bunx","bunx skills add kevinglover\u002Fharnessmith --skill speckit-checklist",{"tool":47,"command":48},"pnpm","pnpm dlx skills add kevinglover\u002Fharnessmith --skill speckit-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fevaluations\u002Fvariants\u002Fspeckit-checklist-router-v2\u002FSKILL.md",[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fanti-examples-what-not-to-do.md","REFERENCE","参考文档",1396,"https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fevaluations\u002Fvariants\u002Fspeckit-checklist-router-v2\u002Freferences\u002Fanti-examples-what-not-to-do.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fexample-checklist-types-sample-items.md",2106,"https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fevaluations\u002Fvariants\u002Fspeckit-checklist-router-v2\u002Freferences\u002Fexample-checklist-types-sample-items.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fproject-generation.md",19158,"https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fevaluations\u002Fvariants\u002Fspeckit-checklist-router-v2\u002Freferences\u002Fproject-generation.md",[66,73,80,87,94,101],{"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},"01M7EB07Y1MWX4ZTX1CG2YC6EX","speckit-taskstoissues","Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.","https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-taskstoissues\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},"01M7EB046SKEQ9GT7STG1T7818","speckit-tasks","Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.","https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-tasks\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},"01M7EB00M6YA8W3V4RJN0NPD57","speckit-specify","Create or update the feature specification from a natural language feature description.","https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-specify\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},"01M7EAZVA1CE5DQE408PJXFE7D","speckit-plan","Execute the implementation planning workflow using the plan template to generate design artifacts.","https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-plan\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7EAZR36Z79X61Y5TV2AQJ44","speckit-implement","Execute the implementation plan by processing and executing all tasks defined in tasks.md","https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-implement\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":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7EAZK7JQ2RAZ77TPA385NN7","speckit-converge","Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.","https:\u002F\u002Fgithub.com\u002Fkevinglover\u002Fharnessmith\u002Fblob\u002Fmain\u002Fskills\u002Fspeckit-converge\u002FSKILL.md",[],[]]