[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71B8VJCTZ2FW2GNTSTX8QGX":3,"skill-same:01M71B8VJCTZ2FW2GNTSTX8QGX":63},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M71B8VJCTZ2FW2GNTSTX8QGX","openspec-archive-change",null,"Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.","Wizarck\u002Fnexandro","Wizarck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F23051550?v=4","01M71B3AAVR67GRWFV5ZXXZP31","arturo6ramirez","01M71B3ABYG1BFNXHX4KZ3PPK6",2,"MIT","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fopenspec-archive-change\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"change","openspec archive change","openspec","archive","finalize","implementation","cli","use","when","workflow","complete","user","2026-11-10 10:12:30",false,"---\nname: openspec-archive-change\ndescription: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.\nlicense: MIT\ncompatibility: Requires openspec CLI.\nmetadata:\n  author: openspec\n  version: \"1.0\"\n  generatedBy: \"1.3.0\"\n---\n\nArchive a completed change in the experimental workflow.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n0. **Verify project board Status=Done before archiving** (per [project-board-sync.md](..\u002F..\u002Fdocs\u002Fconcepts\u002Fproject-board-sync.md) §2 L7)\n\n   Invoke `scripts\u002Fverify_board_state.py` BEFORE doing any archive work. The script queries the GH Project board and exits non-zero if the matching item's Status is not `Done`. Refuse to archive on non-zero exit — do NOT paraphrase the script's output, cite the exit code (per [verification-before-completion.md](..\u002F..\u002Fdocs\u002Frules\u002Fverification-before-completion.rule.md) §4.1.2).\n\n   Required env \u002F inputs:\n   - `--change-id` — the OpenSpec change-id being archived\n   - `--owner` — GH user\u002Forg login owning the project\n   - `--project-number` — numeric Project V2 ID\n   - `--expected-status Done` — default for archive workflows\n\n   ```bash\n   python -m scripts.verify_board_state \\\n       --change-id \u003Cname> \\\n       --owner \u003Cgh-user-or-org> \\\n       --project-number \u003CN> \\\n       --expected-status Done\n   ```\n\n   Exit-code semantics (stable contract):\n   - `0` — Status=Done, proceed.\n   - `1` — Status mismatch. Refuse archive: surface the script's stderr to the user and ask them to (a) wait for L1 PR-merged automation to fire, or (b) verify the L2 workflow ran correctly, or (c) manually advance the status if board got drift.\n   - `2` — Item not found. Refuse archive: the change-id doesn't match a project item title.\n   - `3` — GraphQL\u002Fnetwork error. Surface to user and offer one retry.\n\n   **If `scripts\u002Fverify_board_state.py` is not present** (consumer on ai-playbook \u003C v0.10.0): emit a warning and continue (legacy behaviour). New consumers (v0.10.0+) MUST have the script and MUST not bypass.\n\n1. **If no change name provided, prompt for selection**\n\n   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.\n\n   Show only active changes (not already archived).\n   Include the schema used for each change if available.\n\n   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.\n\n2. **Check artifact completion status**\n\n   Run `openspec status --change \"\u003Cname>\" --json` to check artifact completion.\n\n   Parse the JSON to understand:\n   - `schemaName`: The workflow being used\n   - `artifacts`: List of artifacts with their status (`done` or other)\n\n   **If any artifacts are not `done`:**\n   - Display warning listing incomplete artifacts\n   - Use **AskUserQuestion tool** to confirm user wants to proceed\n   - Proceed if user confirms\n\n3. **Check task completion status**\n\n   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.\n\n   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).\n\n   **If incomplete tasks found:**\n   - Display warning showing count of incomplete tasks\n   - Use **AskUserQuestion tool** to confirm user wants to proceed\n   - Proceed if user confirms\n\n   **If no tasks file exists:** Proceed without task-related warning.\n\n4. **Assess delta spec sync state** (informational only — no automated sync in this version)\n\n   Check for delta specs at `openspec\u002Fchanges\u002F\u003Cname>\u002Fspecs\u002F`. If none exist, proceed without notice.\n\n   **If delta specs exist:**\n   - Compare each delta spec with its corresponding main spec at `openspec\u002Fspecs\u002F\u003Ccapability>\u002Fspec.md`\n   - Determine what changes would be applied (adds, modifications, removals, renames)\n   - Show a combined summary so the user knows what an eventual sync would do.\n\n   Archive only does the move + retro — no automated sync is performed.\n\n5. **Perform the archive**\n\n   Create the archive directory if it doesn't exist:\n   ```bash\n   mkdir -p openspec\u002Fchanges\u002Farchive\n   ```\n\n   Generate target name using current date: `YYYY-MM-DD-\u003Cchange-name>`\n\n   **Check if target already exists:**\n   - If yes: Fail with error, suggest renaming existing archive or using different date\n   - If no: Move the change directory to archive\n\n   ```bash\n   mv openspec\u002Fchanges\u002F\u003Cname> openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\n   ```\n\n6. **Chain a retrospective write to `retros\u002F\u003Cchange-id>.md`** (Gate F deliverable)\n\n   Per [runbook-bmad-openspec.md](..\u002F..\u002Fdocs\u002Fconcepts\u002Frunbook-bmad-openspec.md) §3.1 and §4 + Gate F in §5, every archive MUST chain a retro write. Path: `retros\u002F\u003Cchange-id>.md` (relative to the project root). Create the `retros\u002F` directory if it does not exist.\n\n   - **If a `bmad-retrospective` skill is available**, invoke it via the Skill tool, passing the change-id and the archive path. It produces the retro per the BMAD retrospective format.\n   - **Otherwise, write a stub markdown directly** with the following sections (the human fills them in):\n\n     ```markdown\n     # Retrospective: \u003Cchange-id>\n\n     - **Archived**: YYYY-MM-DD\n     - **Archive path**: openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cchange-id>\u002F\n     - **Schema**: \u003Cschema-name>\n\n     ## What worked\n\n     \u003Cone-paragraph: practices, patterns, decisions that paid off>\n\n     ## What didn't\n\n     \u003Cone-paragraph: friction, surprises, rework>\n\n     ## Lessons\n\n     \u003Cbulleted: durable lessons; candidates for retention to Hindsight if cross-project>\n\n     ## Carry-forward to next change\n\n     \u003Cbulleted: action items, follow-up tickets, spec edits>\n     ```\n\n   If `retros\u002F\u003Cchange-id>.md` already exists, do NOT overwrite — append a new dated section instead and warn the user.\n\n7. **Display summary**\n\n   Show archive completion summary including:\n   - Change name\n   - Schema that was used\n   - Archive location\n   - Whether specs were synced (if applicable)\n   - Note about any warnings (incomplete artifacts\u002Ftasks)\n\n**Output On Success**\n\n```\n## Archive Complete\n\n**Change:** \u003Cchange-name>\n**Schema:** \u003Cschema-name>\n**Archived to:** openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\u002F\n**Specs:** No automated sync (deferred to v0.8.0 spec-sync skill); delta-spec assessment shown above for human follow-up.\n**Retro:** retros\u002F\u003Cchange-id>.md (stub written \u002F appended)\n\nAll artifacts complete. All tasks complete.\n```\n\n**Guardrails**\n- **Always run Step 0 first** (project board Status=Done verification) for consumers on ai-playbook v0.10.0+; refuse archive on non-zero exit per project-board-sync.md L7\n- Always prompt for change selection if not provided\n- Use artifact graph (openspec status --json) for completion checking\n- Don't block archive on warnings - just inform and confirm\n- Preserve .openspec.yaml when moving to archive (it moves with the directory)\n- Show clear summary of what happened\n- Always chain the retro write (step 6) — Gate F deliverable per the runbook; never skip silently\n- If delta specs exist, always run the assessment and show the combined summary (informational only until v0.8.0)\n","Archive a completed change in the experimental workflow.\n\n**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.\n\n**Steps**\n\n0. **Verify project board Status=Done before archiving** (per [project-board-sync.md](..\u002F..\u002Fdocs\u002Fconcepts\u002Fproject-board-sync.md) §2 L7)\n\n   Invoke `scripts\u002Fverify_board_state.py` BEFORE doing any archive work. The script queries the GH Project board and exits non-zero if the matching item's Status is not `Done`. Refuse to archive on non-zero exit — do NOT paraphrase the script's output, cite the exit code (per [verification-before-completion.md](..\u002F..\u002Fdocs\u002Frules\u002Fverification-before-completion.rule.md) §4.1.2).\n\n   Required env \u002F inputs:\n   - `--change-id` — the OpenSpec change-id being archived\n   - `--owner` — GH user\u002Forg login owning the project\n   - `--project-number` — numeric Project V2 ID\n   - `--expected-status Done` — default for archive workflows\n\n   ```bash\n   python -m scripts.verify_board_state \\\n       --change-id \u003Cname> \\\n       --owner \u003Cgh-user-or-org> \\\n       --project-number \u003CN> \\\n       --expected-status Done\n   ```\n\n   Exit-code semantics (stable contract):\n   - `0` — Status=Done, proceed.\n   - `1` — Status mismatch. Refuse archive: surface the script's stderr to the user and ask them to (a) wait for L1 PR-merged automation to fire, or (b) verify the L2 workflow ran correctly, or (c) manually advance the status if board got drift.\n   - `2` — Item not found. Refuse archive: the change-id doesn't match a project item title.\n   - `3` — GraphQL\u002Fnetwork error. Surface to user and offer one retry.\n\n   **If `scripts\u002Fverify_board_state.py` is not present** (consumer on ai-playbook \u003C v0.10.0): emit a warning and continue (legacy behaviour). New consumers (v0.10.0+) MUST have the script and MUST not bypass.\n\n1. **If no change name provided, prompt for selection**\n\n   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.\n\n   Show only active changes (not already archived).\n   Include the schema used for each change if available.\n\n   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.\n\n2. **Check artifact completion status**\n\n   Run `openspec status --change \"\u003Cname>\" --json` to check artifact completion.\n\n   Parse the JSON to understand:\n   - `schemaName`: The workflow being used\n   - `artifacts`: List of artifacts with their status (`done` or other)\n\n   **If any artifacts are not `done`:**\n   - Display warning listing incomplete artifacts\n   - Use **AskUserQuestion tool** to confirm user wants to proceed\n   - Proceed if user confirms\n\n3. **Check task completion status**\n\n   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.\n\n   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).\n\n   **If incomplete tasks found:**\n   - Display warning showing count of incomplete tasks\n   - Use **AskUserQuestion tool** to confirm user wants to proceed\n   - Proceed if user confirms\n\n   **If no tasks file exists:** Proceed without task-related warning.\n\n4. **Assess delta spec sync state** (informational only — no automated sync in this version)\n\n   Check for delta specs at `openspec\u002Fchanges\u002F\u003Cname>\u002Fspecs\u002F`. If none exist, proceed without notice.\n\n   **If delta specs exist:**\n   - Compare each delta spec with its corresponding main spec at `openspec\u002Fspecs\u002F\u003Ccapability>\u002Fspec.md`\n   - Determine what changes would be applied (adds, modifications, removals, renames)\n   - Show a combined summary so the user knows what an eventual sync would do.\n\n   Archive only does the move + retro — no automated sync is performed.\n\n5. **Perform the archive**\n\n   Create the archive directory if it doesn't exist:\n   ```bash\n   mkdir -p openspec\u002Fchanges\u002Farchive\n   ```\n\n   Generate target name using current date: `YYYY-MM-DD-\u003Cchange-name>`\n\n   **Check if target already exists:**\n   - If yes: Fail with error, suggest renaming existing archive or using different date\n   - If no: Move the change directory to archive\n\n   ```bash\n   mv openspec\u002Fchanges\u002F\u003Cname> openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\n   ```\n\n6. **Chain a retrospective write to `retros\u002F\u003Cchange-id>.md`** (Gate F deliverable)\n\n   Per [runbook-bmad-openspec.md](..\u002F..\u002Fdocs\u002Fconcepts\u002Frunbook-bmad-openspec.md) §3.1 and §4 + Gate F in §5, every archive MUST chain a retro write. Path: `retros\u002F\u003Cchange-id>.md` (relative to the project root). Create the `retros\u002F` directory if it does not exist.\n\n   - **If a `bmad-retrospective` skill is available**, invoke it via the Skill tool, passing the change-id and the archive path. It produces the retro per the BMAD retrospective format.\n   - **Otherwise, write a stub markdown directly** with the following sections (the human fills them in):\n\n     ```markdown\n     # Retrospective: \u003Cchange-id>\n\n     - **Archived**: YYYY-MM-DD\n     - **Archive path**: openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cchange-id>\u002F\n     - **Schema**: \u003Cschema-name>\n\n     ## What worked\n\n     \u003Cone-paragraph: practices, patterns, decisions that paid off>\n\n     ## What didn't\n\n     \u003Cone-paragraph: friction, surprises, rework>\n\n     ## Lessons\n\n     \u003Cbulleted: durable lessons; candidates for retention to Hindsight if cross-project>\n\n     ## Carry-forward to next change\n\n     \u003Cbulleted: action items, follow-up tickets, spec edits>\n     ```\n\n   If `retros\u002F\u003Cchange-id>.md` already exists, do NOT overwrite — append a new dated section instead and warn the user.\n\n7. **Display summary**\n\n   Show archive completion summary including:\n   - Change name\n   - Schema that was used\n   - Archive location\n   - Whether specs were synced (if applicable)\n   - Note about any warnings (incomplete artifacts\u002Ftasks)\n\n**Output On Success**\n\n```\n## Archive Complete\n\n**Change:** \u003Cchange-name>\n**Schema:** \u003Cschema-name>\n**Archived to:** openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\u002F\n**Specs:** No automated sync (deferred to v0.8.0 spec-sync skill); delta-spec assessment shown above for human follow-up.\n**Retro:** retros\u002F\u003Cchange-id>.md (stub written \u002F appended)\n\nAll artifacts complete. All tasks complete.\n```\n\n**Guardrails**\n- **Always run Step 0 first** (project board Status=Done verification) for consumers on ai-playbook v0.10.0+; refuse archive on non-zero exit per project-board-sync.md L7\n- Always prompt for change selection if not provided\n- Use artifact graph (openspec status --json) for completion checking\n- Don't block archive on warnings - just inform and confirm\n- Preserve .openspec.yaml when moving to archive (it moves with the directory)\n- Show clear summary of what happened\n- Always chain the retro write (step 6) — Gate F deliverable per the runbook; never skip silently\n- If delta specs exist, always run the assessment and show the combined summary (informational only until v0.8.0)\n",{"name":5,"license":15,"metadata":36,"description":7,"compatibility":39},{"author":21,"version":37,"generatedBy":38},"1.0","1.3.0","Requires openspec CLI.","master","f57cddf3a79f076c1bb1ba9c187850fba797c0c9","skills\u002Fopenspec-archive-change",1,"https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro","https:\u002F\u002Fgithub.com\u002FWizarck","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Framirezarturo\u002F","Geek by birth, with not much to say but plenty to talk about.","2026-09-25 20:04:26",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Wizarck\u002Fnexandro --skill openspec-archive-change",{"tool":55,"command":56},"bunx","bunx skills add Wizarck\u002Fnexandro --skill openspec-archive-change",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Wizarck\u002Fnexandro --skill openspec-archive-change","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fopenspec-archive-change\u002FSKILL.md",true,[],[64,99,128,151,165,191],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":81,"publishedAt":31},"01M71BBM78XJY2YXFXJ2YNCEGY","xlsx","Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file; create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files into proper spreadsheets.","AGPL-3.0","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fxlsx\u002FSKILL.md",[71,76],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000004","电子表格","SCENARIO","使用场景",{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[66,82,83,84,85,86,87,88,89,90,91,92,93,26,94,27,95,96,97,98],"sources","tsv","by name","for","spreadsheet","time","trigger","fix","scratch","open","new","files","Existing","done","convert","file","tabular",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":111,"publishedAt":31},"01M71BBGZJG2FKCPJZWR32SCZ5","use-case-research","Creates JTBD-aligned Use Cases CSVs through structured user interviews, parallel vendor\u002Findustry research, and Jobs-to-be-Done synthesis. Generates 17-column CSV (OFFER-001 format) and validates with \u002Fqa-use-cases. Use when creating or updating use case research for an offering.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fuse-case-research\u002FSKILL.md",[105,108],{"categoryNo":106,"categoryName":107,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":109,"categoryName":110,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发",[112,26,113,114,115,116,117,118,27,95,119,120,121,122,123,124,125,126,85,127],"use case research","case","research","industry research","user interviews","qa","jtbd","Bash","websearch","read","write","edit","interviews","opus","parallel","true",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":31},"01M71BBCCGXCBJZSYK72CT7MJW","sync-jira","Two-way sync between PROGRESS.md pipeline status and JIRA CIT tasks. Use when syncing offering progress with JIRA, checking JIRA status, bootstrapping JIRA tasks for new offerings, or pushing\u002Fpulling status updates. Also use when the user mentions JIRA, CIT tasks, or pipeline sync.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fsync-jira\u002FSKILL.md",[134],{"categoryNo":109,"categoryName":110,"taxonomyType":74,"taxonomyTypeDesc":75},[136,137,138,139,140,85,141,142,92,143,26,27,144,119,145,146,147,148,149,150],"sync jira","jira","sync","pull","push","pipeline","status updates","MCP","updates","tasks","bootstrap","dry","two","with","id",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"publishedAt":31},"01M71BBAV2F4ABBVAM9FMZ692C","strategy","Tunes business strategy and aligns with corporate ABC Goals. Use when working on 01_BS\u002F business strategy files.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstrategy\u002FSKILL.md",[157],{"categoryNo":109,"categoryName":110,"taxonomyType":74,"taxonomyTypeDesc":75},[153,127,93,26,159,27,149,150,160,161,121,122,123,162,163,164],"business","goals","business strategy","corporate","grep","sonnet",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":175,"publishedAt":31},"01M71BB6N1EJDAMAWAF0FSGFRR","start","Starts the full MCP stack: LiteLLM proxy + Docker services (Hindsight, Atlassian, Google Workspace) + skills-manager + notebooklm. All services connect directly — no proxy. Use \u002Fstart at the beginning of any session where MCP tools are needed, or when any service is stopped. LiteLLM must start before Docker — Hindsight depends on it at startup.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart\u002FSKILL.md",[171,174],{"categoryNo":172,"categoryName":173,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":109,"categoryName":110,"taxonomyType":74,"taxonomyTypeDesc":75},[167,176,177,178,179,180,181,143,26,182,27,119,183,184,185,186,187,188,189,190],"hindsight","google workspace","proxy","docker","session","litellm","connect","stack","haiku","services","workspace","at","notebooklm","google","startup",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":31},"01M71BB50307CW202PCTECJ3BB","start-palafito","Úsalo cuando el usuario quiere arrancar el stack palafito-prod (Paperclip) y, si hace falta, levantar Docker Desktop antes.","https:\u002F\u002Fgithub.com\u002FWizarck\u002Fnexandro\u002Fblob\u002Fmaster\u002Fskills\u002Fstart-palafito\u002FSKILL.md",[197],{"categoryNo":172,"categoryName":173,"taxonomyType":74,"taxonomyTypeDesc":75},[167,199,183,200,201,202,119,179,164],"start palafito","desktop","fork","paperclip"]