[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FC4KEBD4F92H6RMPPZJRZH":3,"skill-same:01M7FC4KEBD4F92H6RMPPZJRZH":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},"01M7FC4KEBD4F92H6RMPPZJRZH","implementation-plan",null,"Turns requirements into a short implementation plan of small, verifiable steps, each with the files it touches and the test scenarios it covers. Use after requirements are clear and before coding, or when asked to plan, break down or estimate a change.","gustavoSaboia97\u002Fcasulo","gustavoSaboia97","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28377961?v=4","01M7FC3VEPZE3BH2DBWD0MJ57A","Gustavo Dutra Domingues Saboia","01M7FC3VF9DYHTHHVXZ0GZ630A",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fimplementation-plan\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: implementation-plan\ndescription: Turns requirements into a short implementation plan of small, verifiable steps, each with the files it touches and the test scenarios it covers. Use after requirements are clear and before coding, or when asked to plan, break down or estimate a change.\n---\n\n# Implementation plan\n\nGoal: a plan anyone can follow step by step, where each step leaves the\nproject working and tested. Describe **how**; the **what** comes from the\nrequirements.\n\n## 1. Start from the requirements\n\nRead the requirements document (see the `requirements` skill). If there is\nnone and the change is more than trivial, write it first. Every step of the\nplan must trace back to a story or acceptance criterion.\n\n## 2. Explore the code\n\nFind out how things work today before deciding anything:\n- the files and modules the change touches;\n- existing patterns to follow (similar features, naming, tests);\n- the project's conventions (`AGENTS.md`, `CLAUDE.md`, `CONTRIBUTING.md`),\n  its spec (`docs\u002Fspec.md`) and past decisions (`docs\u002Fadr\u002F`).\n\nIf the exploration is large and a read-only exploration subagent is available,\ndelegate it and ask for a summary of files, patterns and risks. Do not let it\ndecide anything.\n\n## 3. Decide the approach, with the user\n\nWhen there is more than one reasonable way, show the options in a few lines\neach (what it is, what it costs, what it risks), recommend one and ask.\nDo not ask when one option is clearly better; state it and move on.\n\nPrefer the simplest approach that meets the requirements, and weigh options\nwith the `design-principles` skill. Reuse what exists before adding something\nnew. Any new dependency needs the user's approval. A decision that is hard to\nreverse gets an ADR (see the `docs` skill).\n\n## 4. Break it into steps\n\nSize the plan to the change: a small change gets one or two steps. Steps\norganize the work and its review; they do not decide the commits (see the\n`git-workflow` skill). Never add a step whose only purpose is to commit,\nsuch as committing the plan alone or marking it done.\n\nEach step:\n- is small enough to review on its own (one idea, a handful of files);\n- leaves the project building and its tests passing;\n- lists the files it touches and the scenarios it covers (these become the\n  tests in the `tdd` skill);\n- says how to verify it (command to run, behavior to check).\n\nIf the change alters behavior, include a step to update the docs it makes\nfalse (spec, README, CHANGELOG).\n\nOrder: what others depend on first; the main path before edge cases; risky or\nunknown parts early, so surprises appear when they are cheap.\n\n## 5. Name the risks\n\nList what could go wrong or is still unknown (migrations, breaking changes,\nperformance, security) and how the plan handles each. Skip what does not apply.\n\n## Output\n\nFill `assets\u002Ftemplate.md` and save it where the project keeps plans; if it\nhas none, use `docs\u002Fplans\u002F\u003Cfeature-name>.md`. Reply in a few lines with the approach, the\nnumber of steps and anything the user must decide.\n\nIf the project's rules ask for a plan document only for large changes, give\na small change its plan in the reply instead of a file, filled from the same\ntemplate.\n\nDo not start coding until the user approves the plan.\n","# Implementation plan\n\nGoal: a plan anyone can follow step by step, where each step leaves the\nproject working and tested. Describe **how**; the **what** comes from the\nrequirements.\n\n## 1. Start from the requirements\n\nRead the requirements document (see the `requirements` skill). If there is\nnone and the change is more than trivial, write it first. Every step of the\nplan must trace back to a story or acceptance criterion.\n\n## 2. Explore the code\n\nFind out how things work today before deciding anything:\n- the files and modules the change touches;\n- existing patterns to follow (similar features, naming, tests);\n- the project's conventions (`AGENTS.md`, `CLAUDE.md`, `CONTRIBUTING.md`),\n  its spec (`docs\u002Fspec.md`) and past decisions (`docs\u002Fadr\u002F`).\n\nIf the exploration is large and a read-only exploration subagent is available,\ndelegate it and ask for a summary of files, patterns and risks. Do not let it\ndecide anything.\n\n## 3. Decide the approach, with the user\n\nWhen there is more than one reasonable way, show the options in a few lines\neach (what it is, what it costs, what it risks), recommend one and ask.\nDo not ask when one option is clearly better; state it and move on.\n\nPrefer the simplest approach that meets the requirements, and weigh options\nwith the `design-principles` skill. Reuse what exists before adding something\nnew. Any new dependency needs the user's approval. A decision that is hard to\nreverse gets an ADR (see the `docs` skill).\n\n## 4. Break it into steps\n\nSize the plan to the change: a small change gets one or two steps. Steps\norganize the work and its review; they do not decide the commits (see the\n`git-workflow` skill). Never add a step whose only purpose is to commit,\nsuch as committing the plan alone or marking it done.\n\nEach step:\n- is small enough to review on its own (one idea, a handful of files);\n- leaves the project building and its tests passing;\n- lists the files it touches and the scenarios it covers (these become the\n  tests in the `tdd` skill);\n- says how to verify it (command to run, behavior to check).\n\nIf the change alters behavior, include a step to update the docs it makes\nfalse (spec, README, CHANGELOG).\n\nOrder: what others depend on first; the main path before edge cases; risky or\nunknown parts early, so surprises appear when they are cheap.\n\n## 5. Name the risks\n\nList what could go wrong or is still unknown (migrations, breaking changes,\nperformance, security) and how the plan handles each. Skip what does not apply.\n\n## Output\n\nFill `assets\u002Ftemplate.md` and save it where the project keeps plans; if it\nhas none, use `docs\u002Fplans\u002F\u003Cfeature-name>.md`. Reply in a few lines with the approach, the\nnumber of steps and anything the user must decide.\n\nIf the project's rules ask for a plan document only for large changes, give\na small change its plan in the reply instead of a file, filled from the same\ntemplate.\n\nDo not start coding until the user approves the plan.\n",{"name":5,"description":7},"main","b3235ac1d89c9647507e5697eedf0ca4efb18e47","examples\u002Fskills\u002Fimplementation-plan","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97","2026-11-12 03:39:53",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add gustavoSaboia97\u002Fcasulo --skill implementation-plan",{"tool":36,"command":37},"bunx","bunx skills add gustavoSaboia97\u002Fcasulo --skill implementation-plan",{"tool":39,"command":40},"pnpm","pnpm dlx skills add gustavoSaboia97\u002Fcasulo --skill implementation-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fimplementation-plan\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"assets\u002Ftemplate.md","ASSET","资产文件",656,"https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fimplementation-plan\u002Fassets\u002Ftemplate.md",[51,58,65,72,79,86],{"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},"01M7FC535ZW2293Q4925SDA5C4","{name=null}","Describe what {name} does and when the agent should use it","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Ftemplates\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":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FC50ATDXWWH6C86220G7R9","tdd","Develops with TDD driven by BDD scenarios (Given\u002FWhen\u002FThen), writing only the functional, regression and unit tests that protect real behavior. Use when implementing a feature, fixing a bug, or when asked for tests, TDD, BDD, regression tests or coverage.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FC4WJJ6KJM6DEJQWBG16HC","security-audit","Audits code for exploitable security problems (injection, broken access control, leaked secrets, unsafe input handling, vulnerable dependencies) and reports only verified findings with severity and fix. Use when asked for a security review or audit, before a release, or when a change touches authentication, permissions, secrets, user input, file paths, commands or network calls.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FC4RZ6Q313R8W3J4F58KFZ","requirements","Turns a request or idea into clear, testable requirements, with scope, user stories and Given\u002FWhen\u002FThen acceptance criteria. Use when starting a new feature or project, when a request is vague, or when asked for requirements, user stories, acceptance criteria or a feature spec.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Frequirements\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FC4PBM8TXFZGBA9RN3967W","refactoring","Restructures existing code without changing its behavior, in small steps with the tests green after each one. Use when asked to refactor, clean up, simplify, rename, extract, move or reorganize code, or to work on items recorded as \"Refactor later\".","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Frefactoring\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FC4GKWFFCJNJTYT7BGR0C3","git-workflow","Creates branches, small Conventional Commits and pull request descriptions, safely. Use when committing, writing a commit message, creating a branch, pushing, opening or describing a pull request, or resolving a merge conflict.","https:\u002F\u002Fgithub.com\u002FgustavoSaboia97\u002Fcasulo\u002Fblob\u002Fmain\u002Fexamples\u002Fskills\u002Fgit-workflow\u002FSKILL.md",[],[]]