Manage space engineering requirements in a human-readable, trackable format. Use this skill whenever the user wants to define, update, trace, or review system requirements, component specifications, verification criteria, mass/power budgets as requirements, or perform traceability audits. Trigger for "requirement," "specification," "shall statement," "traceability," or "requirements review."
Read
CONVENTIONS.mdat the repo root before proceeding.
This skill defines how to manage engineering requirements. It is the foundation skill — every other skill checks requirements before doing analysis.
Ask the user (if not already known):
/requirements/ at project root.Requirements change frequently. They should be easy to read, easy to diff in git, and easy to parse by scripts if needed. We use Markdown with structured blocks.
### [REQ-PWR-001] Minimum Battery Capacity
**Status**: DRAFT | APPROVED | VERIFIED
**Parent**: [REQ-SYS-050]
**Verification Method**: Test | Analysis | Inspection | Demonstration
The spacecraft shall have a minimum usable battery capacity of 1500 Wh at end-of-life (EOL) to support eclipse operations.
**Rationale**: Based on worst-case eclipse duration of 35 minutes and average power draw of 2 kW, with 20% margin.
Store requirements by subsystem in /requirements/:
requirements/system_level.md — Top-level mission and system requirementsrequirements/power_system.md — EPS requirementsrequirements/thermal.md — Thermal requirementsREQ-[SUBSYSTEM]-[NUMBER] — e.g., REQ-PWR-001, REQ-STR-003, REQ-SYS-100.
**History**: note summarizing the change.When a domain skill (e.g., thermal-assessment) derives a requirement from analysis:
/requirements/v-and-v-manager (for verification closure)