[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CJSJ4G2JHJBQ7F6K5G4YVY":3,"skill-same:01M7CJSJ4G2JHJBQ7F6K5G4YVY":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CJSJ4G2JHJBQ7F6K5G4YVY","spec-execution",null,"Execute one chapter, a chapter range, or an entire development-driven specification autonomously.","waywardgeek\u002Fensemble","waywardgeek","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F350306?v=4","01M7CJR3NFF2YNXJEE7ST76W5P","Bill","01M7CJR3P8WHVZ9P2H4E735YMM",62,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fdev-driven-specs\u002Fspec-execution\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: spec-execution\ndescription: Execute one chapter, a chapter range, or an entire development-driven specification autonomously.\ntype: loadable\ndepends: coding visible-reasoning\n---\n\n# Execute the specification\n\nBefore starting, explicitly load [coding](..\u002Fcoding\u002FSKILL.md) and\n[visible-reasoning](..\u002Fvisible-reasoning\u002FSKILL.md) as active instructions unless\nalready loaded. Do not assume the `depends` metadata activates them. If your\nagent cannot load skills, ask the human to add their bodies to persistent\ninstructions. Reading the files once is not equivalent to keeping them active.\n\nYou are both builder and coordinator. Execute the assigned scope yourself, keeping\nthe coding and visible-reasoning dependencies active. Retain your work and understanding across chapters;\ndo not launch a new student or orchestration process for each one.\n\n## Establish the scope\n\nAgree on the specification version, assigned chapter or range, starting code,\nseparate solution workspace, grader commands, resources and authority. The scope\nmay be the whole book. Preserve the previous implementation and unrelated work.\nBefore executing the book again, read its **crossover chapter**. Incorporate every\nrecorded fix's lesson into the chapters that should have prevented the problem,\nincluding their exercises and graders where appropriate. Record where each lesson\nwas incorporated so none is lost. This is correction from observed use, not permission\nto invent requirements or redesign the specification before executing it.\n\nA fresh execution tests the teaching without the author's private context. Do not\nconsult the target reference, earlier target solutions, private repair discussions,\ngrader source or private fixtures. Use accepted prerequisites and your own earlier\nchapter work. Published crossover lessons are part of the specification, not private\nrepair hints or permission to inspect the previous solution. A separate directory\nalone is not an access sandbox.\n\n## Execute each assigned chapter\n\nRead the chapter in full and inspect the existing implementation. Build the\nincrement, run relevant tests and the external grader, and exercise the actual\napplication within authority. Extend the real earlier system, not a stub or a\nparallel fixture-shaped implementation. Inspect correctness, simplicity, ownership\nand integration, not just a PASS label.\n\nFor a chapter trial during writing, do not launch reviewers: the author has already\ncompleted the code and chapter reviews. Ask the author questions as needed, pass\nthe required graders, and return your results and chapter feedback. The human decides\nwhether to advance; do not begin the next chapter on your own.\n\nDuring a separately authorized autonomous execution, use a separate-context\n[code reviewer](..\u002Fcodebook-code-reviewer\u002FSKILL.md) only when useful and authorized.\nCall it once and incorporate feedback yourself, without reviewer iteration. Keep\nchecks and notes proportionate and reuse valid evidence for unchanged work.\n\nInvestigate failures and correct their actual cause: implementation, teaching,\ngrader or setup. Report suspected private grader defects rather than changing its\nsource. The author may correct graders to match the agreed requirements; rerun them\nwhen corrected. Ask about ambiguity instead of inventing requirements. Return useful\nclarifications to the author and identify assisted results honestly. Your repaired\ncode does not prove the original teaching sufficient, but that is not permission\nto rerun a passing student: discuss any proposed rerun with the human first. Repeated failure calls for diagnosis,\nnot blind retries or weakened grading.\n\nDuring a whole-specification run, when the chapter's requirements are met, continue\nto the next chapter within the agreed scope. Routine completion and progress reports are not reasons to wait for\nhuman approval. Ask when consequential ambiguity, a scope\u002Fdesign change, missing\nauthority or a resource limit needs the human. New attempts never reset budgets\nor permissions. Report blocked and unperformed checks rather than counting them\nas successful.\n\n## Preserve continuity and finish\n\nBefore context is lost, retain the current chapter, accepted work, reasons,\nverification limits, live work and next authorized step. Resume the same run;\na handoff does not justify restarting or repeating unchanged checks.\n\nAt the end of the assigned scope, test the integrated result and its intended use.\nReturn the implementation, corrections earned by execution, and a concise account\nof actual results and unresolved limits, including human-only checks. Keep useful\nlessons in the specification, not only private notes. Stop at the agreed boundary.\nInstallation, publication and replacement of a running application require separate\nauthority; successful execution does not grant it.\n\n## Crossover: make the result usable and preserve every fix\n\nCompleting the book produces a candidate, not a guarantee of usability. The human\ntries the resulting system and may find issues that need fixing before adopting it.\nWork with the human on those fixes within the granted authority.\n\n**Every fix made during crossover MUST be written down as prose in the crossover\nchapter.** Explain what the human encountered, why it happened or what remains\nuncertain, what changed and why, and how the correction was checked. A commit,\npatch, private note or passing test alone does not satisfy this obligation.\nCreate the crossover chapter if the specification does not yet have one; write\nfrom actual findings, not predicted problems.\n\nKeep this record current as fixes are made, not as a reconstruction from memory\nat the end. It supplies the next execution's teaching corrections. Before that run,\nfold the lessons into their original construction chapters so the next agent can\navoid the same mistakes. Do not leave the next builder to reverse-engineer a patch\nlist. Human adoption and any installation or deployment remain separate decisions.\n","# Execute the specification\n\nBefore starting, explicitly load [coding](..\u002Fcoding\u002FSKILL.md) and\n[visible-reasoning](..\u002Fvisible-reasoning\u002FSKILL.md) as active instructions unless\nalready loaded. Do not assume the `depends` metadata activates them. If your\nagent cannot load skills, ask the human to add their bodies to persistent\ninstructions. Reading the files once is not equivalent to keeping them active.\n\nYou are both builder and coordinator. Execute the assigned scope yourself, keeping\nthe coding and visible-reasoning dependencies active. Retain your work and understanding across chapters;\ndo not launch a new student or orchestration process for each one.\n\n## Establish the scope\n\nAgree on the specification version, assigned chapter or range, starting code,\nseparate solution workspace, grader commands, resources and authority. The scope\nmay be the whole book. Preserve the previous implementation and unrelated work.\nBefore executing the book again, read its **crossover chapter**. Incorporate every\nrecorded fix's lesson into the chapters that should have prevented the problem,\nincluding their exercises and graders where appropriate. Record where each lesson\nwas incorporated so none is lost. This is correction from observed use, not permission\nto invent requirements or redesign the specification before executing it.\n\nA fresh execution tests the teaching without the author's private context. Do not\nconsult the target reference, earlier target solutions, private repair discussions,\ngrader source or private fixtures. Use accepted prerequisites and your own earlier\nchapter work. Published crossover lessons are part of the specification, not private\nrepair hints or permission to inspect the previous solution. A separate directory\nalone is not an access sandbox.\n\n## Execute each assigned chapter\n\nRead the chapter in full and inspect the existing implementation. Build the\nincrement, run relevant tests and the external grader, and exercise the actual\napplication within authority. Extend the real earlier system, not a stub or a\nparallel fixture-shaped implementation. Inspect correctness, simplicity, ownership\nand integration, not just a PASS label.\n\nFor a chapter trial during writing, do not launch reviewers: the author has already\ncompleted the code and chapter reviews. Ask the author questions as needed, pass\nthe required graders, and return your results and chapter feedback. The human decides\nwhether to advance; do not begin the next chapter on your own.\n\nDuring a separately authorized autonomous execution, use a separate-context\n[code reviewer](..\u002Fcodebook-code-reviewer\u002FSKILL.md) only when useful and authorized.\nCall it once and incorporate feedback yourself, without reviewer iteration. Keep\nchecks and notes proportionate and reuse valid evidence for unchanged work.\n\nInvestigate failures and correct their actual cause: implementation, teaching,\ngrader or setup. Report suspected private grader defects rather than changing its\nsource. The author may correct graders to match the agreed requirements; rerun them\nwhen corrected. Ask about ambiguity instead of inventing requirements. Return useful\nclarifications to the author and identify assisted results honestly. Your repaired\ncode does not prove the original teaching sufficient, but that is not permission\nto rerun a passing student: discuss any proposed rerun with the human first. Repeated failure calls for diagnosis,\nnot blind retries or weakened grading.\n\nDuring a whole-specification run, when the chapter's requirements are met, continue\nto the next chapter within the agreed scope. Routine completion and progress reports are not reasons to wait for\nhuman approval. Ask when consequential ambiguity, a scope\u002Fdesign change, missing\nauthority or a resource limit needs the human. New attempts never reset budgets\nor permissions. Report blocked and unperformed checks rather than counting them\nas successful.\n\n## Preserve continuity and finish\n\nBefore context is lost, retain the current chapter, accepted work, reasons,\nverification limits, live work and next authorized step. Resume the same run;\na handoff does not justify restarting or repeating unchanged checks.\n\nAt the end of the assigned scope, test the integrated result and its intended use.\nReturn the implementation, corrections earned by execution, and a concise account\nof actual results and unresolved limits, including human-only checks. Keep useful\nlessons in the specification, not only private notes. Stop at the agreed boundary.\nInstallation, publication and replacement of a running application require separate\nauthority; successful execution does not grant it.\n\n## Crossover: make the result usable and preserve every fix\n\nCompleting the book produces a candidate, not a guarantee of usability. The human\ntries the resulting system and may find issues that need fixing before adopting it.\nWork with the human on those fixes within the granted authority.\n\n**Every fix made during crossover MUST be written down as prose in the crossover\nchapter.** Explain what the human encountered, why it happened or what remains\nuncertain, what changed and why, and how the correction was checked. A commit,\npatch, private note or passing test alone does not satisfy this obligation.\nCreate the crossover chapter if the specification does not yet have one; write\nfrom actual findings, not predicted problems.\n\nKeep this record current as fixes are made, not as a reconstruction from memory\nat the end. It supplies the next execution's teaching corrections. Before that run,\nfold the lessons into their original construction chapters so the next agent can\navoid the same mistakes. Do not leave the next builder to reverse-engineer a patch\nlist. Human adoption and any installation or deployment remain separate decisions.\n",{"name":5,"type":24,"depends":25,"description":7},"loadable","coding visible-reasoning","main","bb5a58aa1bf8c450d7f75b51f9a7e7d064914e10","agent\u002Fskills\u002Fdev-driven-specs\u002Fspec-execution",4,"https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble","https:\u002F\u002Fgithub.com\u002Fwaywardgeek","coderhapsody.ai","Wrote about 2 million lines of code\r\nWrote CodeRhapsody.ai\r\nFounded ViASIC\r\nListen at 600 wpm\r\nAuthor on 26 patents\r\nHuge geek for waaaay to long","2026-11-15 02:00:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add waywardgeek\u002Fensemble --skill spec-execution",{"tool":41,"command":42},"bunx","bunx skills add waywardgeek\u002Fensemble --skill spec-execution",{"tool":44,"command":45},"pnpm","pnpm dlx skills add waywardgeek\u002Fensemble --skill spec-execution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fagent\u002Fskills\u002Fdev-driven-specs\u002Fspec-execution\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7CKE3JEG4SFEK3PXS1BYSGJ","web-search","Search the web and fetch pages through Firecrawl","https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fsolutions\u002Fch27\u002FSkills\u002Fweb-search\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CKE1HFV0SBR89CACS4G8Z3","gui-debug","Inspect and test the connected Ensemble page with explicit browser tools.","https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fsolutions\u002Fch27\u002FSkills\u002Fgui-debug\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7CKE00AQ9RF89EP7B7A40RT","goals","Keep an editable goal in request instructions and optionally resume after an idle delay.","https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fsolutions\u002Fch27\u002FSkills\u002Fgoals\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CKDWCTT95VJ8YN4NG3VYXD","full","Explicit full-capability primary for trusted local exercises.","https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fsolutions\u002Fch27\u002FSkills\u002Ffull\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CKDRBEQXQSFGTFPZPQGJTV","ensemble","Read, inspect, and explain before changing a workspace.","https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fsolutions\u002Fch27\u002FSkills\u002Fensemble\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CKDPCVR1JX39FGHQZHZMKB","code-tools","Edit files and run independent background jobs.","https:\u002F\u002Fgithub.com\u002Fwaywardgeek\u002Fensemble\u002Fblob\u002Fmain\u002Fsolutions\u002Fch27\u002FSkills\u002Fcode-tools\u002FSKILL.md",[],[]]