[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74GJVP3XFNK7W1NHHT395V4":3,"skill-same:01M74GJVP3XFNK7W1NHHT395V4":44},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M74GJVP3XFNK7W1NHHT395V4","error-budget-policy",null,"Author an error-budget policy — what happens when budget is healthy, eroding, or exhausted; named consequences not vibes.","MohammadBafkar\u002Fpolymath","MohammadBafkar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F34940462?v=4","01M74G540TQFZWK6KVAPKFVGNR","Mohammad Bafkar","01M74G541HG19QP9V5DQCJVKYE",0,"MIT","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-sre\u002Fskills\u002Ferror-budget-policy\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: error-budget-policy\ndescription: Author an error-budget policy — what happens when budget is healthy, eroding, or exhausted; named consequences not vibes.\n---\n\n# error-budget-policy\n\n> Pin the actions tied to error-budget state. Output is a one-page policy a team can point to.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- An SLO exists but the team doesn't know what to do when budget gets thin.\n- Leadership wants reliability work to compete fairly with feature work.\n- A workflow includes a release gate keyed to the error-budget state.\n\n## Inputs\n\n- The SLO (required): target, window, and SLI — from `polymath-sre:slo-design`. No SLO: stop and run that first; a policy over an undefined budget is not a policy.\n- Budget consumed so far (optional): bad minutes, or failed\u002Ftotal requests, for the current window. Present: classify the current state with the script below.\n- The approver role for exceptions (required) — ask; unattended run: write `[TBD: approver role]` and list it in the summary, never invent a person.\n\n## Procedure\n\n0. **Current state (when consumption data exists) — run the script, don't eyeball it:**\n\n   ```bash\n   python3 \"${POLYMATH_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\u002Fskills\u002Fslo-design\u002Fscripts\u002Ferror-budget.py\" --slo 99.5 --window-days 28 --consumed-minutes 140\n   # request-based SLI: --requests 2000000 --failed 7300\n   ```\n\n   Quote its `Consumed:` and `State:` lines in the policy header.\n1. **Three states**:\n   - **Healthy** — budget consumed \u003C 50% of allowance for the window.\n   - **Eroding** — 50–100% consumed.\n   - **Exhausted** — over budget; service has missed its SLO.\n2. **Per state, name the consequence**:\n   - **Healthy**: feature work proceeds as usual.\n   - **Eroding**: required reliability work in addition to features; no risky launches; new feature flags must be rollable.\n   - **Exhausted**: feature freeze. The team works only on reliability and rollback hardening until budget is back to healthy. Exceptions require a named approver and a documented reason.\n3. **Document the named approver** (a role, e.g. \"VP Eng\", not a person).\n4. **Document the off-ramp** — how the team gets out of an exhausted state. Usually: SLO compliance for 14 consecutive days, or a budget reset following a major incident postmortem.\n5. **SLO trust** — once a quarter, review whether the SLO threshold still matches user expectations. Don't move the threshold to fit the budget; either accept the work or renegotiate the threshold with stakeholders.\n\n## Output\n\n```text\nError-budget policy: refund-service (SLO: 99.5% \u002F 28d)\n\nState: HEALTHY (\u003C 50% of the 3h 21m 36s budget used)\n  - Feature work proceeds as planned.\n  - Standard release cadence.\n\nState: ERODING (50–100% of budget used)\n  - Mandatory: every PR includes a reliability or test improvement.\n  - No \"risky\" launches (defined: schema changes, dependency upgrades,\n    new external integrations).\n  - Feature flags required for new features; must be rollable \u003C 1m.\n  - Daily 5-min standup on burn-rate.\n\nState: EXHAUSTED (> 100% of budget used)\n  - Feature freeze. Reliability and rollback hardening only.\n  - Exceptions require VP Eng sign-off; reason recorded.\n  - Resume normal work after 14 consecutive days of compliant SLO.\n\nQuarterly review:\n  - Does the 99.5% threshold still match what users need?\n  - Is the SLI definition still right (latency cutoff, success codes)?\n\nAnti-pattern guard:\n  We do not move the SLO threshold to \"fit\" the consumed budget.\n  If the SLO is genuinely wrong, we renegotiate with stakeholders\n  in writing, not via a config tweak.\n```\n\n## Anti-patterns to avoid\n\n- \"When budget is low, we'll be careful\" — not a policy.\n- Allowing exceptions without an approver or paper trail.\n- Lowering the SLO threshold to keep budget healthy. That's not reliability work.\n","# error-budget-policy\n\n> Pin the actions tied to error-budget state. Output is a one-page policy a team can point to.\n\n**Mode:** analytical — judgment inside a fixed frame. Keep the output shape; every verdict cites its evidence; unknowns are marked `[TBD]` or `[VERIFY]`, never filled in.\n\n## When to use\n\n- An SLO exists but the team doesn't know what to do when budget gets thin.\n- Leadership wants reliability work to compete fairly with feature work.\n- A workflow includes a release gate keyed to the error-budget state.\n\n## Inputs\n\n- The SLO (required): target, window, and SLI — from `polymath-sre:slo-design`. No SLO: stop and run that first; a policy over an undefined budget is not a policy.\n- Budget consumed so far (optional): bad minutes, or failed\u002Ftotal requests, for the current window. Present: classify the current state with the script below.\n- The approver role for exceptions (required) — ask; unattended run: write `[TBD: approver role]` and list it in the summary, never invent a person.\n\n## Procedure\n\n0. **Current state (when consumption data exists) — run the script, don't eyeball it:**\n\n   ```bash\n   python3 \"${POLYMATH_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}\u002Fskills\u002Fslo-design\u002Fscripts\u002Ferror-budget.py\" --slo 99.5 --window-days 28 --consumed-minutes 140\n   # request-based SLI: --requests 2000000 --failed 7300\n   ```\n\n   Quote its `Consumed:` and `State:` lines in the policy header.\n1. **Three states**:\n   - **Healthy** — budget consumed \u003C 50% of allowance for the window.\n   - **Eroding** — 50–100% consumed.\n   - **Exhausted** — over budget; service has missed its SLO.\n2. **Per state, name the consequence**:\n   - **Healthy**: feature work proceeds as usual.\n   - **Eroding**: required reliability work in addition to features; no risky launches; new feature flags must be rollable.\n   - **Exhausted**: feature freeze. The team works only on reliability and rollback hardening until budget is back to healthy. Exceptions require a named approver and a documented reason.\n3. **Document the named approver** (a role, e.g. \"VP Eng\", not a person).\n4. **Document the off-ramp** — how the team gets out of an exhausted state. Usually: SLO compliance for 14 consecutive days, or a budget reset following a major incident postmortem.\n5. **SLO trust** — once a quarter, review whether the SLO threshold still matches user expectations. Don't move the threshold to fit the budget; either accept the work or renegotiate the threshold with stakeholders.\n\n## Output\n\n```text\nError-budget policy: refund-service (SLO: 99.5% \u002F 28d)\n\nState: HEALTHY (\u003C 50% of the 3h 21m 36s budget used)\n  - Feature work proceeds as planned.\n  - Standard release cadence.\n\nState: ERODING (50–100% of budget used)\n  - Mandatory: every PR includes a reliability or test improvement.\n  - No \"risky\" launches (defined: schema changes, dependency upgrades,\n    new external integrations).\n  - Feature flags required for new features; must be rollable \u003C 1m.\n  - Daily 5-min standup on burn-rate.\n\nState: EXHAUSTED (> 100% of budget used)\n  - Feature freeze. Reliability and rollback hardening only.\n  - Exceptions require VP Eng sign-off; reason recorded.\n  - Resume normal work after 14 consecutive days of compliant SLO.\n\nQuarterly review:\n  - Does the 99.5% threshold still match what users need?\n  - Is the SLI definition still right (latency cutoff, success codes)?\n\nAnti-pattern guard:\n  We do not move the SLO threshold to \"fit\" the consumed budget.\n  If the SLO is genuinely wrong, we renegotiate with stakeholders\n  in writing, not via a config tweak.\n```\n\n## Anti-patterns to avoid\n\n- \"When budget is low, we'll be careful\" — not a policy.\n- Allowing exceptions without an approver or paper trail.\n- Lowering the SLO threshold to keep budget healthy. That's not reliability work.\n",{"name":5,"description":7},"main","23f6e21841a39580c9da2b5ec941f39dda17cd86","plugins\u002Fpolymath-sre\u002Fskills\u002Ferror-budget-policy","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath","https:\u002F\u002Fgithub.com\u002FMohammadBafkar","2026-10-29 18:34:59",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add MohammadBafkar\u002Fpolymath --skill error-budget-policy",{"tool":36,"command":37},"bunx","bunx skills add MohammadBafkar\u002Fpolymath --skill error-budget-policy",{"tool":39,"command":40},"pnpm","pnpm dlx skills add MohammadBafkar\u002Fpolymath --skill error-budget-policy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-sre\u002Fskills\u002Ferror-budget-policy\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M74GN87EBRHM9N87M7AP1HDD","runbook","Write or refresh an operational runbook for an alert\u002Fsymptom; structured as TL;DR + Pre-checks + Steps + Verification + Rollback + Escalation.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frunbook\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M74GN5GPKEC1JEKP2DFQNEQJ","rfc","Draft a lightweight design RFC to docs\u002Frfcs\u002F\u003Cslug>.md; Summary, Motivation, Detailed design, Drawbacks, Alternatives, Unresolved questions. A proposal to debate, not a recorded decision (adr).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Frfc\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M74GN2F4CWPMV4X09TG4E304","editorial-pass","Review and tighten prose in a Markdown artifact for a target tone (terse, formal, friendly) without dropping information; preserve quotations and load-bearing constraints.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Feditorial-pass\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M74GMZWGYMZ37C4DYGT6P23G","architecture-review-facilitation","Run an architecture review as a process — entry criteria, reviewer checklist, decision log, and follow-up actions — pairing the design artifact with a red-team pass.","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-review-facilitation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M74GMXVX0YX3ETDXS527XDGM","architecture-doc","Write a C4-style architecture document; System Context + Containers (+ Components when interesting) with mermaid diagrams. Describes structure, not a decision (adr) or proposal (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Farchitecture-doc\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M74GMVG1WSMCK066S3KE6V5K","adr","Write an Architecture Decision Record (Michael Nygard format) to docs\u002Fadrs\u002FNNNN-\u003Cslug>.md; frontmatter validated by the ADR artifact schema. Records a made decision, not a proposal to debate (rfc).","https:\u002F\u002Fgithub.com\u002FMohammadBafkar\u002Fpolymath\u002Fblob\u002Fmain\u002Fplugins\u002Fpolymath-writing\u002Fskills\u002Fadr\u002FSKILL.md",[],[]]