[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DSPZDF5R45KPEG5YXHE3H":3,"skill-same:01M79DSPZDF5R45KPEG5YXHE3H":76},{"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},"01M79DSPZDF5R45KPEG5YXHE3H","coding-orchestration",null,"Choose delegation, ownership, and verification for non-trivial repository execution with a pinned task contract.","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.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: coding-orchestration\ndescription: Choose delegation, ownership, and verification for non-trivial repository execution with a pinned task contract.\n---\n\n# Coding orchestration\n\nOptimize rápido → bien → barato: reach the complete usable result quickly,\ncorrect it with focused evidence, and keep measured cost and complexity low.\nPreserve behavior, data boundaries and authorization.\n\n## Govern the full feature\n\nRead [Jev governed execution](references\u002Fjev-governance.md) once for non-trivial work. Keep the\nselected parent. Use fast research, Astra planning, a different fresh Astra\nplan review, bounded writers, independent deep review and actual behavior\nevidence. Jev supplies a required judgment at each lifecycle boundary; code\nenforces the applicable gate. Tiny unrelated deterministic work stays direct.\n\n## Resolve the run\n\nThe model selected when the conversation starts remains the orchestrator. It\nchooses workers within the user's provider, quota and capability limits and\nintegrates their results. A roster or native profile is a recommendation, not\nruntime identity or a provider chain. A restricted family stays restricted for\nevery descendant; report a missing browser or vision capability instead of\nsubstituting a different family.\n\nBefore a worker starts, pin one execution contract. It names the objective or\nticket, root and revision, owned paths, expected observable behavior, mode,\nauthorization and endpoint, enumerated checks, evidence receipt, stop\nconditions, and the required completion report. Read\n[the execution contract](references\u002Fexecution-contract.md) for the compact\npacket fields.\n\nUse **exact instructions by default**: give ordered actions, expected\nobservations, checks and stops using the execution contract. Outcome delegation\nis an explicit, reasoned exception for a bounded implementation decision; record\nwhy a recipe would be premature and keep the same acceptance requirements.\n\nThe method is model-agnostic. Preserve the acceptance standard when capability\nor availability changes: reduce packet size and simultaneous decisions, supply\nconcrete examples and observable checkpoints, then correct from the returned\nevidence. A model label never proves capability or acceptance. If an essential\ncapability is unavailable, retain the gap and continue independent work; do not\nsilently substitute a provider or promise equivalent results from every model.\n\n## Execute with useful ownership\n\nThe parent owns decomposition, architecture, integration, conflicts,\nverification, findings and the terminal state. The governance runtime constrains this parent; it does not replace it with another coordinator. Execute the repository's\nlocal canonical recipe; a skill does not migrate a product's form or other\ndomain architecture to match its own examples.\n\nUse deterministic tools directly and batch independent reads. Keep one writer\nper surface. Parallel workers are allowed only for disjoint paths with no\nshared dependency sequence. Start them from the same pinned contract and\nreceive completion events. Do not send repeated unchanged status requests or\npoll a worker when no new event or observation exists. Reuse a worker for a\nfocused correction while it owns the same surface; verify termination before\ntransferring ownership.\n\nEvery worker packet includes the exact root and branch or revision, owned\nsurface, settled routing, relevant references, constraints, focused checks,\nexpected receipt and known failures when resuming. Workers preserve unrelated\nedits and return changed paths, commands, results and remaining gaps. A clean\ndiff, first implementation or passing lint does not close unverified behavior.\n\n## Test changes and evidence gaps\n\nTreat tests as evidence for observable behavior. The default policy is\nallowedChanges = []: a worker does not add, modify, delete or generate a test\nfile unless the parent closes a reviewed policy exception first. Never create\none test per form or feature as a reflex. When a required behavior lacks\nevidence, report the actual gap and its smallest useful check to the parent;\nthe worker does not widen test scope on its own.\n\nWhen test files do change, the parent invokes the shared runtime policy helper:\nfindTestPolicyViolations({root, baseRef, policyPath:\n\"config\u002Ftest-change-policy.json\"}). It returns a violation array. An exception\nmust name each path, its SHA-256 (or null for an authorized deletion), the\nreason, issue and reviewed content. Do not hide a violation with a skipped\nassertion, ignore, disable or fake mock.\n\nChoose the quickest adequate existing check plus the checks named in the\ncontract. Preserve exit codes and rerun only after a relevant change, failure,\nrequired gate or unresolved risk. A test count or green run never substitutes\nfor the accepted objective.\n\n## UI acceptance and evidence\n\nFor visible work, resolve fixture identity, role, organization and useful\nentities once before the main pass. Give a neutral browser executor exact\naction inputs and the values to record; the parent retains the acceptance\nrubric and judges the resulting values. Use the authorized browser mechanism\nand one driver per session.\n\nWhen visual quality matters, complete Impeccable and independent capable\ncritique first, resolve material findings on this candidate, then call\nevidence-capture for final media. A screenshot or copied file proves neither\nlive harness influence nor product acceptance. Backend-only work does not need\na visual workflow.\n\n## Finish\n\nContinue through implementation, focused checks, corrections and the\nauthorized endpoint. Separate source, local runtime, PR, Preview, production\nand acceptance. Report the candidate, actual observed model\u002Ftool identity,\nchanged paths, checks, evidence references and remaining gaps. If blocked,\nname the concrete dependency and finish independent work; a timeout or missing\nreceipt cannot become a passing result.\n\nFor host-specific CLI dispatch, read [host-dispatch](references\u002Fhost-dispatch.md).\nFor interruption or ownership recovery, read\n[execution-continuity](references\u002Fexecution-continuity.md). T3 packet details\nare in [worker-reference](worker-reference.md).\n","# Coding orchestration\n\nOptimize rápido → bien → barato: reach the complete usable result quickly,\ncorrect it with focused evidence, and keep measured cost and complexity low.\nPreserve behavior, data boundaries and authorization.\n\n## Govern the full feature\n\nRead [Jev governed execution](references\u002Fjev-governance.md) once for non-trivial work. Keep the\nselected parent. Use fast research, Astra planning, a different fresh Astra\nplan review, bounded writers, independent deep review and actual behavior\nevidence. Jev supplies a required judgment at each lifecycle boundary; code\nenforces the applicable gate. Tiny unrelated deterministic work stays direct.\n\n## Resolve the run\n\nThe model selected when the conversation starts remains the orchestrator. It\nchooses workers within the user's provider, quota and capability limits and\nintegrates their results. A roster or native profile is a recommendation, not\nruntime identity or a provider chain. A restricted family stays restricted for\nevery descendant; report a missing browser or vision capability instead of\nsubstituting a different family.\n\nBefore a worker starts, pin one execution contract. It names the objective or\nticket, root and revision, owned paths, expected observable behavior, mode,\nauthorization and endpoint, enumerated checks, evidence receipt, stop\nconditions, and the required completion report. Read\n[the execution contract](references\u002Fexecution-contract.md) for the compact\npacket fields.\n\nUse **exact instructions by default**: give ordered actions, expected\nobservations, checks and stops using the execution contract. Outcome delegation\nis an explicit, reasoned exception for a bounded implementation decision; record\nwhy a recipe would be premature and keep the same acceptance requirements.\n\nThe method is model-agnostic. Preserve the acceptance standard when capability\nor availability changes: reduce packet size and simultaneous decisions, supply\nconcrete examples and observable checkpoints, then correct from the returned\nevidence. A model label never proves capability or acceptance. If an essential\ncapability is unavailable, retain the gap and continue independent work; do not\nsilently substitute a provider or promise equivalent results from every model.\n\n## Execute with useful ownership\n\nThe parent owns decomposition, architecture, integration, conflicts,\nverification, findings and the terminal state. The governance runtime constrains this parent; it does not replace it with another coordinator. Execute the repository's\nlocal canonical recipe; a skill does not migrate a product's form or other\ndomain architecture to match its own examples.\n\nUse deterministic tools directly and batch independent reads. Keep one writer\nper surface. Parallel workers are allowed only for disjoint paths with no\nshared dependency sequence. Start them from the same pinned contract and\nreceive completion events. Do not send repeated unchanged status requests or\npoll a worker when no new event or observation exists. Reuse a worker for a\nfocused correction while it owns the same surface; verify termination before\ntransferring ownership.\n\nEvery worker packet includes the exact root and branch or revision, owned\nsurface, settled routing, relevant references, constraints, focused checks,\nexpected receipt and known failures when resuming. Workers preserve unrelated\nedits and return changed paths, commands, results and remaining gaps. A clean\ndiff, first implementation or passing lint does not close unverified behavior.\n\n## Test changes and evidence gaps\n\nTreat tests as evidence for observable behavior. The default policy is\nallowedChanges = []: a worker does not add, modify, delete or generate a test\nfile unless the parent closes a reviewed policy exception first. Never create\none test per form or feature as a reflex. When a required behavior lacks\nevidence, report the actual gap and its smallest useful check to the parent;\nthe worker does not widen test scope on its own.\n\nWhen test files do change, the parent invokes the shared runtime policy helper:\nfindTestPolicyViolations({root, baseRef, policyPath:\n\"config\u002Ftest-change-policy.json\"}). It returns a violation array. An exception\nmust name each path, its SHA-256 (or null for an authorized deletion), the\nreason, issue and reviewed content. Do not hide a violation with a skipped\nassertion, ignore, disable or fake mock.\n\nChoose the quickest adequate existing check plus the checks named in the\ncontract. Preserve exit codes and rerun only after a relevant change, failure,\nrequired gate or unresolved risk. A test count or green run never substitutes\nfor the accepted objective.\n\n## UI acceptance and evidence\n\nFor visible work, resolve fixture identity, role, organization and useful\nentities once before the main pass. Give a neutral browser executor exact\naction inputs and the values to record; the parent retains the acceptance\nrubric and judges the resulting values. Use the authorized browser mechanism\nand one driver per session.\n\nWhen visual quality matters, complete Impeccable and independent capable\ncritique first, resolve material findings on this candidate, then call\nevidence-capture for final media. A screenshot or copied file proves neither\nlive harness influence nor product acceptance. Backend-only work does not need\na visual workflow.\n\n## Finish\n\nContinue through implementation, focused checks, corrections and the\nauthorized endpoint. Separate source, local runtime, PR, Preview, production\nand acceptance. Report the candidate, actual observed model\u002Ftool identity,\nchanged paths, checks, evidence references and remaining gaps. If blocked,\nname the concrete dependency and finish independent work; a timeout or missing\nreceipt cannot become a passing result.\n\nFor host-specific CLI dispatch, read [host-dispatch](references\u002Fhost-dispatch.md).\nFor interruption or ownership recovery, read\n[execution-continuity](references\u002Fexecution-continuity.md). T3 packet details\nare in [worker-reference](worker-reference.md).\n",{"name":5,"description":7},"main","9f5b43aadb1a92441d65e9cb74a584cd6fca62bc","artifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration","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 coding-orchestration",{"tool":38,"command":39},"bunx","bunx skills add AO-HyS\u002Fdevelopment-system --skill coding-orchestration",{"tool":41,"command":42},"pnpm","pnpm dlx skills add AO-HyS\u002Fdevelopment-system --skill coding-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002FSKILL.md",true,[46,52,56,60,64,68,72],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fexecution-continuity.md","REFERENCE","参考文档",3056,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002Freferences\u002Fexecution-continuity.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fexecution-contract.md",3478,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002Freferences\u002Fexecution-contract.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fhost-dispatch.md",2662,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002Freferences\u002Fhost-dispatch.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fjev-advisory.md",486,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002Freferences\u002Fjev-advisory.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fjev-governance.md",14594,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002Freferences\u002Fjev-governance.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fspec-ticket-contract.md",3262,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002Freferences\u002Fspec-ticket-contract.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"worker-reference.md",885,"https:\u002F\u002Fgithub.com\u002FAO-HyS\u002Fdevelopment-system\u002Fblob\u002Fmain\u002Fartifacts\u002F1.26.0\u002Fskills\u002Finternal\u002Fcoding-orchestration\u002Fworker-reference.md",[77,84,91,98,105,112],{"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},"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":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},"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":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},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"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",[],[]]