[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BKMCY1XHFFNEWDVF53GCJC":3,"skill-same:01M7BKMCY1XHFFNEWDVF53GCJC":50},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7BKMCY1XHFFNEWDVF53GCJC","next-steps",null,"Identify remaining completion requirements, meaningful learning to review, and ready successor work.","BetoFrega\u002Fskills","BetoFrega","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F637874?v=4","01M7BKHP444BSK41T281GQDPM7","Beto Frega","01M7BKHP5863T6EC03B63D0Q4T",0,"MIT","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fnext-steps\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: next-steps\ndescription: Identify remaining completion requirements, meaningful learning to review, and ready successor work.\n---\n\n# Next Steps\n\nStart from the latest goal, plan, results, and user corrections. Read the relevant\nwork records, canonical references, and configured completion and delivery rules, and\nverify the actual state of artifacts. Apply\n[artifact links](..\u002Fconsolidate\u002Freferences\u002Fartifact-links.md) to every cited document\nor ticket.\n\nThe user may be switching tasks, so make each consequential next step understandable\non its own: name the project or topic when ambiguous, the components or domain\nentities involved, the action or pending choice, and why it matters or what it\nunlocks. Explain references such as a phase, contract, or issue instead of relying on\ntheir names. Reuse context that is already clear. When a detail is missing, inspect\nthe sources or name the gap, and skip a recap of the whole task.\n\n## Current work incomplete\n\nList the required actions in execution order, immediate action first, with blockers\nand decisions next to the actions they affect. Take the requirements from the goal,\nacceptance, and project workflow: evidence, a rehearsed demo script ([demo-day](..\u002Fdemo-day\u002FSKILL.md)) and the user's\nreview of interaction changes, canonical updates, checks, review, integration,\ndeployment, operational verification, and tracker closure, each only where required. Discovery work is complete when it produces its expected evidence or\noutput, even without a feature.\n\nEach required condition needs verified evidence before you call the work complete,\nper [Evidence Before Claims](..\u002Fbeto-mode\u002Fprinciples\u002Fevidence-before-claims.md). Apply\n[local document delivery](..\u002Fconsolidate\u002Freferences\u002Flocal-document-delivery.md) to\nseparate saved documentation from pending `origin\u002Fmain` integration. For product\nobservations, use [consolidate](..\u002Fconsolidate\u002FSKILL.md) to read implementation,\ndeployment, authorized release, exposure, and flags as separate dimensions.\n\n## Current work complete\n\nRecommend [review-learnings](..\u002Freview-learnings\u002FSKILL.md) when results materially\ncontradict hypotheses, change scope, direction, or rules, or affect related or pending\nwork, taking configured review points into account. Keep required knowledge\nmaintenance apart from learning review. Skip a review per item, and skip reviewing\nlearning already incorporated unless there is new evidence or a review point.\n\nInspect follow-ups, the selected increment or spec references, parent and dependency\nrelations, remaining work, readiness, and documented priority. Recommend one open\nsuccessor whose prerequisites you verified, with its link and title or identifier and\nits value toward the goal. Resolve consequential findings that invalidate its scope or\nreadiness before it starts. A future idea is not yet selected or ready, and having no\nknown blockers does not make work ready. Without tickets, the successor needs support\nfrom the goal and verified relationships. Leave out unsupported successors, report\nunavailable sources, and keep current requirements apart from later work.\n\n## Invocation boundary\n\nAn explicit invocation only reports: return the guidance and end. During execution,\nfinish the remaining authorized work before the final report, or name its blocker.\nUse execution skills for actions and consolidate for canonical records. A\nrecommendation grants no new permission for work, decisions, publication, release, or\nscheduling, and existing authorization still applies. If no goal is known, ask which\ntask the user means.\n","# Next Steps\n\nStart from the latest goal, plan, results, and user corrections. Read the relevant\nwork records, canonical references, and configured completion and delivery rules, and\nverify the actual state of artifacts. Apply\n[artifact links](..\u002Fconsolidate\u002Freferences\u002Fartifact-links.md) to every cited document\nor ticket.\n\nThe user may be switching tasks, so make each consequential next step understandable\non its own: name the project or topic when ambiguous, the components or domain\nentities involved, the action or pending choice, and why it matters or what it\nunlocks. Explain references such as a phase, contract, or issue instead of relying on\ntheir names. Reuse context that is already clear. When a detail is missing, inspect\nthe sources or name the gap, and skip a recap of the whole task.\n\n## Current work incomplete\n\nList the required actions in execution order, immediate action first, with blockers\nand decisions next to the actions they affect. Take the requirements from the goal,\nacceptance, and project workflow: evidence, a rehearsed demo script ([demo-day](..\u002Fdemo-day\u002FSKILL.md)) and the user's\nreview of interaction changes, canonical updates, checks, review, integration,\ndeployment, operational verification, and tracker closure, each only where required. Discovery work is complete when it produces its expected evidence or\noutput, even without a feature.\n\nEach required condition needs verified evidence before you call the work complete,\nper [Evidence Before Claims](..\u002Fbeto-mode\u002Fprinciples\u002Fevidence-before-claims.md). Apply\n[local document delivery](..\u002Fconsolidate\u002Freferences\u002Flocal-document-delivery.md) to\nseparate saved documentation from pending `origin\u002Fmain` integration. For product\nobservations, use [consolidate](..\u002Fconsolidate\u002FSKILL.md) to read implementation,\ndeployment, authorized release, exposure, and flags as separate dimensions.\n\n## Current work complete\n\nRecommend [review-learnings](..\u002Freview-learnings\u002FSKILL.md) when results materially\ncontradict hypotheses, change scope, direction, or rules, or affect related or pending\nwork, taking configured review points into account. Keep required knowledge\nmaintenance apart from learning review. Skip a review per item, and skip reviewing\nlearning already incorporated unless there is new evidence or a review point.\n\nInspect follow-ups, the selected increment or spec references, parent and dependency\nrelations, remaining work, readiness, and documented priority. Recommend one open\nsuccessor whose prerequisites you verified, with its link and title or identifier and\nits value toward the goal. Resolve consequential findings that invalidate its scope or\nreadiness before it starts. A future idea is not yet selected or ready, and having no\nknown blockers does not make work ready. Without tickets, the successor needs support\nfrom the goal and verified relationships. Leave out unsupported successors, report\nunavailable sources, and keep current requirements apart from later work.\n\n## Invocation boundary\n\nAn explicit invocation only reports: return the guidance and end. During execution,\nfinish the remaining authorized work before the final report, or name its blocker.\nUse execution skills for actions and consolidate for canonical records. A\nrecommendation grants no new permission for work, decisions, publication, release, or\nscheduling, and existing authorization still applies. If no goal is known, ask which\ntask the user means.\n",{"name":5,"description":7},"main","b212a89a4ff3d13380a0ee75a91d99ee0aad2858","skills\u002Fnext-steps","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills","https:\u002F\u002Fgithub.com\u002FBetoFrega","2026-11-14 02:43:03",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add BetoFrega\u002Fskills --skill next-steps",{"tool":36,"command":37},"bunx","bunx skills add BetoFrega\u002Fskills --skill next-steps",{"tool":39,"command":40},"pnpm","pnpm dlx skills add BetoFrega\u002Fskills --skill next-steps","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fnext-steps\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",163,"https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fnext-steps\u002Fagents\u002Fopenai.yaml",[51,58,66,73,81,88],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7BKPW918QFBHANWQRR8JXTA","writing-for-humans","Load before writing any reader-facing text, including messages, and follow its rules as you write. Also use to rewrite or audit existing prose for plain language, clarity, readability, or actionability.","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-humans\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":62,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7BKPSYAK48C7RBZXKQN805M","writing-for-agents","Write agent-facing documents. Use when creating or editing skills, AGENTS.md, or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\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},"01M7BKPQG1ZNVYYJVSGE69V5DZ","write-adr","Write, revise, or supersede architecture decision records (ADRs) documenting an architectural choice and its rationale.","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-adr\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":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7BKPMZC59QZ0G1746SCZ3S4","wizard","Wizard scripts for human-only provisioning, credential\u002FCI setup, unfamiliar dashboards, migrations, or cutovers; use only for steps the agent cannot perform.","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7BKPHD7Y6X4BM9SV06PNKAC","verify","Check whether the current task's claimed outcome is confirmed.","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"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":94,"publishedAt":19},"01M7BKPESBZ2WZYN1EWK6SGB67","verb-tense","Choose verb tense and mood by when each event happens and how certain it is. Use when writing or reviewing any text, and when a reader asks for a tense review.","https:\u002F\u002Fgithub.com\u002FBetoFrega\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fverb-tense\u002FSKILL.md",[],[]]