senior-operating-system
Skill0 starsChanged 4 months agoMITView on GitHub
A capstone bundle that activates the core senior engineering skill set for a specific workflow such as delivery, architecture, staff leadership, reliability, or launch readiness.
In this repository32 other files it gives its agents.
- architect-modeSkill
- architecture-bundleSkill
- code-like-a-localSkill
- decision-making-guardrailsSkill
- decision-recordsSkill
- delivery-bundleSkill
- fable-modeSkill
- finish-the-turnSkill
- incident-response-playbookSkill
- launch-readiness-gateSkill
- lead-developer-modeSkill
- lead-with-outcomeSkill
- lean-tool-useSkill
- migration-refactor-safetySkill
- plan-before-implementationSkill
- pr-and-commit-hygieneSkill
- product-delivery-bundleSkill
- product-minded-engineer-modeSkill
- reliability-bundleSkill
- reliability-incident-modeSkill
- review-quality-gateSkill
- run-guardrails-on-code-changesSkill
- security-bundleSkill
- security-minded-engineer-modeSkill
- staff-engineering-bundleSkill
- staff-engineer-modeSkill
- stakeholder-communicationSkill
- surgical-questionsSkill
- systematic-debuggingSkill
- test-disciplineSkill
- truthful-reportingSkill
- verify-by-exercisingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this bundle when you want a coherent senior-engineering operating mode rather than a single isolated skill.
- Distinctive: line 26
Add the guardrail skills that prevent premature completion, weak review, or poor execution.
- Distinctive: line 27
Add the communication skill when coordination or stakeholder clarity matters.
- Distinctive: line 28
Use the reliability or migration skill when the work creates operational risk.
- Distinctive: line 32
When this bundle is active:
- Distinctive: line 34
start with the outcome and the real problem
- Distinctive: line 36
keep the work moving without compromising rigor
- Distinctive: line 37
verify before claiming success
- Distinctive: line 40
Use this bundle as a capstone mode for senior execution across delivery, architecture, leadership, reliability, and launch work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Senior operating system
Use this bundle when you want a coherent senior-engineering operating mode rather than a single isolated skill. It combines the role-specific behavior, guardrails, and communication norms needed for a high-quality workflow.
How to use this bundle
Choose the preset bundle that matches the work at hand, then read and apply it. The bundle files are the source of truth for which skills each workflow activates:
- Delivery:
delivery-bundle— everyday implementation, bug fixes, and review - Architecture:
architecture-bundle— system shaping, design trade-offs, and major refactors - Staff engineering:
staff-engineering-bundle— cross-team coordination, leverage, and alignment - Reliability:
reliability-bundle— incidents, operational recovery, and hardening - Product delivery:
product-delivery-bundle— product-minded delivery with scope and launch discipline - Security:
security-bundle— trust-boundary work, security review, and hardening
The methodology skills (systematic-debugging, plan-before-implementation, verify-by-exercising, test-discipline, pr-and-commit-hygiene, decision-records) have trigger-oriented descriptions and load themselves when relevant; pull one in explicitly whenever its moment arrives.
Bundle principles
- Activate the role skill first.
- Add the guardrail skills that prevent premature completion, weak review, or poor execution.
- Add the communication skill when coordination or stakeholder clarity matters.
- Use the reliability or migration skill when the work creates operational risk.
Default operating posture
When this bundle is active:
- start with the outcome and the real problem
- make trade-offs explicit
- keep the work moving without compromising rigor
- verify before claiming success
- communicate the state clearly to the people who need to act
Use this bundle as a capstone mode for senior execution across delivery, architecture, leadership, reliability, and launch work.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.