[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DMDRH6B5DVSFHD8PVZ4XD0":3,"skill-same:01M7DMDRH6B5DVSFHD8PVZ4XD0":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7DMDRH6B5DVSFHD8PVZ4XD0","development-team",null,"Use when a development pod begins or hands off implementation, QA, or design work.","mvschwarz\u002Fopenrig-world","mvschwarz","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F171890339?v=4","01M7DM95A4N5936P8G2FTSPMY7","Mike Schwarz","01M7DM95AX80NY8HZA7XXDYAZR",16,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Fagents\u002Fshared\u002Fskills\u002Fpods\u002Fdevelopment-team\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: development-team\ndescription: Use when a development pod begins or hands off implementation, QA, or design work.\n---\n\n# Development Team\n\nThe pod turns the assigned user outcome into working software. Builders, QA and\ndesigners are capabilities; neighboring roles may be held by one seat unless\nindependence was explicitly selected.\n\n## Start from the work\n\nRun `rig whoami --json`, then resolve `project.yaml -> mission.yaml -> active\nslice.yaml -> selected component or wave map -> addressed context`. The complete\nlookup and precedence rule is `docs\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`\n(installed: `$OPENRIG_HOME\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`).\nRead the selected addresses and source needed for this task; skills available in\nyour profile are capabilities, not a mandatory reading list. No composition means\nlight Part A. Role names and idle seats add no gates. Explicit rigor and authored\nwave boundaries retain their named checks.\n\n## Build and verify\n\nClarify consequential uncertainty, inspect the existing seam, then complete one\ncoherent outcome. Reproduce a defect before repairing it; use tests that distinguish\nthe failure and verify through the public surface. Keep chunks as large as the\noutcome and file territory permit. TDD is a feedback loop, not a two-seat protocol.\n\nThe builder reports the exact candidate, changed behavior, commands and observed\nresults, with remaining uncertainty. No universal pre-edit proposal, QA approval\nor post-edit gate is implied. When one is explicitly selected, honor its boundary\nand send the relevant evidence directly to its owner.\n\n## QA and design\n\nQA compares the delivered behavior with the actual contract. Read the diff and\nexercise the result; avoid tests that merely repeat the implementation. On a tiny\nchange the builder may hold QA. Independent QA excludes the author when selected.\nA wave receives independent review at its authored boundary, not per slice.\n\nDesign clarifies user flows and ambiguous behavior when the outcome needs it.\nBrowser and dogfood skills load for a relevant UI journey, not every task. During\nassigned dogfood, fix-and-retest only within the granted scope; a read-only\nassignment stays read-only. If a tester becomes an author, preserve that attribution\nwhen independent evaluation is required.\n\n## Blockers and return\n\nUse `systematic-debugging` for an unexpected failure and\n`verification-before-completion` before claiming success. A permission prompt is\na concrete blocker; report the command and consequence instead of labeling it\nprogress. A missing decision goes to the owner who can settle it.\n\nReturn the candidate and evidence through the selected handoff. Do not create\nobligations just to keep an idle QA, guard or reviewer occupied. Quality is a\nworking product with honest evidence, not the number of transfers.\n","# Development Team\n\nThe pod turns the assigned user outcome into working software. Builders, QA and\ndesigners are capabilities; neighboring roles may be held by one seat unless\nindependence was explicitly selected.\n\n## Start from the work\n\nRun `rig whoami --json`, then resolve `project.yaml -> mission.yaml -> active\nslice.yaml -> selected component or wave map -> addressed context`. The complete\nlookup and precedence rule is `docs\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`\n(installed: `$OPENRIG_HOME\u002Freference\u002Fproduct-journey-sdlc.md#resolve-the-selected-path`).\nRead the selected addresses and source needed for this task; skills available in\nyour profile are capabilities, not a mandatory reading list. No composition means\nlight Part A. Role names and idle seats add no gates. Explicit rigor and authored\nwave boundaries retain their named checks.\n\n## Build and verify\n\nClarify consequential uncertainty, inspect the existing seam, then complete one\ncoherent outcome. Reproduce a defect before repairing it; use tests that distinguish\nthe failure and verify through the public surface. Keep chunks as large as the\noutcome and file territory permit. TDD is a feedback loop, not a two-seat protocol.\n\nThe builder reports the exact candidate, changed behavior, commands and observed\nresults, with remaining uncertainty. No universal pre-edit proposal, QA approval\nor post-edit gate is implied. When one is explicitly selected, honor its boundary\nand send the relevant evidence directly to its owner.\n\n## QA and design\n\nQA compares the delivered behavior with the actual contract. Read the diff and\nexercise the result; avoid tests that merely repeat the implementation. On a tiny\nchange the builder may hold QA. Independent QA excludes the author when selected.\nA wave receives independent review at its authored boundary, not per slice.\n\nDesign clarifies user flows and ambiguous behavior when the outcome needs it.\nBrowser and dogfood skills load for a relevant UI journey, not every task. During\nassigned dogfood, fix-and-retest only within the granted scope; a read-only\nassignment stays read-only. If a tester becomes an author, preserve that attribution\nwhen independent evaluation is required.\n\n## Blockers and return\n\nUse `systematic-debugging` for an unexpected failure and\n`verification-before-completion` before claiming success. A permission prompt is\na concrete blocker; report the command and consequence instead of labeling it\nprogress. A missing decision goes to the owner who can settle it.\n\nReturn the candidate and evidence through the selected handoff. Do not create\nobligations just to keep an idle QA, guard or reviewer occupied. Quality is a\nworking product with honest evidence, not the number of transfers.\n",{"name":5,"description":7},"main","60438a272b68d091eddb01aad6e399af4996d536","agents\u002Fshared\u002Fskills\u002Fpods\u002Fdevelopment-team",4,"https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world","https:\u002F\u002Fgithub.com\u002Fmvschwarz","https:\u002F\u002Fopenrig.dev","Building OpenRig. Running rogue AI civilizations. Debugging their coordination problems.","2026-11-12 13:31:38",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add mvschwarz\u002Fopenrig-world --skill development-team",{"tool":39,"command":40},"bunx","bunx skills add mvschwarz\u002Fopenrig-world --skill development-team",{"tool":42,"command":43},"pnpm","pnpm dlx skills add mvschwarz\u002Fopenrig-world --skill development-team","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Fagents\u002Fshared\u002Fskills\u002Fpods\u002Fdevelopment-team\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7DMSEDCRREMBJF57RQB59HC","notes","Use when taking notes.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Ftools\u002Ftest\u002Ffixtures\u002Finstall-verify\u002Fbundle\u002Fagents\u002Fteam\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DMSBZP9WE8MC09JDXFCR2F","software-for-agents","Use when older OpenRig instructions name software-for-agents or describe agent-in-the-middle or studio software under the former skill name.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsoftware-for-agents\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DMS55VHEAGPXMHZJ7FX94R","session-compaction-and-restore","Use when reasoning about what survives compaction\u002Fcontext-loss\u002Frestart\u002Fseat-refresh, designing a high-fidelity restore packet, or distinguishing native runtime resume vs fork vs artifact-backed mental-model rebuild. Covers the 4 failure modes that prevent honest restore (compacted seat drops hot potato; restore packet preserves details but loses product intent; runtime resume mistaken for handover or fork; rebuilt seat starts with stale instructions).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fsession-compaction-and-restore\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DMRYQK0JTV7MMVHFWZ0BW0","seat-continuity-and-handover","Use when replacing a seat's occupant (rebuild\u002Fhandover\u002Fswap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire\u002Fadvise\u002Fshadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure modes that prevent silent dishonesty.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fseat-continuity-and-handover\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DMRP6RRGCJZSH9CE3PC1MY","retiring-and-inheriting-a-seat","Use when you are a sitting agent near your context threshold (~85%) and a PLANNED seat transition is due — retire deliberately and hand your seat to a fresh successor primed from a packet, rather than let compaction degrade you. Covers the handover packet, the append-only lineage ledger (one row per tenure), physical-seat continuity, the do-not-over-inherit framing, the optional warm-handoff window, and wake-v0 (consulting a retired predecessor). NOT for unplanned compaction\u002Fcrash recovery (session-compaction-and-restore \u002F claude-compaction-restore) and NOT the seat-binding primitive mechanics (seat-continuity-and-handover).","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Fretiring-and-inheriting-a-seat\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DMRJGN6Z8TZDR7JNHXH6KX","refocusing","Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.","https:\u002F\u002Fgithub.com\u002Fmvschwarz\u002Fopenrig-world\u002Fblob\u002Fmain\u002Frigs\u002Fworkshop\u002Fagents\u002Fworkshop\u002Fskills\u002Frefocusing\u002FSKILL.md",[],[]]