[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVC9F58D5TQR13JC4F67FE":3,"skill-same:01M7CVC9F58D5TQR13JC4F67FE":55},{"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},"01M7CVC9F58D5TQR13JC4F67FE","plan-spec",null,"Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","TudeOrangBiasa\u002Fskills-for-agents","TudeOrangBiasa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F125188681?v=4","01M7CV804RMMCVN5M0D4ZCQ6D8","TudeStillLearning!","01M7CV805CRFTQY48WZ6JK57YK",1,"MIT","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-spec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: plan-spec\ndescription: \"Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.\"\ndisable-model-invocation: true\n---\n\nThis skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-repo`.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\nPre-write gate: do not write the spec until both lists exist. Map: components, data flow, and the expensive decisions, agreed with the user. Guardrails: what must always happen, what must never happen, and the key failure cases. If either list is vague, return to `\u002Fplan-grill-docs` first; a spec written over fog just freezes the fog.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\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\nA LONG, numbered list of user stories. Each user story should be in the format of:\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\nThis list of user stories should be extremely extensive and cover all aspects of 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- A description of what makes a good test (only test external behavior, not implementation details)\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","This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know.\n\nThe issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `\u002Fsetup-repo`.\n\n## Process\n\n1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.\n\n2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.\n\nCheck with the user that these seams match their expectations.\n\nPre-write gate: do not write the spec until both lists exist. Map: components, data flow, and the expensive decisions, agreed with the user. Guardrails: what must always happen, what must never happen, and the key failure cases. If either list is vague, return to `\u002Fplan-grill-docs` first; a spec written over fog just freezes the fog.\n\n3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.\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\nA LONG, numbered list of user stories. Each user story should be in the format of:\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\nThis list of user stories should be extremely extensive and cover all aspects of 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- A description of what makes a good test (only test external behavior, not implementation details)\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","d26d63fb9a1a8091ba1d908b1b35738b60e8be79","skills\u002Fuser-invoked\u002Fplan-spec",0,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa","2026-11-05 23:44:38",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add TudeOrangBiasa\u002Fskills-for-agents --skill plan-spec",{"tool":38,"command":39},"bunx","bunx skills add TudeOrangBiasa\u002Fskills-for-agents --skill plan-spec",{"tool":41,"command":42},"pnpm","pnpm dlx skills add TudeOrangBiasa\u002Fskills-for-agents --skill plan-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-spec\u002FSKILL.md",[45,51],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",135,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-spec\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"CREDITS.md",463,"https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fplan-spec\u002FCREDITS.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CVDKFYKNEY024TK36QAA2R","whips","Route any non-trivial task through one entry: match a playbook, drive HIT skills plus subagents, open a reviewed ready PR with ship-pr-shaped evidence.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fwhips\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CVDFG46BBHV71Q5JVZ7XZT","verify-upkeep","Periodic upkeep for a project's verification skill: source wave plus live pass per feature, at most one PR of proven corrections. Use to audit the verify skill.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-upkeep\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CVDB20QNGAPR8T5YXDRNT9","verify-statechart","Check a TLA+ model of a system that moves between states, such as a product flow, a protocol, or a service, and draw it as a Mermaid statechart. The report gives the shortest path to each state that breaks a rule. Use to show a bug as a path through states.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-statechart\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CVD6Y3W2A12ZDEQBS39QPD","verify-new","Generate a project-local skill that drives the app like a user (launch, doctor, drive, evidence, feature map), proven once. Use when a project has no scripted proof.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fverify-new\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CVD2WTQ83ETMQ82GWWZAAV","ship-triage","Move issues and external PRs through a state machine of triage roles, categorise, verify, interview if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fship-triage\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CVCYS0S8S8XW68V819QKZ6","ship-runner","Run ready-for-agent issue queues on any schedule through \u002Fwhips intake, one fresh worktree each, landing per risk tier, with the agent and model you pick at setup.","https:\u002F\u002Fgithub.com\u002FTudeOrangBiasa\u002Fskills-for-agents\u002Fblob\u002Fmain\u002Fskills\u002Fuser-invoked\u002Fship-runner\u002FSKILL.md",[],[]]