Applied engineering disciplines
Skill r-irbe/proof-skills/skills/applied-engineering-disciplines
APM-installable agent skills for Lean 4 and Mathlib4 — proof tactics, math domains, review and research workflows, generic tooling.
npx -y skills add r-irbe/proof-skills --skill applied-engineering-disciplinesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
USE FOR: Engineering disciplines relevant to formal mathematical systems — control theory, systems engineering, reliability engineering, software verification, signal processing, and testing methodology. Use for bridging mathematical foundations to engineering practice, and for formalizing engineering requirements in Lean 4. DO NOT USE FOR: formal verification in Lean (use @lean-ai-formalization); security-specific engineering (use @applied-data-information-security); strategy analysis (use @applied-strategy-analysis). TRIGGERS: control theory, systems engineering, reliability engineering, software verification, engineering discipline.
SKILL.md
4.0 KB, as published. Nobody here has run it
Engineering Disciplines for Formal Mathematical Systems
Engineering methods and frameworks that connect formal mathematics to practical system design, verification, testing, and deployment.
Routing
- USE FOR: Engineering disciplines relevant to formal mathematical systems — control theory, systems engineering, reliability engineering, software verification, signal processing, and testing methodology. Use for bridging mathematical foundations to engineering practice, and for formalizing engineering requirements in Lean 4.
- DO NOT USE FOR: formal verification in Lean (use @lean-ai-formalization); security-specific engineering (use @applied-data-information-security); strategy analysis (use @applied-strategy-analysis).
- TRIGGERS: control theory, systems engineering, reliability engineering, software verification, engineering discipline.
Workflow
- Identify the discipline match: control theory, systems engineering, reliability engineering, or software verification.
- Pick the relevant section of the body; trace the chosen methodology end-to-end.
- Produce the engineering artifact (control law, FMEA, reliability budget) in the form the caller needs.
- Hand off: to
@lean-ai-formalizationfor formal proofs of correctness, to@math-nonlinear-dynamicsif control-theoretic dynamics dominate, to@lean-zettelkasten.
Recovery & STOP
- STOP if the question is about the formal-verification proof itself — delegate to
@lean-ai-formalization. - STOP if the discipline match is unclear — surface a clarifying question rather than guessing.
- STOP if the answer needs domain-specific data not in the body — escalate to
@research-council.
Handoffs
- Predecessors:
agent:gateway,skill:lean-research. - Successors:
skill:lean-ai-formalization,skill:lean-security-formalization,skill:math-nonlinear-dynamics.
Detailed reference
Full content for applied-engineering-disciplines lives in
references/applied-engineering-disciplines-handbook.md.
Load that file when the skill is convened; the SKILL.md only carries
the dispatch contract and the parts index.
| Section | Topic |
|---|---|
| Part 1 | Control Theory |
| Part 2 | Systems Engineering |
| Part 3 | Reliability Engineering |
| Part 4 | Software Verification & Testing |
| Part 5 | Signal Processing & Estimation |
| Part 6 | Engineering Process for Lean Projects |
| Part 7 | Configuration Management |
| Part 8 | Cross-References |
See also
../../references/applied-engineering-disciplines-handbook.md— Full handbook (extracted from this skill)../lean-ai-formalization/SKILL.md— Successor../lean-security-formalization/SKILL.md— Successor../math-nonlinear-dynamics/SKILL.md— Successor