# Engineering Operating System

> Engineering Operating System

- Skill: `lucadominguez/engineering-operating-system` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lucadominguez/engineering-operating-system`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lucadominguez/engineering-operating-system/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lucadominguez (https://skillmd.com/u/lucadominguez)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lucadominguez/engineering-operating-system

---

# Engineering Operating System

## Purpose

Use this as a lightweight router for engineering work. It borrows the useful parts of Superpowers and Agent Skills without making every task follow a full heavyweight process.

## Rule of Precedence

Project-specific skills and repo instructions win over this skill. If a project skill conflicts with this router, follow the project skill.

## Start Here

Before choosing a workflow, classify the request:

- Tiny change: inspect, edit, verify. Do not force a formal plan.
- Ambiguous feature: clarify intent, then use writing-plans when implementation is likely.
- Debugging/failing test: load systematic-debugging before proposing fixes.
- Framework/library-specific code: load source-driven-development and verify current official docs.
- UI/browser work: load rontend-ui-engineering; use browser verification when available.
- Security-sensitive work: load security-and-hardening before implementation and again before completion.
- Completion claim, commit, PR, or handoff: load erification-before-completion.
- Code review request: load 
equesting-code-review.
- Test-first requested or risk is high: load 	est-driven-development.

## Operating Modes

### Fast Path

For simple edits, avoid ceremony:

1. Read the relevant files.
2. Make the smallest coherent change.
3. Run the narrowest meaningful verification.
4. Report exactly what changed and what was verified.

### Feature Path

For feature-sized work:

1. Clarify the user-facing outcome.
2. Inspect existing patterns.
3. Write or follow a short plan.
4. Implement incrementally.
5. Verify behavior with tests, build, browser, or direct command output.
6. Review for regressions before claiming completion.

### Debug Path

For bugs:

1. Reproduce or inspect the failure evidence.
2. Find root cause before changing code.
3. Make the minimal fix.
4. Verify the original symptom is gone.
5. Add or update a regression check when practical.

## Constraints

- Do not make worktrees, subagents, or formal TDD mandatory unless the task justifies them.
- Do not load every related skill. Load the smallest set that materially improves the task.
- Do not claim completion without fresh verification evidence.
- Keep project momentum higher priority than ritual.