[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71M2X6WFMS1R9MJ0H3FSRBS":3,"skill-same:01M71M2X6WFMS1R9MJ0H3FSRBS":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71M2X6WFMS1R9MJ0H3FSRBS","mastermind-release",null,"Mastermind release domain — versioning, changelog, deployment coordination. Spawns a Release Manager who coordinates testing and deployment agents for a safe, traceable release pipeline.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmastermind-release\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"release","mastermind release","domain","for","pipeline","deployment","testing","auto","release manager","coordination","changelog","versioning","safe","coordinates","manager","2026-11-10 10:56:23",false,"---\nname: mastermind-release\ndescription: Mastermind release domain — versioning, changelog, deployment coordination. Spawns a Release Manager who coordinates testing and deployment agents for a safe, traceable release pipeline.\ntype: domain-skill\ndefault_mode: auto\n---\n\n# Mastermind Release Domain\n\nThis skill is invoked by `mastermind:master` or directly via `\u002Fmastermind:release`.\n\n---\n\n## Inputs\n\n- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol\u002FSKILL.md brain load)\n- `prompt`: the release goal (version target, scope, environment)\n- `project_name`: monotask space name\n- `board_id`: monotask board ID (set by master, or created standalone)\n- `mode`: auto | confirm\n\n---\n\n## Complexity Assessment\n\nAssess the prompt to determine execution mode:\n\n**Simple (direct execution):** Single-step release action:\n- \"Bump the version to 1.2.3 in package.json\"\n- \"Generate a changelog for this git range\"\n→ Use a single release-manager or coder agent. Skip manager delegation.\n\n**Complex (spawn Release Manager agent):** Any of these:\n- Full end-to-end release (version + changelog + tests + deploy)\n- Multi-environment deployment (staging → production)\n- Release requiring review gates or rollback plan\n- Coordinated release across multiple packages\n→ Spawn Release Manager agent with full briefing.\n\n---\n\n## Standalone Execution (when called without master)\n\nIf this skill is invoked directly (not by master):\n\n1. Load brain context following mastermind-protocol\u002FSKILL.md Brain Load Procedure (namespace: `release`)\n2. Run intake from mastermind-intake\u002FSKILL.md if prompt is vague\n3. Follow mastermind-protocol\u002FSKILL.md Monotask Space+Board Setup Procedure:\n   ```bash\n   project_name=\"${project_name:-$(basename \"$PWD\")}\"\n   space_id=$(monotask space list 2>\u002Fdev\u002Fnull | awk -F' \\| ' -v n=\"$project_name\" '$2==n{print $1}' | head -1)\n   [ -z \"$space_id\" ] && space_id=$(monotask space create \"$project_name\" 2>&1 | grep -oE '[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}')\n   [ -z \"$space_id\" ] && { echo \"ERROR: Could not find or create space '$project_name'\"; exit 1; }\n   board_id=$(monotask board create \"release\" --json | jq -r '.id \u002F\u002F empty')\n   [ -z \"$board_id\" ] && { echo \"ERROR: Failed to create release board\"; exit 1; }\n   monotask space boards add \"$space_id\" \"$board_id\" >\u002Fdev\u002Fnull 2>&1 || true\n   todo_col=$(monotask column create \"$board_id\" \"Todo\"  --json | jq -r '.id')\n   doing_col=$(monotask column create \"$board_id\" \"Doing\" --json | jq -r '.id')\n   done_col=$(monotask column create \"$board_id\" \"Done\"  --json | jq -r '.id')\n   ```\n4. Proceed with complexity assessment below\n5. At end: follow mastermind-protocol\u002FSKILL.md Brain Write Procedure (namespace: `release`)\n\n---\n\n## Complex Execution — Release Manager Agent\n\nSpawn a Release Manager agent via Task tool:\n\n```javascript\nTask({\n  subagent_type: \"coordinator\",\n  description: `You are the Release Manager for project \u003Cproject_name>.\n\nCONTEXT: \u003Cdate> | Project: \u003Cproject_name> | Spawned by: mastermind:release\n\nBRAIN CONTEXT:\n\u003Cbrain_context>\n\nYOUR BOARD: \u003Cboard_id>\nYOUR GOAL: \u003Cprompt>\n\nSTEP 1 — PLAN\nDecompose the release into ordered stages. Identify for each stage:\n- Pre-release: version bump, changelog, final tests\n- Release: build, package, deploy to target environment\n- Post-release: smoke tests, monitoring check, announcement prep\n- Rollback plan: what triggers a rollback and how to execute it\n\nSTEP 2 — CREATE TASKS\nFor each release stage, create a monotask card on the project board. First look up column IDs and assign shell variables:\n```bash\ncolumns=$(monotask column list \"$BOARD_ID\" --json)\nCOL_TODO_ID=$(echo \"$columns\" | jq -r '.[] | select(.title == \"Todo\" or .title == \"Backlog\") | .id' | head -1)\nCOL_DONE_ID=$(echo \"$columns\" | jq -r '.[] | select(.title == \"Done\") | .id' | head -1)\n```\nThen create the card:\n```bash\nresult=$(monotask card create \"$BOARD_ID\" \"$COL_TODO_ID\" \"\u003Cshort summary of release stage goal, ≤80 chars>\" --json)\nCARD_ID=$(echo \"$result\" | jq -r '.id \u002F\u002F empty')\nmonotask card set-description \"$BOARD_ID\" \"$CARD_ID\" \"[specific release stage goal]\"\nmonotask card comment add \"$BOARD_ID\" \"$CARD_ID\" \"CONTEXT: \u003Cdate> | Project: \u003Cproject_name> | Created by: Release Manager\nBRAIN MEMORY: [paste most relevant 3-5 brain context excerpts]\nSCOPE: [packages, environments, services in scope]\nCONSTRAINTS: [breaking change rules, downtime windows, rollback triggers, compliance gates]\nSUCCESS CRITERIA:\n- [ ] [checkable item — e.g. \\\"all tests green before deploy\\\"]\nAGENT: [specialist picked in STEP 3]\nSWARM: hierarchical 5 raft\nDEPENDENCIES: [prior stage task ID — release pipeline is sequential]\nOUTPUT FORMAT: unified output schema\"\n```\n\nSTEP 3 — EXECUTE\nSpawn Task agents in release order (hierarchical raft — coordinator maintains authoritative release state).\nPick one specialist per release stage from the shared agent index (the Jev decision model when configured, keyword ranking otherwise); it only returns agents that exist. In order: the prompt's `[PICK]` line when it fits this release stage; else `mcp__monomind__pick({ task: \"\u003Crelease stage>: \u003Cscope>\", kind: \"agents\", top: 1 })` → `agents.ranked[0].name`; else the local CLI through the version-checked `mmpick` helper (never npx; the block defines it because each Bash call starts a fresh shell):\n```bash\n# Local only — never npx. Accept a binary only when its pick output is the\n# unified index (skill entries carry `source`); see mastermind-agent-select.\nmmpick() { for c in monomind .\u002Fnode_modules\u002F.bin\u002Fmonomind; do\n    command -v \"$c\" >\u002Fdev\u002Fnull 2>&1 || continue\n    out=$(\"$c\" pick \"$@\" --json 2>\u002Fdev\u002Fnull) || continue\n    printf '%s' \"$out\" | jq -e '[.skills.ranked[]? | has(\"source\")] | (length > 0 and all)' \\\n      >\u002Fdev\u002Fnull 2>&1 && { printf '%s\\n' \"$out\"; return 0; }\n  done; return 127; }\nmmpick -t \"\u003Crelease stage>: \u003Cscope>\" --top 1 | jq -r '.agents.ranked[0].name \u002F\u002F empty'\n```\nUse the returned name as that release stage's subagent_type. If nothing is returned, use the default below.\n- Pre-release prep: \"release-manager\"\n- Testing gate: \"tester\"\n- Infrastructure and deploy: \"DevOps Automator\"\n- CI\u002FCD pipeline: \"workflow-automation\"\n\nAlso run \u002Fmastermind:do --board \u003Cboard_id> to track execution.\n\nSTEP 4 — COLLECT AND RETURN\nCollect all stage outcomes. Return to caller:\n\ndomain: release\nstatus: complete | partial | blocked\nartifacts:\n  - path: [changelog file, release notes, deployment manifest]\n    type: config\ndecisions:\n  - what: [version strategy, deploy window, rollback threshold]\n    why: [reasoning]\n    confidence: [0.0-1.0]\n    outcome: shipped | pending | reverted\nlessons:\n  - what_worked: [what made the release smooth]\n  - what_didnt: [what caused delays or required rollback]\nnext_actions:\n  - [e.g. \"run mastermind:ops to monitor post-release metrics\"]\n  - [e.g. \"run mastermind:review on the next release candidate\"]\nboard_url: monotask:\u002F\u002F\u003Cproject_name>\u002Frelease\nrun_id: \u003CISO8601-timestamp>`,\n  run_in_background: true\n})\n```\n\n---\n\n## Simple Execution\n\nFor simple tasks (single agent, single step):\n\n1. Spawn one Task agent with the release action as a self-contained briefing\n2. Collect output\n3. Return unified output schema with `status: complete`\n\n---\n\n## Domain Swarm Defaults\n\n| Task Type | Agent | Swarm |\n|---|---|---|\n| Full end-to-end release | coordinator + tester + DevOps Automator | hierarchical 5 raft specialized |\n| Multi-package release | coordinator + release-manager | hierarchical 5 raft specialized |\n| Deploy only | DevOps Automator | hierarchical 3 raft specialized |\n| Test gate | tester | star 4 raft parallel |\n| Changelog \u002F version bump | release-manager | single agent |\n","# Mastermind Release Domain\n\nThis skill is invoked by `mastermind:master` or directly via `\u002Fmastermind:release`.\n\n---\n\n## Inputs\n\n- `brain_context`: BRAIN CONTEXT block (injected by master, or loaded standalone via mastermind-protocol\u002FSKILL.md brain load)\n- `prompt`: the release goal (version target, scope, environment)\n- `project_name`: monotask space name\n- `board_id`: monotask board ID (set by master, or created standalone)\n- `mode`: auto | confirm\n\n---\n\n## Complexity Assessment\n\nAssess the prompt to determine execution mode:\n\n**Simple (direct execution):** Single-step release action:\n- \"Bump the version to 1.2.3 in package.json\"\n- \"Generate a changelog for this git range\"\n→ Use a single release-manager or coder agent. Skip manager delegation.\n\n**Complex (spawn Release Manager agent):** Any of these:\n- Full end-to-end release (version + changelog + tests + deploy)\n- Multi-environment deployment (staging → production)\n- Release requiring review gates or rollback plan\n- Coordinated release across multiple packages\n→ Spawn Release Manager agent with full briefing.\n\n---\n\n## Standalone Execution (when called without master)\n\nIf this skill is invoked directly (not by master):\n\n1. Load brain context following mastermind-protocol\u002FSKILL.md Brain Load Procedure (namespace: `release`)\n2. Run intake from mastermind-intake\u002FSKILL.md if prompt is vague\n3. Follow mastermind-protocol\u002FSKILL.md Monotask Space+Board Setup Procedure:\n   ```bash\n   project_name=\"${project_name:-$(basename \"$PWD\")}\"\n   space_id=$(monotask space list 2>\u002Fdev\u002Fnull | awk -F' \\| ' -v n=\"$project_name\" '$2==n{print $1}' | head -1)\n   [ -z \"$space_id\" ] && space_id=$(monotask space create \"$project_name\" 2>&1 | grep -oE '[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}')\n   [ -z \"$space_id\" ] && { echo \"ERROR: Could not find or create space '$project_name'\"; exit 1; }\n   board_id=$(monotask board create \"release\" --json | jq -r '.id \u002F\u002F empty')\n   [ -z \"$board_id\" ] && { echo \"ERROR: Failed to create release board\"; exit 1; }\n   monotask space boards add \"$space_id\" \"$board_id\" >\u002Fdev\u002Fnull 2>&1 || true\n   todo_col=$(monotask column create \"$board_id\" \"Todo\"  --json | jq -r '.id')\n   doing_col=$(monotask column create \"$board_id\" \"Doing\" --json | jq -r '.id')\n   done_col=$(monotask column create \"$board_id\" \"Done\"  --json | jq -r '.id')\n   ```\n4. Proceed with complexity assessment below\n5. At end: follow mastermind-protocol\u002FSKILL.md Brain Write Procedure (namespace: `release`)\n\n---\n\n## Complex Execution — Release Manager Agent\n\nSpawn a Release Manager agent via Task tool:\n\n```javascript\nTask({\n  subagent_type: \"coordinator\",\n  description: `You are the Release Manager for project \u003Cproject_name>.\n\nCONTEXT: \u003Cdate> | Project: \u003Cproject_name> | Spawned by: mastermind:release\n\nBRAIN CONTEXT:\n\u003Cbrain_context>\n\nYOUR BOARD: \u003Cboard_id>\nYOUR GOAL: \u003Cprompt>\n\nSTEP 1 — PLAN\nDecompose the release into ordered stages. Identify for each stage:\n- Pre-release: version bump, changelog, final tests\n- Release: build, package, deploy to target environment\n- Post-release: smoke tests, monitoring check, announcement prep\n- Rollback plan: what triggers a rollback and how to execute it\n\nSTEP 2 — CREATE TASKS\nFor each release stage, create a monotask card on the project board. First look up column IDs and assign shell variables:\n```bash\ncolumns=$(monotask column list \"$BOARD_ID\" --json)\nCOL_TODO_ID=$(echo \"$columns\" | jq -r '.[] | select(.title == \"Todo\" or .title == \"Backlog\") | .id' | head -1)\nCOL_DONE_ID=$(echo \"$columns\" | jq -r '.[] | select(.title == \"Done\") | .id' | head -1)\n```\nThen create the card:\n```bash\nresult=$(monotask card create \"$BOARD_ID\" \"$COL_TODO_ID\" \"\u003Cshort summary of release stage goal, ≤80 chars>\" --json)\nCARD_ID=$(echo \"$result\" | jq -r '.id \u002F\u002F empty')\nmonotask card set-description \"$BOARD_ID\" \"$CARD_ID\" \"[specific release stage goal]\"\nmonotask card comment add \"$BOARD_ID\" \"$CARD_ID\" \"CONTEXT: \u003Cdate> | Project: \u003Cproject_name> | Created by: Release Manager\nBRAIN MEMORY: [paste most relevant 3-5 brain context excerpts]\nSCOPE: [packages, environments, services in scope]\nCONSTRAINTS: [breaking change rules, downtime windows, rollback triggers, compliance gates]\nSUCCESS CRITERIA:\n- [ ] [checkable item — e.g. \\\"all tests green before deploy\\\"]\nAGENT: [specialist picked in STEP 3]\nSWARM: hierarchical 5 raft\nDEPENDENCIES: [prior stage task ID — release pipeline is sequential]\nOUTPUT FORMAT: unified output schema\"\n```\n\nSTEP 3 — EXECUTE\nSpawn Task agents in release order (hierarchical raft — coordinator maintains authoritative release state).\nPick one specialist per release stage from the shared agent index (the Jev decision model when configured, keyword ranking otherwise); it only returns agents that exist. In order: the prompt's `[PICK]` line when it fits this release stage; else `mcp__monomind__pick({ task: \"\u003Crelease stage>: \u003Cscope>\", kind: \"agents\", top: 1 })` → `agents.ranked[0].name`; else the local CLI through the version-checked `mmpick` helper (never npx; the block defines it because each Bash call starts a fresh shell):\n```bash\n# Local only — never npx. Accept a binary only when its pick output is the\n# unified index (skill entries carry `source`); see mastermind-agent-select.\nmmpick() { for c in monomind .\u002Fnode_modules\u002F.bin\u002Fmonomind; do\n    command -v \"$c\" >\u002Fdev\u002Fnull 2>&1 || continue\n    out=$(\"$c\" pick \"$@\" --json 2>\u002Fdev\u002Fnull) || continue\n    printf '%s' \"$out\" | jq -e '[.skills.ranked[]? | has(\"source\")] | (length > 0 and all)' \\\n      >\u002Fdev\u002Fnull 2>&1 && { printf '%s\\n' \"$out\"; return 0; }\n  done; return 127; }\nmmpick -t \"\u003Crelease stage>: \u003Cscope>\" --top 1 | jq -r '.agents.ranked[0].name \u002F\u002F empty'\n```\nUse the returned name as that release stage's subagent_type. If nothing is returned, use the default below.\n- Pre-release prep: \"release-manager\"\n- Testing gate: \"tester\"\n- Infrastructure and deploy: \"DevOps Automator\"\n- CI\u002FCD pipeline: \"workflow-automation\"\n\nAlso run \u002Fmastermind:do --board \u003Cboard_id> to track execution.\n\nSTEP 4 — COLLECT AND RETURN\nCollect all stage outcomes. Return to caller:\n\ndomain: release\nstatus: complete | partial | blocked\nartifacts:\n  - path: [changelog file, release notes, deployment manifest]\n    type: config\ndecisions:\n  - what: [version strategy, deploy window, rollback threshold]\n    why: [reasoning]\n    confidence: [0.0-1.0]\n    outcome: shipped | pending | reverted\nlessons:\n  - what_worked: [what made the release smooth]\n  - what_didnt: [what caused delays or required rollback]\nnext_actions:\n  - [e.g. \"run mastermind:ops to monitor post-release metrics\"]\n  - [e.g. \"run mastermind:review on the next release candidate\"]\nboard_url: monotask:\u002F\u002F\u003Cproject_name>\u002Frelease\nrun_id: \u003CISO8601-timestamp>`,\n  run_in_background: true\n})\n```\n\n---\n\n## Simple Execution\n\nFor simple tasks (single agent, single step):\n\n1. Spawn one Task agent with the release action as a self-contained briefing\n2. Collect output\n3. Return unified output schema with `status: complete`\n\n---\n\n## Domain Swarm Defaults\n\n| Task Type | Agent | Swarm |\n|---|---|---|\n| Full end-to-end release | coordinator + tester + DevOps Automator | hierarchical 5 raft specialized |\n| Multi-package release | coordinator + release-manager | hierarchical 5 raft specialized |\n| Deploy only | DevOps Automator | hierarchical 3 raft specialized |\n| Test gate | tester | star 4 raft parallel |\n| Changelog \u002F version bump | release-manager | single agent |\n",{"name":5,"type":43,"description":7,"default_mode":30},"domain-skill","main","f7cd4595d0f8959822163e14f9787117765c931a",".claude\u002Fskills\u002Fmastermind-release",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add monoes\u002Fmonomind --skill mastermind-release",{"tool":59,"command":60},"bunx","bunx skills add monoes\u002Fmonomind --skill mastermind-release",{"tool":62,"command":63},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill mastermind-release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmastermind-release\u002FSKILL.md",true,[],[68,96,131,158,182,207],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":95},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":100,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":112,"publishedAt":95},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[104,107],{"categoryNo":105,"categoryName":106,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":108,"categoryName":109,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[113,114,115,79,116,117,118,119,84,120,121,122,123,124,125,126,127,128,129,130],"writing","writing plans","plans","superpowers","implementation plan","when","you","code","tasks","plan","product","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":141,"publishedAt":95},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[138],{"categoryNo":139,"categoryName":140,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000031","产品经理",[124,142,143,144,145,82,146,118,147,148,149,123,150,151,152,153,154,155,156,157],"write spec","spec","user request","problem","acceptance","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":168,"publishedAt":95},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[165],{"categoryNo":166,"categoryName":167,"taxonomyType":110,"taxonomyTypeDesc":111},"01JBSEEDCAT000000000000033","数据分析师",[84,124,169,170,26,171,82,156,118,172,173,174,175,149,176,177,178,179,180,181],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":192,"publishedAt":95},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[188,191],{"categoryNo":189,"categoryName":190,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[193,194,195,196,26,197,198,199,200,83,201,202,203,84,87,176,204,205,206,178],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":214,"publishedAt":95},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[213],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[195,215,216,217,218,219,220,26,221,222,120,223,224,225,87,176,226,227,178,228],"workflow architect","architect","trees","user journeys","branch","planning","map","workflows","architecture","state","leadership","recovery","operations","systems"]