[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SFWY2ECHFSQR3N47YPT3X":3,"skill-same:01M71SFWY2ECHFSQR3N47YPT3X":44},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":25,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M71SFWY2ECHFSQR3N47YPT3X","planning",null,"Praneeth-Suresh\u002FBeryl","Praneeth-Suresh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F86470588?v=4","01M71SF2BCZ4JMKKYZR66WNHAF","Praneeth Suresh","01M71SF2C5JMS7B9676HSA2SG6",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fplanning\u002FSKILL.md",[],[5],"2026-11-10 13:02:02",false,"# Planning\n\n## Purpose\n\nTurn a requested change into a small, reviewable plan, get the user's approval,\nand then implement it within the approved scope.\n\n## Use When\n\n- The user asks for a plan, design, approach, or breakdown.\n- The user asks to add or change behavior and there is no approved plan yet.\n- The user has approved a plan and implementation is next.\n\n## Initial Build Handoff\n\nWhen the request explicitly describes a large or greenfield application, route to\n`.beryl\u002Fagent\u002Fskills\u002Finitial-build\u002FSKILL.md` instead of using this general planning\nworkflow. A request to plan an ordinary feature remains in this workflow. If an\nactive `.beryl\u002Fagent\u002Fhierarchy.md` exists, resume the initial-build workflow and\nimplement only a dependency-ready hierarchy node.\n\n## Plan\n\n1. Restate the requested outcome.\n2. Read only the canonical files needed for the relevant bounded context,\n   usually `.beryl\u002Fagent\u002Farchitecture.md`, `.beryl\u002Fagent\u002Fubiquitous-language.md`,\n   and `.beryl\u002Fagent\u002Ftesting-policy.md`.\n3. Identify the public interface, likely files, and checks that may change.\n4. If more than one implementation path is plausible, present the options and\n   wait for the user to choose, unless the user explicitly allowed you to choose.\n5. Define success checks: the expected file or artifact change, a narrow\n   command, a broader command, generated output or browser evidence when\n   applicable, and one user-visible behavior.\n6. Propose commit boundaries. Each one needs one purpose, the expected files,\n   and the check command that validates it.\n7. For risky or ambiguous work, run `grill-me` and fold the answers into the\n   plan.\n8. Present the plan, then stop. Do not edit implementation code until the user\n   approves it.\n\nFor non-trivial work, use these headings:\n\n```text\n## Implementation Paths\n## Acceptance Criteria\n## Commit Boundaries\n## Risks\n```\n\n## Implement\n\nAfter the user approves the plan:\n\n1. Implement one commit boundary at a time, behind the intended public\n   interface. Use `test-driven-development` for new behavior.\n2. Run the formatter if configured, then the narrow check, then the broader\n   check.\n3. If a check fails, use `systematic-debugging` and repair from the tool output.\n4. If the work changes scope, stop and return to the plan.\n5. Before saying the work is done, use `verification-before-completion`.\n6. When a durable decision, boundary, or term changed, update\n   `.beryl\u002Fagent\u002Farchitecture.md` or `.beryl\u002Fagent\u002Fubiquitous-language.md`.\n\n## Rules\n\n- Do not weaken tests to make implementation pass. Explain any intentional\n  test change.\n- Keep progress tracking out of canonical files.\n- Do not use sub-agents unless the user explicitly asks for them.\n\n## Final Response\n\nUse `communicating-with-users`. Include what changed, a map from changed files\nto commit boundaries (flag any file outside them), the checks that ran, the\nchecks that were skipped, and whether tests changed and why.\n",{},"main","3a5bd7e327cbdad81a70b624ec3fc6e43ec91f12",".beryl\u002Fagent\u002Fskills\u002Fplanning",0,"https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh","Just built it.","2026-11-09 18:59:34",{"source":7,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Praneeth-Suresh\u002FBeryl --skill planning",{"tool":36,"command":37},"bunx","bunx skills add Praneeth-Suresh\u002FBeryl --skill planning",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Praneeth-Suresh\u002FBeryl --skill planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fplanning\u002FSKILL.md",true,[],[45,70,77,110,135,150],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":49,"licenseFileUrl":50,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M71SGEFHAT82F5TQH73XY6H8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","MIT","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fverification-before-completion\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69],"verification","verification before completion","committing","commands","about","work","claims","output","evidence","when","assertions","use","claim","prs","complete","running",{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M71SGD1DV15B9Z2S5V3M8YPH","using-beryl","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fusing-beryl\u002FSKILL.md",[],[76],"using beryl",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":91,"publishedAt":18},"01M71SGAJ7D211GQR4703TTZCW","understand-codebase","Teach a developer how a repository, subsystem, execution path, migration, diff, commit, branch, or pull request works. Use when the user asks to understand, explain, map, walk through, explore, or quiz themselves on code, or asks for an interactive HTML understanding artifact.","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Funderstand-codebase\u002FSKILL.md",[83,88],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":89,"categoryName":90,"taxonomyType":86,"taxonomyTypeDesc":87},"01JBSEEDCAT000000000000039","教师与教育",[92,93,94,95,96,97,98,99,100,101,65,63,102,103,104,105,106,107,108,109],"understand","codebase","understand codebase","branch","diff","for","explore","execution","quiz","map","code","commit","interactive","explain","artifact","how","pull request","pull",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":49,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":125,"publishedAt":18},"01M71SG8H7CZGRND4C2BS49RV2","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Ftest-driven-development\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[117,122],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":123,"categoryName":124,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000018","写作与文案",[126,127,128,129,130,131,132,65,63,102,133,134],"driven","test","test driven development","development","feature","implementing","writing","bugfix","implementation",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":49,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":143,"publishedAt":18},"01M71SG4N855A3ASYXWFX45DH5","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fsystematic-debugging\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[142],{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},[144,145,146,147,65,63,127,148,149],"systematic","debugging","systematic debugging","fixes","behavior","bug",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":18},"01M71SG18JMNV8ED6XQ97Z48X0","simplifying-code","Use when code in a specific module or area is hard to understand or change, when the user asks to simplify, refactor, clean up, or improve the design or architecture of some code, or when a maintenance program hands over a refactor slice. Finds unmanaged complexity from evidence and removes it with small, behavior-preserving changes.","https:\u002F\u002Fgithub.com\u002FPraneeth-Suresh\u002FBeryl\u002Fblob\u002Fmain\u002F.beryl\u002Fagent\u002Fskills\u002Fsimplifying-code\u002FSKILL.md",[156],{"categoryNo":84,"categoryName":85,"taxonomyType":86,"taxonomyTypeDesc":87},[158,102,159,160,161,162,163,164,63,65,165,166,167,168,169,170,62,171,172,173],"simplifying code","design","change","with","architecture","program","simplify","module","changes","improve","clean","up","slice","complexity","behavior-preserving","maintenance"]