菜单
Manage tracking, evaluating, and adopting autonomous releases from mecris-bot, deciding when to sunset legacy tracks. Trigger with /follow-leader
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when users want guidance on Spec-Driven Development methodology using GitHub's Spec-Kit. Guide users through executable specification workflows for both new projects (greenfield) and existing codebases (brownfield). After any SDD command generates artifacts, automatically provide structured 10-point summaries with feature status tracking, enabling natural language feature management and keeping users engaged throughout the process.
Configure GitHub MCP server using gh CLI with Docker. Enables AI agents to interact with GitHub repositories, PRs, issues, and code search. Trigger with /github-mcp or "setup GitHub MCP"
Write SKILL.md for the user using all available wisdom and documented guidance about how Agent Skills are made. New skills are written carefully to be orthogonal to the existing skills in the same repo.
Generate Sunkworks-style post-mortem reports with timeline reconstruction, failure pattern recognition, honest technical assessments, and recovery playbooks. Trigger with /postmortem
Observe and report on Prometheus installation state, active alerts, AlertManager configuration, and rule evaluation status. Trigger with /prometheus-status
Ship Operating System: Emergency Kubernetes cluster recovery, Talos reset procedures, Synology Container Manager recovery, and graceful shutdown protocols. Trigger with /sos
| name | follow-leader |
| description | Manage tracking, evaluating, and adopting autonomous releases from mecris-bot, deciding when to sunset legacy tracks. Trigger with /follow-leader |
| allowed-tools | ["read_file","run_shell_command","mcp_github_list_pull_requests","mcp_github_get_pull_request"] |
I act as the strategic evaluator for autonomous releases published by mecris-bot, tracking when to follow its vanguard, manage parallel versions (canary vs. legacy), and sunset old releases.
/follow-leadermecris-bot.main canary vs. legacy-cloud shim).When infrastructure (like Spin v3 vs. v4) enforces constraints that the bot has moved past:
main): Follow the bot. Test bleeding-edge changes in local/sandbox environments.legacy-cloud): Maintain pragmatic shims. Backport fixes where necessary but heavily gate merging bleeding-edge bot changes here.main.| Failure Mode | Symptoms | Workaround |
|---|---|---|
| Incompatible ABI merge | Spin v4 consumer crashes on Spin v3 host | Revert on legacy-cloud; rely on negative E2E test. |
| Divergent Histories | Merge conflicts backporting to legacy | Manually resolve or rewrite async/sync logic as needed. |
| Missing Bot PRs | No updates from mecris-bot | Check token expiration or bot failure state. |
/follow-leaderRuns the autonomous evaluation workflow:
mecris-bot.main, legacy-cloud).v0.1.0-canary vs v0.0.1).