[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KKC9GGCCSH0K1V73H5TR2N":3,"skill-same:01M6KKC9GGCCSH0K1V73H5TR2N":87},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6KKC9GGCCSH0K1V73H5TR2N","write-spec",null,"Draft feature specifications, requirements documents, user stories, acceptance criteria, and validation-ready specs from a feature request. Use this skill when you need to write a spec, define requirements, capture user stories, or produce a structured specification document.","markhazleton\u002Fdevspark","markhazleton","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F223906?v=4","01M6KK0W78YZYB4P42RD3SPBPY","Mark Hazleton","01M6KK0WB5CB9VWPRVTAS52ZG8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fwrite-spec\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"write spec","write","spec","specification","request","stories","you","specifications","feature","define","requirements","draft","acceptance criteria","document","ready","use","produce","acceptance","dev","documents","2026-11-10 10:12:30",false,"---\nsource: \"DevSpark — © 2026 Make Bold Solutions. Source: https:\u002F\u002Fdev.makeboldspark.com\"\nname: write-spec\ndescription: Draft feature specifications, requirements documents, user stories, acceptance criteria, and validation-ready specs from a feature request. Use this skill when you need to write a spec, define requirements, capture user stories, or produce a structured specification document.\nmetadata:\n  version: \"0.1.0\"\n---\n\n# write-spec\n\nDraft a structured feature specification from a user's feature request. This\nskill works in any skills-compatible client with or without DevSpark installed.\n\n---\n\n## Context Loading\n\nBefore drafting, run the context-gathering script for your platform:\n\n- **PowerShell**: `scripts\u002Fgather-context.ps1`\n- **Bash\u002FmacOS\u002FLinux**: `bash scripts\u002Fgather-context.sh`\n\nParse the JSON output. If the script exits non-zero, produces empty output, or\nproduces non-JSON output, use this fallback and continue without blocking:\n\n```json\n{\n  \"constitution_summary\": null,\n  \"prior_specs\": [],\n  \"skipped_context\": [\"script-error\"]\n}\n```\n\nThe JSON output contains:\n\n- `constitution_summary` — key constraints from the repo constitution, or null\n- `prior_specs` — list of prior spec summaries for naming and scope awareness\n- `skipped_context` — list of context items that could not be gathered\n\nIf `constitution_summary` is non-null, apply the listed constraints to the spec.\nIf `prior_specs` is non-empty, use the existing numbering pattern for the new\nspec and avoid duplicating solved problems.\n\n---\n\n## Drafting Procedure\n\nUse the spec template in `references\u002Fspec-template.md`.\n\n1. Set `name` from the feature request. Generate a sequential number if prior\n   specs are available (e.g., if the last spec was `004-...`, use `005-`).\n2. Set `status: Draft` always. Do not set any other lifecycle state.\n3. Write the **Product Owner TLDR** — a short non-technical summary that\n   clearly states WHAT this spec changes and WHY it matters now.\n4. Write the **Rationale Summary** — core problem, decision summary, key\n   drivers, tradeoffs considered.\n5. Write **User Stories** — at least one per priority tier in the request.\n   Each story must have: actor, capability, business value, and acceptance\n   scenarios.\n6. Write **Requirements** — MUST-level functional requirements as the minimum\n   viable set. Do not add requirements the user has not implied.\n7. Write **Success Criteria** — measurable outcomes. Each criterion must be\n   verifiable without DevSpark installed.\n8. Add an **Assumptions** section listing anything the spec takes for granted,\n   including any context items listed in `skipped_context`.\n9. Add an **Out of Scope** section. Capture anything explicitly not covered by\n   this spec.\n\nDo NOT include implementation details (frameworks, library versions, file\npaths). Keep the spec technology-agnostic.\n\nLimit `[NEEDS CLARIFICATION]` markers to three. Use them only for genuine\nblocking ambiguities that would prevent drafting a section.\n\n---\n\n## Clarification Format\n\nWhen a `[NEEDS CLARIFICATION]` marker is needed, follow this format:\n\n```text\n[NEEDS CLARIFICATION]: \u003Cquestion>\nContext: \u003Cwhy this matters for the spec>\nOptions: \u003Clist 2-3 concrete options when possible>\n```\n\nConsolidate related ambiguities into one marker. Do not add markers for\nstylistic preferences or implementation decisions.\n\n---\n\n## Output\n\nProduce a single `spec.md` file in the current working directory (or the path\nprovided by the host client). The file must:\n\n- Pass the shared spec validation contract (see `references\u002Fspec-template.md`)\n- Have valid YAML frontmatter with `status: Draft`\n- Contain a `Product Owner TLDR` section that answers WHAT and WHY at a high level\n- Contain the four mandatory full-spec sections: Rationale Summary, User\n   Stories, Requirements, and Success Criteria\n- Contain no more than three `[NEEDS CLARIFICATION]` markers\n- Contain no implementation details (no language choices, no library versions)\n\nDo not perform branch creation, file moves to governed paths, checklist\ngeneration, or gate enforcement. Those are DevSpark-command responsibilities.\n\n---\n\n## Assumptions Section\n\nIn the produced `spec.md`, always include an Assumptions section that lists:\n\n- Any context gathered or not gathered (from `skipped_context`)\n- Any decisions made without user input\n- Any scope boundaries inferred rather than stated\n","# write-spec\n\nDraft a structured feature specification from a user's feature request. This\nskill works in any skills-compatible client with or without DevSpark installed.\n\n---\n\n## Context Loading\n\nBefore drafting, run the context-gathering script for your platform:\n\n- **PowerShell**: `scripts\u002Fgather-context.ps1`\n- **Bash\u002FmacOS\u002FLinux**: `bash scripts\u002Fgather-context.sh`\n\nParse the JSON output. If the script exits non-zero, produces empty output, or\nproduces non-JSON output, use this fallback and continue without blocking:\n\n```json\n{\n  \"constitution_summary\": null,\n  \"prior_specs\": [],\n  \"skipped_context\": [\"script-error\"]\n}\n```\n\nThe JSON output contains:\n\n- `constitution_summary` — key constraints from the repo constitution, or null\n- `prior_specs` — list of prior spec summaries for naming and scope awareness\n- `skipped_context` — list of context items that could not be gathered\n\nIf `constitution_summary` is non-null, apply the listed constraints to the spec.\nIf `prior_specs` is non-empty, use the existing numbering pattern for the new\nspec and avoid duplicating solved problems.\n\n---\n\n## Drafting Procedure\n\nUse the spec template in `references\u002Fspec-template.md`.\n\n1. Set `name` from the feature request. Generate a sequential number if prior\n   specs are available (e.g., if the last spec was `004-...`, use `005-`).\n2. Set `status: Draft` always. Do not set any other lifecycle state.\n3. Write the **Product Owner TLDR** — a short non-technical summary that\n   clearly states WHAT this spec changes and WHY it matters now.\n4. Write the **Rationale Summary** — core problem, decision summary, key\n   drivers, tradeoffs considered.\n5. Write **User Stories** — at least one per priority tier in the request.\n   Each story must have: actor, capability, business value, and acceptance\n   scenarios.\n6. Write **Requirements** — MUST-level functional requirements as the minimum\n   viable set. Do not add requirements the user has not implied.\n7. Write **Success Criteria** — measurable outcomes. Each criterion must be\n   verifiable without DevSpark installed.\n8. Add an **Assumptions** section listing anything the spec takes for granted,\n   including any context items listed in `skipped_context`.\n9. Add an **Out of Scope** section. Capture anything explicitly not covered by\n   this spec.\n\nDo NOT include implementation details (frameworks, library versions, file\npaths). Keep the spec technology-agnostic.\n\nLimit `[NEEDS CLARIFICATION]` markers to three. Use them only for genuine\nblocking ambiguities that would prevent drafting a section.\n\n---\n\n## Clarification Format\n\nWhen a `[NEEDS CLARIFICATION]` marker is needed, follow this format:\n\n```text\n[NEEDS CLARIFICATION]: \u003Cquestion>\nContext: \u003Cwhy this matters for the spec>\nOptions: \u003Clist 2-3 concrete options when possible>\n```\n\nConsolidate related ambiguities into one marker. Do not add markers for\nstylistic preferences or implementation decisions.\n\n---\n\n## Output\n\nProduce a single `spec.md` file in the current working directory (or the path\nprovided by the host client). The file must:\n\n- Pass the shared spec validation contract (see `references\u002Fspec-template.md`)\n- Have valid YAML frontmatter with `status: Draft`\n- Contain a `Product Owner TLDR` section that answers WHAT and WHY at a high level\n- Contain the four mandatory full-spec sections: Rationale Summary, User\n   Stories, Requirements, and Success Criteria\n- Contain no more than three `[NEEDS CLARIFICATION]` markers\n- Contain no implementation details (no language choices, no library versions)\n\nDo not perform branch creation, file moves to governed paths, checklist\ngeneration, or gate enforcement. Those are DevSpark-command responsibilities.\n\n---\n\n## Assumptions Section\n\nIn the produced `spec.md`, always include an Assumptions section that lists:\n\n- Any context gathered or not gathered (from `skipped_context`)\n- Any decisions made without user input\n- Any scope boundaries inferred rather than stated\n",{"name":5,"source":44,"metadata":45,"description":7},"DevSpark — © 2026 Make Bold Solutions. Source: https:\u002F\u002Fdev.makeboldspark.com",{"version":46},"0.1.0","main","d823c831a8fc3d9a3e154001cc7abcb37861350d","templates\u002Fskills\u002Fwrite-spec",1,"https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark","http:\u002F\u002Fdev.makeboldspark.com\u002F","https:\u002F\u002Fgithub.com\u002Fmarkhazleton","https:\u002F\u002Fmarkhazleton.com","Solutions Architect, lifelong learner, passionate for solutions which make technology work for business, not sidetracked by sizzle","2026-11-15 03:43:55",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add markhazleton\u002Fdevspark --skill write-spec",{"tool":63,"command":64},"bunx","bunx skills add markhazleton\u002Fdevspark --skill write-spec",{"tool":66,"command":67},"pnpm","pnpm dlx skills add markhazleton\u002Fdevspark --skill write-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fwrite-spec\u002FSKILL.md",true,[71,77,83],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fspec-template.md","REFERENCE","参考文档",3047,"https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fwrite-spec\u002Freferences\u002Fspec-template.md",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Fgather-context.ps1","SCRIPT","脚本",3199,"https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fwrite-spec\u002Fscripts\u002Fgather-context.ps1",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"scripts\u002Fgather-context.sh",3717,"https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftemplates\u002Fskills\u002Fwrite-spec\u002Fscripts\u002Fgather-context.sh",[88,118,124,135,146,158],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":99,"publishedAt":39},"01M6MNBGS67Q2EJ8TEXQ1WXZRZ","devspark-roadmap","Optional roadmap planning. Establish product direction, record and right-size Prospective Specs, review delivery evidence for drift, and keep the roadmap structurally consistent, without touching code, tests, or Knowledge.","https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftemplates\u002Fconsumer-skills\u002Fdevspark-roadmap\u002FSKILL.md",[94],{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"devspark roadmap","roadmap","review","code","planning","product","knowledge","evidence","record","drift","delivery","tests","direction","keep","roadmap planning","size","true","for",{"skillNo":119,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":39},"01M6MNB3KS236X44PZF2280RRE","https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fdevspark-roadmap\u002FSKILL.md",[122],{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},[100,101,115,116,117,113,102,114,103,104,105,106,107,108,109,110,111,112],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"01M6KKDZCRGPT87KHMMB7TSD39","team-helper","Unrelated team skill","https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fupgrade\u002Fforeign-files\u002F.github\u002Fskills\u002Fteam-helper\u002FSKILL.md",[],[131,132,133,134],"team helper","helper","team","unrelated",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":39},"01M6KKDWN5WYWQ5VZDE5YKDJVW","devspark-specify","Team-authored skill that happens to use a managed name","https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fupgrade\u002Fforeign-files\u002F.github\u002Fskills\u002Fdevspark-specify\u002FSKILL.md",[],[142,143,133,34,144,116,145],"devspark specify","specify","name","managed",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":39},"01M6KKDR6B2Y3KQ47WJD5DE1QW","devspark-retired-demo","Previously generated skill whose command is no longer shipped","https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fupgrade\u002Fforeign-files\u002F.github\u002Fskills\u002Fdevspark-retired-demo\u002FSKILL.md",[],[153,154,155,116,156,157],"devspark retired demo","demo","generated skill","generated","command",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":39},"01M6KKDM0PKYYDC3PRF5NES3RB","devspark-next","Detect the next lifecycle step","https:\u002F\u002Fgithub.com\u002Fmarkhazleton\u002Fdevspark\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fupgrade\u002Fforeign-files\u002F.github\u002Fskills\u002Fdevspark-next\u002FSKILL.md",[],[165,166,167,116,168],"next","devspark next","detect","lifecycle"]