[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P5EDTNN6KNT571VCGKWTC4":3,"skill-same:01M6P5EDTNN6KNT571VCGKWTC4":95},{"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":26,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":73,"commitSha":74,"skillDirectory":75,"forksCount":76,"repositoryHtmlUrl":77,"repositoryHomepageUrl":6,"ownerHtmlUrl":78,"ownerBlogUrl":79,"ownerDescription":6,"updatedAt":80,"install":81,"resources":94},"01M6P5EDTNN6KNT571VCGKWTC4","retrospective",null,"Produces a Retrospective Document with structured reflection (what went well, what was hard, what to change) and seeds for the memory garden. Use when: 'do a retrospective', 'what did we learn from this sprint', 'reflect on this release', 'harvest the learnings', 'what went well and what was hard'.","DojoGenesis\u002Fgateway","DojoGenesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273886418?v=4","01M6P54RXMD3TZ2082Z3Z4JMQP","Cruz Morales (TresPies)","01M6P54S269YR0ZZZ96WGQM439",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fcontinuous-learning\u002Fskills\u002Fretrospective\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[5,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"use","for","opus","STRING","sprint","false","learnings","do","document","reflection","memory","session","context","system","learning","release","learn","reflect","change","2026-11-10 10:12:30",false,"---\nname: retrospective\nmodel: opus\ndescription: \"Produces a Retrospective Document with structured reflection (what went well, what was hard, what to change) and seeds for the memory garden. Use when: 'do a retrospective', 'what did we learn from this sprint', 'reflect on this release', 'harvest the learnings', 'what went well and what was hard'.\"\ncategory: continuous-learning\ntriggers:\n  - \"do a retrospective\"\n  - \"what did we learn from this sprint\"\n  - \"reflect on this release\"\n  - \"harvest the learnings\"\n  - \"what went well and what was hard\"\ntier: 1\nagents:\n  - \"primary\"\ntool_dependencies:\n  - \"file_system\"\n\ninputs:\n  - name: context\n    type: string\n    description: Description of the sprint, release, or session to reflect on\n    required: false\noutputs:\n  - name: retrospective_document\n    type: ref\n    format: cas-ref\n    description: Retrospective Document with structured reflection (what went well, what was hard, what to change) and memory garden seeds\n---\n\n# Retrospective Skill\n\n**Version:** 1.0  \n**Created:** 2026-02-04  \n**Author:** Manus AI  \n**Purpose:** To provide a structured, repeatable process for conducting sprint retrospectives, harvesting learnings, and feeding them back into our collaborative practice.\n\n---\n\n## I. The Philosophy of the Harvest\n\nA retrospective is not a post-mortem. It is not about blame or judgment. It is a **harvest**. After a season of hard work, we pause to gather the fruits of our labor—not just the features we shipped, but the wisdom we gained in the process. It is a practice of gratitude, honesty, and a commitment to continuous learning.\n\nThis skill turns the informal act of looking back into a formal ritual, ensuring that the valuable lessons from each sprint are not lost, but are instead integrated into our shared memory and future workflows.\n\n---\n\n## II. When to Use This Skill\n\n-   **After a major release:** (e.g., after Dojo Genesis v0.0.25 is fully shipped)\n-   **After a significant milestone:** (e.g., after completing a major refactor)\n-   **When a project feels stuck or has encountered significant friction.**\n-   **At regular intervals** (e.g., monthly) to maintain a cadence of reflection.\n\n---\n\n## III. The Retrospective Workflow\n\n### Step 1: Initiate the Retrospective\n\nWhen a trigger event occurs, state the intention to conduct a retrospective. Frame it as a positive and necessary part of the workflow.\n\n**Example:** \"Now that v0.0.25 is shipped, let's conduct a retrospective to harvest the learnings from this sprint. I'll use the Retrospective skill to guide us.\"\n\n### Step 2: Create the Retrospective Document\n\nCreate a new markdown file in the relevant project's `docs\u002Fretrospectives\u002F` directory (e.g., `\u002Fhome\u002Fubuntu\u002Fdojo-genesis\u002Fdocs\u002Fretrospectives\u002Fv0.0.25_retrospective.md`). Use the template provided in Section IV of this skill.\n\n### Step 3: Answer the Three Core Questions\n\nCollaboratively, answer the three core questions of the retrospective. This should be a brainstorming phase. Capture all thoughts without judgment.\n\n1.  **What went well?** (What should we amplify?)\n2.  **What was hard?** (What were the sources of friction or difficulty?)\n3.  **What would we do differently next time?** (What are the concrete, actionable changes we can make?)\n\n### Step 4: Synthesize and Extract Learnings\n\nAnalyze the answers to the three questions and synthesize them into key themes and actionable insights. This is the most critical step.\n\n-   **Identify Patterns:** Look for recurring themes across the different answers.\n-   **Distill Actionable Insights:** For each theme, identify a concrete action that can be taken to improve the workflow.\n-   **Create Seeds for the Memory Garden:** If a lesson is particularly profound or reusable, distill it into a Dojo Seed.\n\n### Step 5: Commit and Share\n\nCommit the completed retrospective document to the repository. Share the key findings and action items to ensure they are integrated into the next sprint's planning.\n\n---\n\n## IV. Retrospective Document Template\n\n```markdown\n# Retrospective: [Sprint\u002FRelease Name]\n\n**Date:** [Date]\n**Participants:** [e.g., Cruz, Manus]\n**Context:** A reflection on the [Sprint\u002FRelease Name] sprint, which focused on [brief description of the sprint's goals].\n\n---\n\n## 1. The Three Core Questions\n\n### What Went Well?\n\n- *[Observation 1]*\n- *[Observation 2]*\n- *[Observation 3]*\n\n### What Was Hard?\n\n- *[Friction Point 1]*\n- *[Friction Point 2]*\n- *[Friction Point 3]*\n\n### What Would We Do Differently Next Time?\n\n- *[Actionable Suggestion 1]*\n- *[Actionable Suggestion 2]*\n- *[Actionable Suggestion 3]*\n\n---\n\n## 2. Key Themes & Insights\n\n| Theme | Analysis | Action Item |\n| :--- | :--- | :--- |\n| **[Theme 1]** | [A summary of the observations related to this theme.] | [A concrete action to be taken in the next sprint.] |\n| **[Theme 2]** | [A summary of the observations related to this theme.] | [A concrete action to be taken in the next sprint.] |\n| **[Theme 3]** | [A summary of the observations related to this theme.] | [A concrete action to be taken in the next sprint.] |\n\n---\n\n## 3. Seeds for the Memory Garden\n\n-   **Seed:** [Seed Name] — *Why it matters:* [Explanation] — *Revisit trigger:* [When to remember this lesson]\n\n---\n\n## 4. Closing\n\n[A brief closing statement summarizing the key takeaway from the retrospective and expressing gratitude for the practice.]\n```\n\n---\n\n## V. Best Practices\n\n-   **Be Honest and Gentle:** The goal is learning, not blame.\n-   **Focus on Process, Not People:** Analyze the workflow, not the individuals.\n-   **Be Specific and Concrete:** Avoid vague statements. Use specific examples.\n-   **End with Action:** Every retrospective should result in at least one concrete action item for the next sprint.\n-   **Keep it Lightweight:** The process should feel energizing, not burdensome.\n\n---\n\n## Output\n\n- A Retrospective Document saved to the project's `docs\u002Fretrospectives\u002F` directory\n- Named: `[sprint-or-release-name]_retrospective.md`\n- Sections: Three Core Questions, Key Themes and Insights table, Seeds for Memory Garden, Closing\n- At least one Action Item per theme that enters the next sprint's planning\n\n---\n\n## Examples\n\n**Scenario 1:** \"Do a retrospective on v0.3 ship\" → Retrospective Document with What Went Well \u002F What Was Hard \u002F What Would We Do Differently, 3 themes with action items, and 1-2 memory garden seeds from the most reusable lessons\n\n**Scenario 2:** \"The project feels stuck, let's reflect\" → Retrospective triggered mid-sprint, identifies friction source (a recurring integration bottleneck), synthesizes into an action item to fix the integration pattern, and seeds a lesson about early integration testing\n\n---\n\n## Edge Cases\n\n- **Solo retrospective (no collaborators):** Run the three questions as a self-interview; treat your own perspective as a single data point and note where additional perspectives would change the synthesis\n- **Retrospective immediately after a failure or conflict:** Lead with the \"What Went Well\" section first to establish psychological safety before surfacing friction\n- **Too many themes identified (6+):** Cluster into 3 parent themes; sub-themes belong inside those clusters, not as separate rows\n\n---\n\n## Anti-Patterns\n\n- Conducting a retrospective during a crisis or before the sprint is complete — retrospective requires a closed period to reflect on, not an open one\n- Producing only a list of complaints without action items — every friction point must map to a concrete next step\n- Conflating \"what was hard\" with \"who was at fault\" — retrospectives analyze process, never individuals\n- Skipping the Seeds section when a lesson is particularly reusable — the seeds are how retrospective learning transfers to future sprints\n","# Retrospective Skill\n\n**Version:** 1.0  \n**Created:** 2026-02-04  \n**Author:** Manus AI  \n**Purpose:** To provide a structured, repeatable process for conducting sprint retrospectives, harvesting learnings, and feeding them back into our collaborative practice.\n\n---\n\n## I. The Philosophy of the Harvest\n\nA retrospective is not a post-mortem. It is not about blame or judgment. It is a **harvest**. After a season of hard work, we pause to gather the fruits of our labor—not just the features we shipped, but the wisdom we gained in the process. It is a practice of gratitude, honesty, and a commitment to continuous learning.\n\nThis skill turns the informal act of looking back into a formal ritual, ensuring that the valuable lessons from each sprint are not lost, but are instead integrated into our shared memory and future workflows.\n\n---\n\n## II. When to Use This Skill\n\n-   **After a major release:** (e.g., after Dojo Genesis v0.0.25 is fully shipped)\n-   **After a significant milestone:** (e.g., after completing a major refactor)\n-   **When a project feels stuck or has encountered significant friction.**\n-   **At regular intervals** (e.g., monthly) to maintain a cadence of reflection.\n\n---\n\n## III. The Retrospective Workflow\n\n### Step 1: Initiate the Retrospective\n\nWhen a trigger event occurs, state the intention to conduct a retrospective. Frame it as a positive and necessary part of the workflow.\n\n**Example:** \"Now that v0.0.25 is shipped, let's conduct a retrospective to harvest the learnings from this sprint. I'll use the Retrospective skill to guide us.\"\n\n### Step 2: Create the Retrospective Document\n\nCreate a new markdown file in the relevant project's `docs\u002Fretrospectives\u002F` directory (e.g., `\u002Fhome\u002Fubuntu\u002Fdojo-genesis\u002Fdocs\u002Fretrospectives\u002Fv0.0.25_retrospective.md`). Use the template provided in Section IV of this skill.\n\n### Step 3: Answer the Three Core Questions\n\nCollaboratively, answer the three core questions of the retrospective. This should be a brainstorming phase. Capture all thoughts without judgment.\n\n1.  **What went well?** (What should we amplify?)\n2.  **What was hard?** (What were the sources of friction or difficulty?)\n3.  **What would we do differently next time?** (What are the concrete, actionable changes we can make?)\n\n### Step 4: Synthesize and Extract Learnings\n\nAnalyze the answers to the three questions and synthesize them into key themes and actionable insights. This is the most critical step.\n\n-   **Identify Patterns:** Look for recurring themes across the different answers.\n-   **Distill Actionable Insights:** For each theme, identify a concrete action that can be taken to improve the workflow.\n-   **Create Seeds for the Memory Garden:** If a lesson is particularly profound or reusable, distill it into a Dojo Seed.\n\n### Step 5: Commit and Share\n\nCommit the completed retrospective document to the repository. Share the key findings and action items to ensure they are integrated into the next sprint's planning.\n\n---\n\n## IV. Retrospective Document Template\n\n```markdown\n# Retrospective: [Sprint\u002FRelease Name]\n\n**Date:** [Date]\n**Participants:** [e.g., Cruz, Manus]\n**Context:** A reflection on the [Sprint\u002FRelease Name] sprint, which focused on [brief description of the sprint's goals].\n\n---\n\n## 1. The Three Core Questions\n\n### What Went Well?\n\n- *[Observation 1]*\n- *[Observation 2]*\n- *[Observation 3]*\n\n### What Was Hard?\n\n- *[Friction Point 1]*\n- *[Friction Point 2]*\n- *[Friction Point 3]*\n\n### What Would We Do Differently Next Time?\n\n- *[Actionable Suggestion 1]*\n- *[Actionable Suggestion 2]*\n- *[Actionable Suggestion 3]*\n\n---\n\n## 2. Key Themes & Insights\n\n| Theme | Analysis | Action Item |\n| :--- | :--- | :--- |\n| **[Theme 1]** | [A summary of the observations related to this theme.] | [A concrete action to be taken in the next sprint.] |\n| **[Theme 2]** | [A summary of the observations related to this theme.] | [A concrete action to be taken in the next sprint.] |\n| **[Theme 3]** | [A summary of the observations related to this theme.] | [A concrete action to be taken in the next sprint.] |\n\n---\n\n## 3. Seeds for the Memory Garden\n\n-   **Seed:** [Seed Name] — *Why it matters:* [Explanation] — *Revisit trigger:* [When to remember this lesson]\n\n---\n\n## 4. Closing\n\n[A brief closing statement summarizing the key takeaway from the retrospective and expressing gratitude for the practice.]\n```\n\n---\n\n## V. Best Practices\n\n-   **Be Honest and Gentle:** The goal is learning, not blame.\n-   **Focus on Process, Not People:** Analyze the workflow, not the individuals.\n-   **Be Specific and Concrete:** Avoid vague statements. Use specific examples.\n-   **End with Action:** Every retrospective should result in at least one concrete action item for the next sprint.\n-   **Keep it Lightweight:** The process should feel energizing, not burdensome.\n\n---\n\n## Output\n\n- A Retrospective Document saved to the project's `docs\u002Fretrospectives\u002F` directory\n- Named: `[sprint-or-release-name]_retrospective.md`\n- Sections: Three Core Questions, Key Themes and Insights table, Seeds for Memory Garden, Closing\n- At least one Action Item per theme that enters the next sprint's planning\n\n---\n\n## Examples\n\n**Scenario 1:** \"Do a retrospective on v0.3 ship\" → Retrospective Document with What Went Well \u002F What Was Hard \u002F What Would We Do Differently, 3 themes with action items, and 1-2 memory garden seeds from the most reusable lessons\n\n**Scenario 2:** \"The project feels stuck, let's reflect\" → Retrospective triggered mid-sprint, identifies friction source (a recurring integration bottleneck), synthesizes into an action item to fix the integration pattern, and seeds a lesson about early integration testing\n\n---\n\n## Edge Cases\n\n- **Solo retrospective (no collaborators):** Run the three questions as a self-interview; treat your own perspective as a single data point and note where additional perspectives would change the synthesis\n- **Retrospective immediately after a failure or conflict:** Lead with the \"What Went Well\" section first to establish psychological safety before surfacing friction\n- **Too many themes identified (6+):** Cluster into 3 parent themes; sub-themes belong inside those clusters, not as separate rows\n\n---\n\n## Anti-Patterns\n\n- Conducting a retrospective during a crisis or before the sprint is complete — retrospective requires a closed period to reflect on, not an open one\n- Producing only a list of complaints without action items — every friction point must map to a concrete next step\n- Conflating \"what was hard\" with \"who was at fault\" — retrospectives analyze process, never individuals\n- Skipping the Seeds section when a lesson is particularly reusable — the seeds are how retrospective learning transfers to future sprints\n",{"name":5,"tier":51,"model":29,"agents":52,"inputs":54,"outputs":58,"category":64,"triggers":65,"description":7,"tool_dependencies":71},1,[53],"primary",[55],{"name":39,"type":56,"required":47,"description":57},"string","Description of the sprint, release, or session to reflect on",[59],{"name":60,"type":61,"format":62,"description":63},"retrospective_document","ref","cas-ref","Retrospective Document with structured reflection (what went well, what was hard, what to change) and memory garden seeds","continuous-learning",[66,67,68,69,70],"do a retrospective","what did we learn from this sprint","reflect on this release","harvest the learnings","what went well and what was hard",[72],"file_system","main","ff07df5fd8f75762c2a131e6e26d297e8ae403ee","plugins\u002Fcontinuous-learning\u002Fskills\u002Fretrospective",0,"https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway","https:\u002F\u002Fgithub.com\u002FDojoGenesis","dojogenesis.com","2026-10-25 22:59:58",{"source":8,"skillName":5,"commands":82,"prompt":92,"zipAvailable":93},[83,86,89],{"tool":84,"command":85},"npx","npx skills add DojoGenesis\u002Fgateway --skill retrospective",{"tool":87,"command":88},"bunx","bunx skills add DojoGenesis\u002Fgateway --skill retrospective",{"tool":90,"command":91},"pnpm","pnpm dlx skills add DojoGenesis\u002Fgateway --skill retrospective","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fcontinuous-learning\u002Fskills\u002Fretrospective\u002FSKILL.md",true,[],[96,115,126,134,174,199],{"skillNo":97,"name":98,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":104,"publishedAt":46},"01M6P6J0WYSD1MTGA3ZX6MGGZ5","kata-test-echo","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-test-echo\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[105,106,107,108,109,110,111,112,113,114],"kata test echo","Echo","test","json","v1","output","input","structured","contracts","schema",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":46},"01M6P6HQJNGG4WPZW0DEWMAY2N","kata-plain","An ordinary prose skill; not dispatchable.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-plain\u002FSKILL.md",[121],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[123,124,125],"kata plain","prose skill","prose",{"skillNo":127,"name":128,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":46},"01M6P6HH6Y7K8K6606MF7VZ1HB","kata-broken","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fserver\u002Ftestdata\u002Fkata\u002Fskills\u002Fkata-broken\u002FSKILL.md",[],[132,133,112,113,106,114,108,107,111,109,110],"kata broken","broken",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":154,"publishedAt":46},"01M6P6GW520QJ03A6K7Y5PWJ52","voice-before-structure","Read the project's design language and philosophy before writing structural artifacts. Ground manifests, READMEs, and descriptions in the project's voice, not boilerplate. Use when creating manifests or READMEs for established projects, writing ecosystem-level documentation, building plugin descriptions or marketplace metadata, or authoring metadata that carries a project's identity. Trigger phrases: 'write the manifest', 'create a README', 'describe this plugin', 'ground yourself in the philosophy', 'ecosystem-level work'.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fvoice-before-structure\u002FSKILL.md",[140,143,146,151],{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":144,"categoryName":145,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":152,"categoryName":153,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000036","内容创作者",[155,156,157,158,159,32,160,161,162,163,164,165,166,167,168,169,170,171,172,173],"voice before structure","structure","voice","manifests","ecosystem","authoring","structural","project","artifact","philosophy","design","writing","identity","documentation","create","projects","work","read","write",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":181,"publishedAt":46},"01M6P6GMNA4HJ4D5RRM3BQZ73M","system-prompt-archaeology","Produces a named ADA disposition preset (YAML) and a layered behavioral analysis (structural decomposition + evidence-cited classifications) from a system prompt. Use when: \"analyze this system prompt\", \"extract disposition from prompt\", \"reverse-engineer agent behavior\", \"what patterns does this prompt use\", \"build a preset from this prompt\".","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsystem-prompt-archaeology\u002FSKILL.md",[180],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[182,183,184,40,185,186,161,187,188,189,190,191,192,193,194,195,30,196,197,198],"system prompt archaeology","system prompt","prompt","behavioral","classify","decomposition","wisdom","patterns","engineer","decompose","evidence","ada","analyze","analysis","sonnet","true","reverse",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":206,"publishedAt":46},"01M6P6G2D70T9R00HX6K154X5Y","session-lifecycle-automation","Designs and configures all three loops of solo-operator session automation — session bookends, background maintenance agents, and a delegation flywheel. Use when setting up a new workspace, recovering from the 44% zero-artifact session leak, or preparing to scale delegation across multiple concurrent agents.","https:\u002F\u002Fgithub.com\u002FDojoGenesis\u002Fgateway\u002Fblob\u002Fmain\u002Fplugins\u002Fwisdom-garden\u002Fskills\u002Fsession-lifecycle-automation\u002FSKILL.md",[205],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[207,208,209,210,38,211,212,213,214,215,216,217,218,163,219,220,221,222,223,224],"automation","session lifecycle automation","session lifecycle","lifecycle","markdown","configure","directory","config","delegation","audit","SET","files","solo","across","scheduled","loops","up","template"]