On this page
Arc Skills / Requirements
Open Source Requirements Review Tool
Arc Skills includes an MIT-licensed open source requirements review workflow focused on verifiability. Provide exact statements, controlled definitions and the intended product boundary. Your AI assistant reads the supplied material with available file tools and follows the skill to identify a credible evidence route, precise blockers and minimal wording or criterion proposals for an engineer to review.
Use this skill
Use Arc Skills to check whether the supplied requirements are verifiable.
Inputs:
- Requirement IDs, exact statements, revision, and controlled definitions
- Intended product boundary, article or model, and available observations
- Existing acceptance criteria and verification context
Return a per-requirement verdict, shortest credible evidence route, exact blocker, and minimal proposal.
Separate missing wording from missing test resources. Preserve the originals and leave unsupplied limits openSet up the toolkit · Read the skill instructions · Download the free toolkit · View on GitHub · MIT licence
What you provide and what you get
| What you have | How it is used | What you get |
|---|---|---|
| Controlled statements | Identifies actor, condition, response, and limit | Verifiability verdict |
| Definitions and criteria | Resolves event and observable boundaries | Specific wording or criterion gap |
| Article and access | Shows whether evidence can be gathered at this level | Plausible verification route |
Readable display versus timed fault indication
Illustrative engineering example.
Two illustrative display requirements are assessed on a Controller C2 prototype. A working screen is available, but the fault-detection timestamp source has not been defined.
R-1: The display shall be easy to read.
R-2: The display shall show fault code F within 1 s of fault detection.| Requirement | Verdict and shortest route | Exact blocker / proposal |
|---|---|---|
| R-1 | Not yet verifiable; human inspection or usability trial possible later | No reader, task, lighting, or pass boundary. Define those from approved use conditions. |
| R-2 | Conditionally verifiable; timed functional test | Fault detection start event and timestamp source undefined; retain the 1 s limit. |
| R-2 timing | Screen inspection alone is insufficient | A code visible at an arbitrary instant cannot demonstrate elapsed time ≤1 s. |
R-1 is understandable in ordinary language but gives two assessors no common decision boundary. R-2 contains a bounded observable outcome, so it needs event instrumentation rather than a new performance limit.
The third row explains method suitability for R-2 rather than counting another requirement. If the prototype lacks timestamp access, that is an evidence-resource issue; once the event is defined, the statement may still be sound.
Find the decisive observation
- Identify subject, trigger or state, observable response, and comparator in each statement.
- Check controlled definitions for terms that shift the pass boundary.
- Name a plausible inspection, analysis, demonstration, or test on the intended article.
- Distinguish missing requirement content from unavailable equipment or configuration.
Questions about this task
Does an existing Test link make a requirement verifiable?
No. A Test can be linked while missing the criterion or condition needed to decide the obligation.
Must every qualitative requirement be rewritten numerically?
No. Some attributes are inspectable with agreed qualitative criteria. Add numbers only when project intent supplies them.
Is this an automated open source requirements checker?
It is an open source skill for an AI assistant to follow. The assistant supplies the engineering reasoning and uses the available file tools to read your material. The output is a review proposal, and the responsible engineer decides whether the wording and evidence route are acceptable.
Can I use it without an ECSS or INCOSE standard?
Yes, for an engineering review of whether an observation could decide the stated obligation. A clause-level standards finding needs the applicable inspected edition and project context. The toolkit does not bundle licensed standards or certify compliance.
When does requirements review need a shared environment?
When several owners need to review proposed wording, retain decisions and keep criteria connected to current revisions, evaluate a shared programme environment such as Arc. Keep the assistant's findings separate from the approved requirement until the owner's review is complete.
Sources and further reading
- NASA Systems Engineering Handbook: Lifecycle and requirements guidance; the example decisions are illustrative.
- ECSS-E-ST-10-06C technical requirements specification: Official standard identification and scope; use the controlled edition for clause findings.
Once the requirement owner resolves a wording or acceptance gap, record the decision with the requirement revision and verification context. A shared programme record can keep the accepted statement and its evidence links available to design and test contributors.