[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DP0980WB0ZPEN21FKYQZ1":3,"skill-same:01M79DP0980WB0ZPEN21FKYQZ1":46},{"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":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79DP0980WB0ZPEN21FKYQZ1","drive-development-flow",null,"Select the next software workflow when defining, implementing, reviewing, or resuming development work.","AO-HyS\u002Fdevelopment-system","AO-HyS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286554351?v=4","01M79DCXZGC6076EH5QATNXCY2","AO HyS","01M79DCY06TSBCJ946VP0BT0RG",0,"MIT","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.18.0\u002Fskills\u002Finternal\u002Fdrive-development-flow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: drive-development-flow\ndescription: Select the next software workflow when defining, implementing, reviewing, or resuming development work.\n---\n\n# Development flow\n\nOptimize **rápido → bien → barato**: time to the complete usable outcome,\nincluding corrections. Recover the outcome, settled decisions and authorized\nendpoint from the current request and available project context. Follow-ups\nsteer that outcome unless the user replaces it.\n\n## Choose only the current stage\n\n- Clear implementation or a bug fix: proceed with `flow-implement`. A small,\n  obvious edit can be handled directly with applicable repository checks.\n- Approved specification: use `implement-spec` when coordinating its scope or\n  ticket dependencies; reuse the existing spec instead of defining it again.\n- Requested discovery or questioning: use `grill-with-docs`. Use\n  `working-backwards` for a requested PRFAQ or staged product definition.\n- New visual direction or an approved design handoff: use `design-direction`.\n  A small visual refinement stays in Impeccable's matching workflow.\n- Branch\u002Fdiff review: use `flow-code-review`. Review of a thread's claims and\n  execution history: use `review-thread`.\n- Explanation or status: answer from relevant sources; this does not start\n  implementation or require a generated document.\n\nLoad the applicable branch, not this entire list. For non-trivial repository\nexecution, `coding-orchestration` owns delegation and verification. A worker\nwith an exact root, task and checks executes its packet; it does not repeat\nparent routing. A supplied `orchestrate-work` execution method can satisfy that\nresponsibility without loading a second coordination stack.\n\n## Continue through the agreed endpoint\n\nMake completion observable: requested behavior, relevant checks, unresolved\nacceptance criteria and the delivery surface. Reuse the existing task record;\nan ordinary edit needs no new planning document. Continue implementation,\nverification and corrections already authorized. A first draft or a worker's\ncompletion is not the user's complete result.\n\nRetain authorization across turns. Prepare the concrete, reviewable result\nbefore requesting a genuinely missing authorization for a distinct operation.\nPreserve repository protections and host permission boundaries; authority for\none operation does not automatically authorize another. Continue independent\nwork when a dependency is blocked.\n\nCurrent user instructions supersede skill guidelines. If a skill actually\nprevents authorized progress, link its exact file, quote the applicable rule\nand explain the missing decision; do not invent an approval requirement.\n","# Development flow\n\nOptimize **rápido → bien → barato**: time to the complete usable outcome,\nincluding corrections. Recover the outcome, settled decisions and authorized\nendpoint from the current request and available project context. Follow-ups\nsteer that outcome unless the user replaces it.\n\n## Choose only the current stage\n\n- Clear implementation or a bug fix: proceed with `flow-implement`. A small,\n  obvious edit can be handled directly with applicable repository checks.\n- Approved specification: use `implement-spec` when coordinating its scope or\n  ticket dependencies; reuse the existing spec instead of defining it again.\n- Requested discovery or questioning: use `grill-with-docs`. Use\n  `working-backwards` for a requested PRFAQ or staged product definition.\n- New visual direction or an approved design handoff: use `design-direction`.\n  A small visual refinement stays in Impeccable's matching workflow.\n- Branch\u002Fdiff review: use `flow-code-review`. Review of a thread's claims and\n  execution history: use `review-thread`.\n- Explanation or status: answer from relevant sources; this does not start\n  implementation or require a generated document.\n\nLoad the applicable branch, not this entire list. For non-trivial repository\nexecution, `coding-orchestration` owns delegation and verification. A worker\nwith an exact root, task and checks executes its packet; it does not repeat\nparent routing. A supplied `orchestrate-work` execution method can satisfy that\nresponsibility without loading a second coordination stack.\n\n## Continue through the agreed endpoint\n\nMake completion observable: requested behavior, relevant checks, unresolved\nacceptance criteria and the delivery surface. Reuse the existing task record;\nan ordinary edit needs no new planning document. Continue implementation,\nverification and corrections already authorized. A first draft or a worker's\ncompletion is not the user's complete result.\n\nRetain authorization across turns. Prepare the concrete, reviewable result\nbefore requesting a genuinely missing authorization for a distinct operation.\nPreserve repository protections and host permission boundaries; authority for\none operation does not automatically authorize another. Continue independent\nwork when a dependency is blocked.\n\nCurrent user instructions supersede skill guidelines. If a skill actually\nprevents authorized progress, link its exact file, quote the applicable rule\nand explain the missing decision; do not invent an approval requirement.\n",{"name":5,"description":7},"main","9f5b43aadb1a92441d65e9cb74a584cd6fca62bc","artifacts\u002F1.18.0\u002Fskills\u002Finternal\u002Fdrive-development-flow","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system","https:\u002F\u002Fgithub.com\u002FAO-HyS","https:\u002F\u002Faohys.net\u002F","Software Boutique, we make your projects come true live. ","2026-11-14 03:17:27",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add AO-HyS\u002Fdevelopment-system --skill drive-development-flow",{"tool":38,"command":39},"bunx","bunx skills add AO-HyS\u002Fdevelopment-system --skill drive-development-flow",{"tool":41,"command":42},"pnpm","pnpm dlx skills add AO-HyS\u002Fdevelopment-system --skill drive-development-flow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.18.0\u002Fskills\u002Finternal\u002Fdrive-development-flow\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M79EQ4BPYQTX8RWN1Y1J2K1F","working-backwards","Define a software feature through PRFAQ and staged documents when the user requests working backwards before coding.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fworking-backwards\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79EQ2E8P85Y1Y7VNJZMNEJE","flow-implement","Implement a requested software change through verification, corrections, and its authorized delivery endpoint.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fflow-implement\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79EQ0PNMKHPJ78F8WMNX06P","development-steward","Run the scheduled, read-only weekly maintenance review for the six explicitly opted-in repositories and prepare one concise private report for Check-in.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.8.0\u002Fskills\u002Finternal\u002Fdevelopment-steward\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79EPXJ56MX7955GWP1HD4B0","grill-with-docs","Run one recoverable interview for functional, visual, or mixed software grills; reuse equivalent answers and offer the shared HTML questionnaire.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Finternal\u002Fgrill-with-docs\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79EPTFPHYEV40ZG52Z0GVS2","global-agent-guardrails","Install, audit, test, or update the Development System's global destructive-command guard for Codex, Claude Code and T3 Code. Use when configuring agent safety hooks or investigating whether dangerous shell operations are blocked.","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Finternal\u002Fglobal-agent-guardrails\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79EPR0KPHKAFN7V6CEEDR0Y","impeccable","Design or refine frontend UI using project context and a focused design playbook; also handles visual critique and polish.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Fexternal\u002Fimpeccable\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F2.7.0\u002Fskills\u002Fexternal\u002Fimpeccable\u002FSKILL.md",[],[]]