Define mechanical requirements from system requirements and system architecture. Trigger: When system requirements and system architecture are approved and mechanical requirements shall be defined.
After system requirements and system architecture are approved.
When any mechanical requirements activity is required.
Critical Patterns
Shall strictly follow the provided resources and recursively review all referenced documents required to understand the current process, inputs, outputs, rules and directly referenced work products.
Shall align with system requirements and system architecture (no inconsistencies).
Shall ensure all mechanical requirements are derived from system requirements and system architecture by adding explicit traceability between them.
Shall avoid embedding design implementation details in mechanical requirements.
Shall keep documentation DRY (Don't Repeat Yourself) by adding references instead of duplicating content.
Shall ask for approval when mechanical requirements are incomplete, ambiguous, or conflicting.
Shall request final validation before closing the mechanical requirements to ensure no further iterations are needed.
Resources
相关技能
Documentation: See references/docs.md for resources needed to perform this skill.