engineer-subsystem
Turn a mechanical design brief into a saved CAD study, author or revise its model, and preserve requirements and failed measurements through Text-to-CAD.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 21
- Forks
- 15
01 前言 Front Matter
- name
- engineer-subsystem
- description
- Turn a mechanical design brief into a saved CAD study, author or revise its model, and preserve requirements and failed measurements through Text-to-CAD.
02 资源文件 1
- 参考文档agents/openai.yaml297 B
03 SKILL.md 正文
Engineer a subsystem
Use this workflow for a new mechanical part or the bundled drone assembly. Read the brief and compatibility. Resolve the plugin root two directories above this skill; assets must work from the installed package.
Establish the study
- Resolve the user's goal, interfaces, material assumptions and acceptance
limits. Record unresolved requirements. Choose
mechanical-partfor a custom single-solid part with supported measurements, ordrone-moduleonly for the two-part example. Do not force a new project into the drone dimensions. - Use
scripts/engineering.py. Inspect--helpas needed. New studies need an empty directory. Resume existing studies withresume STUDY;study.jsonis authoritative andcontext.mdis a generated summary. - Check Python 3.14 and
PE_RUNTIME. If needed, explain the dependency download and usesetup --runtime DIRin an authorized location. Preserve existing CAD installations and respect host permissions. - For a custom part, follow the model and requirements contract,
then run
init STUDY --profile mechanical-part --requirements FILE. Omitting the file provides a sensor plate starter. Save the functional brief and unresolved requirements insrc/brief.mdso handoffs retain them. Useinit STUDY --profile drone-modulefor the drone brief.
Author and revise
Implement the accepted brief in the study's src/model.py and export source.
The generic starter constructs a plate; replace it for another shape. Keep its
export contract. Use the separately installed Text-to-CAD authoring/viewing
capabilities for CAD work. Inspect externally supplied Python before execution.
Run build STUDY, then use verify-engineering-design. Model declarations and
rendered appearance are not acceptance measurements. A property unsupported by
the checker needs a separate measurement method; retain it as unresolved.
For a custom part, save revised requirements and run
change STUDY --requirements FILE --reason TEXT. For the drone example, use
--battery B or --frame-pitch-x 110. Never edit the installed checker or weaken
acceptance limits to make geometry pass. A changed requirement does not update
old geometry: verify it first, retain the actual result, then revise and build.
Keep failed runs. Routine repairs within the brief need no further approval; conflicting requirements need an explicit decision before alteration. Record real interventions; unknown usage or cost stays unknown.
Return
Summarize the selected profile/run, requirement revision, measured results and
next action. Show the actual CAD view when available. Use
prepare-engineering-handoff to regenerate deliveries. Distinguish the measured
geometry from unresolved manufacturing, structural and other physical checks.
04 同仓库更多 Skills
verify-engineering-design
Measure a study's CAD exports against its saved requirements, preserving failed or unknown results and the source, checker and artifact provenance.
prepare-engineering-handoff
Regenerate a study's checked CAD, source, measurements and BOM, then rebuild the delivered package in a separate destination and compare the results.
revise-pcba-assembly
Preview and apply a bounded, revision-bound PCBA placement or population correction using explicit authoritative geometry, then regenerate and recheck the assembly package.
review-pcba-package
Review supplied PCB assembly BOM and placement data, reconcile population and geometry evidence, and create a persistent local PCBA project with an offline visual assembly guide.
prepare-pcba-handoff
Export a consistent PCBA project into an immutable offline assembly packet and independently re-read its BOM, placements, provenance and artifact hashes before delivery.
recommend-review-reference-architecture
Recommend a conservative shadow-only review reference architecture from valid offline evidence. Use only when the user explicitly asks for a reference-architecture recommendation or uses the bundled synthetic fixture.