[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79EY05RBKECMDQJ3FP1SNW8":3,"skill-same:01M79EY05RBKECMDQJ3FP1SNW8":51},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":44},"01M79EY05RBKECMDQJ3FP1SNW8","to-spec",null,"Synthesize a conversation into a scoped specification, with publication when requested.","BumpyClock\u002Fagent-templates","BumpyClock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1883824?v=4","01M79EW0FDP9MFXH1FKH800S7T","Aditya Sharma","01M79EW0G27TTKZWTFQ8W5HVB4",2,"MIT","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fto-spec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-spec\ndescription: Synthesize a conversation into a scoped specification, with publication when requested.\ndisable-model-invocation: true\n---\n\nSynthesize the current conversation and relevant codebase understanding into a spec. Reuse settled requirements, contracts, and decisions without another interview.\n\nWhen fetching tracker context or preparing publication, read [Tracker integration](..\u002Ftriage\u002FTRACKER.md) for destination, role mapping, and authorization rules. Missing tracker setup does not block a draft.\n\n## Process\n\n1. Reuse existing context. Inspect relevant code only where it could change the spec's behavior or contracts. Use the project's domain glossary vocabulary and respect ADRs in the affected area.\n\n2. Identify the agreed contracts and test interfaces. Ask only about unresolved choices that materially affect scope or those contracts. Do not reopen settled seams or invent decisions to fill gaps.\n\n3. Write the requested spec using the applicable template sections below. Keep the problem, behavior, and scope explicit; scale the detail to the change. Return the draft, or publish it to the authorized destination when requested. Apply the configured `ready-for-agent` role only when the scope and contracts are settled enough for agent work.\n\nFinish with the draft or published issue reference. If publication is blocked, return the completed draft and the specific remaining decision or access requirement.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nNumber the distinct in-scope user behaviors. Use this format where it clarifies the actor and benefit:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nCover the requested behavior and meaningful edge cases without padding the list or expanding the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- The contracts and risks the selected checks address\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n","Synthesize the current conversation and relevant codebase understanding into a spec. Reuse settled requirements, contracts, and decisions without another interview.\n\nWhen fetching tracker context or preparing publication, read [Tracker integration](..\u002Ftriage\u002FTRACKER.md) for destination, role mapping, and authorization rules. Missing tracker setup does not block a draft.\n\n## Process\n\n1. Reuse existing context. Inspect relevant code only where it could change the spec's behavior or contracts. Use the project's domain glossary vocabulary and respect ADRs in the affected area.\n\n2. Identify the agreed contracts and test interfaces. Ask only about unresolved choices that materially affect scope or those contracts. Do not reopen settled seams or invent decisions to fill gaps.\n\n3. Write the requested spec using the applicable template sections below. Keep the problem, behavior, and scope explicit; scale the detail to the change. Return the draft, or publish it to the authorized destination when requested. Apply the configured `ready-for-agent` role only when the scope and contracts are settled enough for agent work.\n\nFinish with the draft or published issue reference. If publication is blocked, return the completed draft and the specific remaining decision or access requirement.\n\n\u003Cspec-template>\n\n## Problem Statement\n\nThe problem that the user is facing, from the user's perspective.\n\n## Solution\n\nThe solution to the problem, from the user's perspective.\n\n## User Stories\n\nNumber the distinct in-scope user behaviors. Use this format where it clarifies the actor and benefit:\n\n1. As an \u003Cactor>, I want a \u003Cfeature>, so that \u003Cbenefit>\n\n\u003Cuser-story-example>\n1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending\n\u003C\u002Fuser-story-example>\n\nCover the requested behavior and meaningful edge cases without padding the list or expanding the feature.\n\n## Implementation Decisions\n\nA list of implementation decisions that were made. This can include:\n\n- The modules that will be built\u002Fmodified\n- The interfaces of those modules that will be modified\n- Technical clarifications from the developer\n- Architectural decisions\n- Schema changes\n- API contracts\n- Specific interactions\n\nDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.\n\nException: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts, not a working demo, just the important bits.\n\n## Testing Decisions\n\nA list of testing decisions that were made. Include:\n\n- The contracts and risks the selected checks address\n- Which modules will be tested\n- Prior art for the tests (i.e. similar types of tests in the codebase)\n\n## Out of Scope\n\nA description of the things that are out of scope for this spec.\n\n## Further Notes\n\nAny further notes about the feature.\n\n\u003C\u002Fspec-template>\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","e24b64bdac040ad169ed16b14853eff1b20cd726","skills\u002Fengineering\u002Fto-spec",0,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates","https:\u002F\u002Fgithub.com\u002FBumpyClock","2026-11-14 03:12:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add BumpyClock\u002Fagent-templates --skill to-spec",{"tool":38,"command":39},"bunx","bunx skills add BumpyClock\u002Fagent-templates --skill to-spec",{"tool":41,"command":42},"pnpm","pnpm dlx skills add BumpyClock\u002Fagent-templates --skill to-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fto-spec\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",315,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills\u002Fengineering\u002Fto-spec\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79FEE6E257MWVEBY43X0NVN","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79FEB8GTJC6ZHDK67T40R20","workflow-from-chats","Extract preferences from agent chats → skills, rules, workflow docs. For learning preferences, mining feedback, personalizing workflows.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fworkflow-from-chats\u002FSKILL.md",[],[],{"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},"01M79FE7TMNGVZZ0M8NV4N0X6N","winui3-csharp-app","WinUI 3 \u002F Windows App SDK desktop apps in C#\u002FXAML. MVVM, bindings, navigation, Mica\u002FAcrylic, windowing, packaging, performance.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwinui3-csharp-app\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},"01M79FE31HY46BHN67CQGB7MVJ","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhy\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},"01M79FE0N7MGWDG8SCD60FWTV5","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise status update.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhat-did-i-get-done\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},"01M79FDYBJG9QNCQC0MMVBDT80","weekly-review","Produce a short weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fweekly-review\u002FSKILL.md",[],[]]