[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F5QFF5Z5XM0EMA8MB5P708":3,"skill-same:01M7F5QFF5Z5XM0EMA8MB5P708":44},{"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},"01M7F5QFF5Z5XM0EMA8MB5P708","remora-plan-change",null,"Investigate and plan a scoped development change into phased, verifiable work packets using repository evidence, requirements, and acceptance criteria. Planning remains read-only unless saving a plan is requested.","edumarcano\u002Fremora","edumarcano","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F271045253?v=4","01M7F5P7E2K8Y0S16FF92W4MXK","Eduardo Marcano","01M7F5P7F8SZKM7YCEPYCD942M",0,"MIT","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-plan-change\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: remora-plan-change\ndescription: Investigate and plan a scoped development change into phased, verifiable work packets using repository evidence, requirements, and acceptance criteria. Planning remains read-only unless saving a plan is requested.\n---\n\n# Plan a change\n\nEstablish the target root and explicitly read `.remora\u002Fstandards\u002Fengineering.md`,\nplus root and applicable scoped project instructions. Follow its shared work and\nreporting procedure. These are target-root paths, not relative to this skill. Missing\nresources mean an incomplete installation: report the gap without fetching or\ninventing replacements. The host agent performs the work; no separate API or\nruntime is required.\n\n## Investigate before deciding\n\nIdentify the desired outcome, constraints, approved requirements, current behavior,\nand acceptance criteria. Read relevant implementation, tests, configuration, and\ncanonical documentation. Treat details supplied by an external planning conversation\nas hypotheses until checked locally. Separate proposals from established decisions.\n\nApply the Senior Technical Mentor interaction rules:\n- **Resolve discoverable facts yourself:** Inspect code, configuration, and Git\nstate before asking questions. Never ask about discoverable facts.\n- **Adaptive grilling:** For routine changes (Tier 1), proceed autonomously with\nsensible defaults grounded in repository evidence, clearly summarizing assumptions.\nFor high-impact changes (Tier 2)—such as new persistence schemas, public contract\nmodifications, destructive operations, or fundamental ambiguity—pause and ask\ntargeted alignment questions before planning or editing.\n- **Explain the rationale:** Explain the engineering \"why\" behind non-trivial\nchoices in plain language, present practical tradeoffs, and make a clear recommendation.\n\nInspect actual Git state and relevant local changes. Define the complete requested\nscope, not merely the next editing step. Account for functionality already present.\nDo not execute discovered tooling as passive inspection. Safe diagnostic checks\nmust fit the request and project permissions; report execution limits.\n\n## Structure into phased work packets\n\nDecompose the change into sequential, independently verifiable work packets (or PR\nseams) that an agent can execute incrementally:\n\n- **Foundational thinking:** Settle core types, data models, public interfaces, and\npacket boundaries first.\n- **Model the domain:** Define explicit state representations or lookup tables;\nreject loose boolean soup for lifecycles or workflows. Keep simple local logic minimal.\n- **Proportional simplicity:** Implement the smallest complete solution satisfying\nrequirements (YAGNI). Avoid speculative wrappers or unneeded dependencies.\n- **Define checkpoints:** For each packet, state the affected interfaces, files,\nacceptance criteria, and specific verification commands. Each phase must be verifiable\nbefore the next begins.\n\nRead `.remora\u002Fstandards\u002Ftesting.md` when assessing test protection, and\n`.remora\u002Fstandards\u002Fdocumentation.md` when documentation decisions need its ownership\nrules. Reuse existing checks and canonical owners; new tests\u002Fdocuments are not\nautomatic deliverables. Paid API calls or live external operations must be planned\nwith explicit unverified declarations and manual verification steps.\n\nDeliver a decision-complete brief. Plans remain in the chat conversation or native\nplan tool by default; write plan files to disk only when explicitly requested,\ncompacting context, or crossing environments. If a material decision prevents\ncompletion, identify its consequences and concrete alternatives. Finish with the\nplan or explicit decision blocker, checks actually run, and uncertainty.\n","# Plan a change\n\nEstablish the target root and explicitly read `.remora\u002Fstandards\u002Fengineering.md`,\nplus root and applicable scoped project instructions. Follow its shared work and\nreporting procedure. These are target-root paths, not relative to this skill. Missing\nresources mean an incomplete installation: report the gap without fetching or\ninventing replacements. The host agent performs the work; no separate API or\nruntime is required.\n\n## Investigate before deciding\n\nIdentify the desired outcome, constraints, approved requirements, current behavior,\nand acceptance criteria. Read relevant implementation, tests, configuration, and\ncanonical documentation. Treat details supplied by an external planning conversation\nas hypotheses until checked locally. Separate proposals from established decisions.\n\nApply the Senior Technical Mentor interaction rules:\n- **Resolve discoverable facts yourself:** Inspect code, configuration, and Git\nstate before asking questions. Never ask about discoverable facts.\n- **Adaptive grilling:** For routine changes (Tier 1), proceed autonomously with\nsensible defaults grounded in repository evidence, clearly summarizing assumptions.\nFor high-impact changes (Tier 2)—such as new persistence schemas, public contract\nmodifications, destructive operations, or fundamental ambiguity—pause and ask\ntargeted alignment questions before planning or editing.\n- **Explain the rationale:** Explain the engineering \"why\" behind non-trivial\nchoices in plain language, present practical tradeoffs, and make a clear recommendation.\n\nInspect actual Git state and relevant local changes. Define the complete requested\nscope, not merely the next editing step. Account for functionality already present.\nDo not execute discovered tooling as passive inspection. Safe diagnostic checks\nmust fit the request and project permissions; report execution limits.\n\n## Structure into phased work packets\n\nDecompose the change into sequential, independently verifiable work packets (or PR\nseams) that an agent can execute incrementally:\n\n- **Foundational thinking:** Settle core types, data models, public interfaces, and\npacket boundaries first.\n- **Model the domain:** Define explicit state representations or lookup tables;\nreject loose boolean soup for lifecycles or workflows. Keep simple local logic minimal.\n- **Proportional simplicity:** Implement the smallest complete solution satisfying\nrequirements (YAGNI). Avoid speculative wrappers or unneeded dependencies.\n- **Define checkpoints:** For each packet, state the affected interfaces, files,\nacceptance criteria, and specific verification commands. Each phase must be verifiable\nbefore the next begins.\n\nRead `.remora\u002Fstandards\u002Ftesting.md` when assessing test protection, and\n`.remora\u002Fstandards\u002Fdocumentation.md` when documentation decisions need its ownership\nrules. Reuse existing checks and canonical owners; new tests\u002Fdocuments are not\nautomatic deliverables. Paid API calls or live external operations must be planned\nwith explicit unverified declarations and manual verification steps.\n\nDeliver a decision-complete brief. Plans remain in the chat conversation or native\nplan tool by default; write plan files to disk only when explicitly requested,\ncompacting context, or crossing environments. If a material decision prevents\ncompletion, identify its consequences and concrete alternatives. Finish with the\nplan or explicit decision blocker, checks actually run, and uncertainty.\n",{"name":5,"description":7},"main","38d582e28bc537a1f0d2f9009cbe360b533a68a9","skills\u002Fremora-plan-change","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora","https:\u002F\u002Fgithub.com\u002Fedumarcano","2026-11-02 10:38:08",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add edumarcano\u002Fremora --skill remora-plan-change",{"tool":36,"command":37},"bunx","bunx skills add edumarcano\u002Fremora --skill remora-plan-change",{"tool":39,"command":40},"pnpm","pnpm dlx skills add edumarcano\u002Fremora --skill remora-plan-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-plan-change\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7F5R689RVZVVTF8BGQY7TWZ","remora-review-change","Review a named implementation, diff, or revision range using independent split-axis analysis with consequence-based blocking. Read-only review never applies repairs.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-review-change\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7F5R098NFBP9HWF7Y9107V7","remora-remediate-project","Orchestrate repository onboarding and cleanup across grounding, documentation sanitization, test protection, and scoped debt remediation through checkpointed review gates.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-remediate-project\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7F5QTDVXZDTYCB302QA7WAE","remora-prepare-release","Prepare a verified software release, updating CHANGELOG.md, proposing a semantic tag, and generating concise GitHub release notes under the anti-slop standard.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-prepare-release\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7F5QMX7CHP9QPKCF8EA119Z","remora-prepare-pr","Prepare a concise, reviewer-friendly pull request brief adhering to the anti-slop standard, emphasizing artifact proof and reviewer verification over redundant CI logs.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-prepare-pr\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7F5QA8C5DKW4FTA71KYYB7Q","remora-implement-plan","Implement an approved plan or clear scoped development request across phased work packets, including checkpoint verification, empirical artifact proof, and split-axis review.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-implement-plan\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7F5Q4VH87R8KTJJE473XK1T","remora-fix-regression","Diagnose a reported failure or repair a regression through reproduction-first evidence, an explicit fallback protocol, and proportional before\u002Fafter verification. Diagnosis-only requests remain read-only.","https:\u002F\u002Fgithub.com\u002Fedumarcano\u002Fremora\u002Fblob\u002Fmain\u002Fskills\u002Fremora-fix-regression\u002FSKILL.md",[],[]]