跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

file-requirement

File or triage a LET requirements issue. Use when opening, rewriting, or reviewing a requirement; when an issue names a commercial product to copy; or when the user runs /file-requirement.

linux-engineering-tools · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add linux-engineering-tools/community --skill file-requirement

技能说明


name: file-requirement description: File or triage a LET requirements issue. Use when opening, rewriting, or reviewing a requirement; when an issue names a commercial product to copy; or when the user runs /file-requirement.

File or triage a requirement

Use the Requirement issue form in this repo. Do not open a blank issue. Spell out a term on first use, or link TERMS.md.

Write the issue

Required substance (map to form fields):

  • Job — who, what they are finishing, how often. No commercial feature names.
  • Inputs/outputs/standards — published specs (ISO 10303 STEP, Drawing Exchange Format (DXF), ISO geometrical product specifications (GPS), ASME Y14.5, IPC, G-code dialect). Not vendor-internal formats.
  • Acceptance tests — observable, preferably command-line interface (CLI) + fixtures (in-tree sample files).
  • Existing free and open-source software (FOSS) — from catalog/README.md. Say whether this should go upstream. File on the catalog Forge URL, not a GitHub mirror of GitLab or Savannah.
  • Graphical user interface (GUI)? — if yes, the desktop contract applies (agents/skills/omarchy-desktop/SKILL.md) before incubation.

Title: [req] plus the job in a few words.

Labels: type:requirement, status:needs-triage, domain:<name>, ip:clean if the form checks passed.

Map domain → space with SPACES.md. Check that space’s catalog page first (Forge and Display columns). Display notes are not Omarchy tests.

  • cad parametric solids; mesh polygon/sculpt (not a FreeCAD clone of Blender, not the reverse)
  • cam toolpaths; cnc machine control; print slice/host/firmware
  • eda schematic/PCB; bench instruments and repair (sigrok / lxi-tools first)
  • process flowsheet / DEXPI; automation IEC 61131 tests / industrial I/O (not a vendor runtime clone)

Catalog questions belong in Discussions in that space, not as issues.

Rewrite product-named drafts

If the draft says “like Product X” or names a vendor feature:

  1. Keep the job (what the engineer must finish).
  2. Drop product, feature, and menu names.
  3. Replace with standards and tests.
  4. If that is impossible because the submitter only has a clone in mind, close as not a LET requirement and point at CONTRIBUTING.md.

Never paste the proprietary detail you are removing into a comment.

Triage

ObservationAction
Clone-spec or commercial UI screenshotsClose; ip:flagged
Proprietary source / NDAStop; ip:flagged; do not quote the material
Valid job, missing tests or standardsAsk for those; keep status:needs-triage
Existing FOSS can take itLabel type:upstream, status:upstream-first; link that project
Needs a spec before codestatus:needs-spec; point at specs/
Agent-drafted, no human namedAsk for the accountable human; do not merge/accept without one

Do not incubate a repo from a requirement issue. That is an RFC plus agents/skills/incubate-tool/SKILL.md.