Claude Skills by ashfordeOU

Use when prepare a structural test prediction report per ECSS-E-ST-32C Annex Q: determine predicted response quantities (displacement, load, stress, natural frequency) at each monitoring point for every test load case, derive safety-abort thresholds from scaled finite-element analysis outputs, verify that predicted peak responses fall within instrument measurement ranges, and establish the analysis-to-test correlation acceptance band for each monitored quantity. Trigger: ecss, e-st-32-structu...

Use when compute the dynamic response of a spacecraft structure to sine, random, or shock loading per ECSS-E-ST-32C clause 4.6.2.5: apply the dynamic amplification factor to a swept-sine excitation, derive the RMS and 3-sigma acceleration response to a random-vibration input via Miles' equation, evaluate the shock response spectrum for a half-sine pulse, or identify which analysis type applies to a given load event. Categorize each load event as sine, random, shock, or transient before select...

"Use when perform sine-sweep, random-vibration, and shock dynamic

Use when assemble an engineering analysis report to the ECSS-E-ST-10C Annex S content guideline so its result can be cited as verification evidence: confirm every required section carries content, confirm each input datum states where it came from, confirm the analysis tool is named with its qualification status, confirm every reported result carries an uncertainty, and confirm a compliance conclusion actually survives its own uncertainty against the limit. Trigger: ecss, e-st-10-system-scope...

Use when validate the analysis methods, tools and models behind a space system analysis before its results are used, under ECSS-E-ST-10C clause 5.3.4: decide whether a tool qualifies by heritage reuse or must be correlated, compute its correlation error against independently derived reference data, compare that error against the acceptance tolerance set by the analysis criticality, and aggregate every tool review into a single verdict on whether the analysis is valid. Trigger: ecss, e-st-10-s...

Use when produce or review a project technical budget report against the ECSS-E-ST-10C Annex I Document Requirements Definition: place every budget item in a recognized category, inflate its basic value into a current best estimate using the margin its design maturity earns, check each estimate against its allocated maximum, roll the estimates up per category and system-wide, apply the system margin, and decide whether the report satisfies the DRD. Trigger: ecss, e-st-10-system-scope, technic...

Use when consolidating technical budgets (mass, power, data rate, pointing, thermal, propellant, etc.) at system level under ECSS-E-ST-10C flow-down and applying the project margin policy: roll up contributor current-best-estimate plus maturity margin, add the system-level contingency margin, and check the result against the allocated value with a phase-appropriate minimum remaining margin. Trigger: ecss, e-st-10c, technical budget, budget consolidation, margin policy, mass budget, power budg...

Use when controlling an engineering change or nonconformance that may affect requirements or design under ECSS-E-ST-10C: assess whether it impacts the approved baseline, route it to the right approval authority, and gate implementation on an approved disposition with the baseline updated, consistent with M-ST-40 (configuration management) and Q-ST-10-09 (nonconformance control). Trigger: ecss, e-st-10c, engineering change, change request, nonconformance, ncr, m-st-40, q-st-10-09, baseline imp...

Use when determining the physical and functional grouping rules that govern how configuration items are assembled for integration under ECSS-E-ST-10C clause 5.4.2.3: check every pair of configuration items proposed for one physical assembly for mounting-zone match, hazard separation between energetic and non-energetic items, and EMI role conflict between a sensitive and an emitting item; flag a functional grouping conflict when items sharing a function group are physically incompatible; accou...

Use when establishing the functional, allocated, or product configuration baseline for a space system under ECSS-E-ST-10C clause 5.4.2.2: classify the baseline type, confirm every earlier baseline in the functional-then-allocated-then-product sequence is already established, verify the gating milestone review (SRR for functional, PDR for allocated, CDR for product) has passed, check that the baseline's required configuration-management artifacts are on record, and aggregate the findings per b...

Use when define or check the configuration content of a space product under ECSS-E-ST-10C clause 5.4.2.1 and Annex H: confirm the product tree resolves as a hierarchy with no dangling parent and no cycle, allocate every function of the function tree to a real product-tree node, confirm each leaf node performs at least one function and carries a design definition, and confirm the assembly constraints reference only real nodes in an acyclic precedence order. Trigger: ecss, e-st-10-system-scope,...

Use when engineering data across an ECSS-E-ST-10C programme (system level) needs to be checked for consistent use of reference coordinate systems per E-ST-10-09 and SI units, before it is exchanged between disciplines, suppliers, or verification/operations teams. Trigger: coordinate system, reference frame, SI units, unit consistency, coordinate systems document, CSD, E-ST-10-09, frame consistency, ecss, e-st-10c.

"Use when validating or generating a Design Definition File

Use when produce or maintain the Design Definition File (DDF) for a space system product under ECSS-E-ST-10C clause 5.4.1.4 and Annex G: classify each DDF content item into its section (design description, budget, or interface data), compute a budget item's margin against the minimum margin required at the current review milestone, verify each interface data item declares a valid mating product, confirm every mandatory DDF section is populated for the product, and determine whether the produc...

Use when convert a heritage programme's legacy design data pack onto the ECSS document set following the ECSS-E-ST-10C Annex R mapping guidance: validate each legacy item's disposition, confirm a carried-forward item names at least one recognized ECSS target document, confirm a retired item states why and claims no target, and walk the mapping in the opposite direction to find any owed ECSS document that no legacy content feeds. Trigger: ecss, e-st-10-system-scope, legacy-data-pack, annex-r-m...

Use when planning or checking which systems-engineering documents a space project must deliver or re-baseline at each review milestone per ECSS-E-ST-10C Annex A (informative): build the document-by-review delivery schedule, verify a given review's deliveries against it (missing and unplanned deliveries), and roll up readiness across the whole review sequence. Trigger: delivery schedule, document delivery per review, Annex A, review deliverables, MDR PRR SRR PDR CDR QR AR FRR CRR ER documents,...

Use when allocate technical budgets (mass, power, data rate, link, pointing, thermal, or any other quantifiable design resource) for a space system under ECSS-E-ST-10C clause 5.4.1.2 and Annex I: determine the minimum required margin for the project's current life-cycle phase, track each item's current best estimate against its allocation and the phase's required margin, verify that sub-item allocations sum within the parent system-level allocation, and check the system-level margin on the su...

Use when conduct and document a product's design against its allocated Technical Requirements Specification under ECSS-E-ST-10C clause 5.4.1.1: confirm every allocated requirement is covered by at least one design definition item, confirm every design item traces back to a known requirement, and confirm every design decision records the alternatives considered, the option selected and the rationale for selecting it, then decide whether the product's design is complete for the assessment. Trig...

Use when select and validate the design methods, tools and models behind a design output under ECSS-E-ST-10C clause 5.4.1.3: separate model-based methods from rule-based ones, establish each model's validation status against the domain of applicability of the present design case, weight the confirmation each model contributes and compare the total against the threshold in the method selection plan, and confirm a recorded rationale exists wherever a design rule is applied outside its documente...

Use when assemble or review a product Design Justification File against the ECSS-E-ST-10C Annex K Document Requirements Definition: validate each justification record's method and review status, confirm every record cites the document its evidence lives in, resolve each requirement to justified, open, rejected-evidence or no-evidence under a severity ordering, surface a requirement whose accepted argument rests on similarity alone, and decide whether the file supports the design. Trigger: ecs...

Use when manage a space project's engineering data items under ECSS-E-ST-10C clause 5.6.3 consistently with the ECSS-M-ST-40 configuration identification scheme: parse and check an item identifier against its declared type, originator and revision, place the item in a controlled repository with a retention period, link it to a configuration baseline before distribution is authorized, and report which items in the register are still short of configuration control. Trigger: ecss, e-st-10-system...

"Use when you define the natural and induced environments a

Use when generate or validate a system function tree against the ECSS-E-ST-10C Annex H Document Requirements Definition: confirm the functional breakdown resolves as a single-rooted, fully connected hierarchy with unique identifiers and resolvable parent links, confirm each function is named with a bare action verb plus an object, reject a level that splits into a single pass-through child, and confirm every elementary function traces to a requirement and is allocated to exactly one system el...

Use when you identify and control system-level interfaces under ECSS-E-ST-10C clause 5.6.4: catalog each interface between two interfacing elements, classify its physical domain (mechanical, electrical, thermal, data, fluid) and reject an unrecognized domain, determine whether it crosses an internal or external responsibility boundary and which control document ECSS-E-ST-10-24 requires as a result, draft the interface requirement document (IRD) before the interface matures, define the interfa...

Use when generating or validating a Mission Description Document (MDD) for a European space project per ECSS-E-ST-10C Annex B: check that the required sections (objectives, mission statement, mission scenario, constraints) are present, that the mission statement carries an objective/target/timeframe, that the mission scenario phases follow the launch-to-disposal order, and that every constraint is categorised (programmatic, technical, operational, environmental) before the MDD is handed off a...

Use when checking per-phase system engineering task lists and outputs under ECSS-E-ST-10C: confirm the project's tasks for lifecycle phases 0 through F (mission analysis through disposal) are identified and tracked against the System Engineering Plan (SEP) deliverables. ECSS-E-ST-10C clause 4.3.3-4.3.9 gives the informative per-phase task overview. Trigger: ecss, e-st-10c, phase task, lifecycle phase, phase 0, phase A, phase B, phase C, phase D, phase E, phase F, systems engineering, 4.3.3, s...

Use when applying the ECSS-E-ST-10C clause 7 pre-tailoring matrix to a space project: for the project's declared space product type (e.g. space segment, ground segment, launch service segment element), determine which clause-5 system-engineering requirements are applicable, optional, or not applicable, before project-specific tailoring per ECSS-S-ST-00-01. Checks the matrix itself is complete and well-formed, and checks the project's carried-forward requirement clauses against the resolved ap...

Use when verify a product against its Technical Specification and close the verification out under ECSS-E-ST-10C clause 5.5.2: confirm each requirement carries at least one recognized verification method, resolve each assigned method to a status from its recorded objective evidence, partition the product's requirements into verified, open, failed and no-method-assigned, and decide whether the verification file supports close-out. Trigger: ecss, e-st-10-system-scope, product-verification, veri...

Use when produce or review a Product User Manual against the ECSS-E-ST-10C Annex P Document Requirements Definition: confirm the manual declares the product configuration it describes and that it matches what was delivered, confirm every required section is present and not empty, confirm procedure steps are numbered contiguously without repeats, confirm every hazardous step carries its warning ahead of the step, and confirm each maintenance task states its interval and required resources. Tri...

Use when drive the customer and supplier sign-off loop on a technical requirements specification under ECSS-E-ST-10C clause 5.2.3.7: determine who must sign, check each party's recorded review against the specification's current baseline revision, separate a stale agreement from an open comment and from a party that has not responded, flag a review left open beyond the agreed review period, and decide whether the specification is agreed. Trigger: ecss, e-st-10-system-scope, requirements-agree...

Use when allocating requirements to functions and to product-tree elements (configuration items) under ECSS-E-ST-10C: run functional analysis to establish the function tree, allocate each requirement to the function(s) it drives, allocate each requirement to the configuration item(s) that implement it, and check allocation completeness (no unallocated requirement, no orphan function or element) before the requirement baseline is frozen. ECSS-E-ST-10C clause 5.2.3.5 governs requirement allocat...

Use when analysing customer or upper-level requirements to derive, generate, control and document the requirement set for a space system and for each lower level, per ECSS-E-ST-10C clause 5.2.1. Checks that every requirement traces to a customer requirement or an existing upper-level requirement (no orphans), carries identifying text and rationale (documented), and is under configuration control (released or baselined). Trigger: ecss, e-st-10c, requirement analysis, derive requirements, requi...

Use when establishing or controlling the requirements baseline for a configuration item (CI) under ECSS-E-ST-10C clause 5.2.3.9: classify each requirement's approval status ahead of an agreed baseline milestone, verify it carries requirement text and a verification method, identify duplicate requirement identifiers within the set, define the baseline record once every requirement in the set is ready, and validate every subsequent addition, modification, or deletion of a baselined requirement ...

Use when identify and resolve internal inconsistencies inside a requirement baseline under ECSS-E-ST-10C clause 5.2.3.6: reduce each requirement that bounds a shared parameter to the feasible interval its constraint implies, intersect the intervals of a group to find a parameter no value can satisfy, and compare every requirement binding on a shared interface attribute to find the same attribute given two different values. Trigger: ecss, e-st-10-system-scope, requirement-consistency, conflict...

Use when a requirement subject is common to several next-lower-level products in an ECSS-E-ST-10C specification tree and must be consolidated into a support specification instead of repeated per product, or when the same requirement flows down to two or more products with conflicting values and the conflict must be resolved before the requirement baseline is set. ECSS-E-ST-10C clause 5.2.3.2 governs requirement consolidation and flow-down conflict resolution. Trigger: ecss, e-st-10c, requirem...

Use when maintaining ECSS-E-ST-10C requirements under configuration control (clause 5.2.3.8): determine whether a requirement's lifecycle state transition (draft, proposed, baselined, obsolete) is allowed, verify that a change to a baselined requirement carries an approved change request before it is applied, assess the change's impact on derived requirements found via the parent-child traceability link and on verification items linked to the requirement, and confirm the impact assessment and...

Use when assessing the technical/requirement risk of a candidate or derived requirement during ECSS-E-ST-10C flow-down: determine likelihood x severity into a risk class, feed the project risk register, and gate baselining on a defined mitigation for medium-and-above risk consistent with M-ST-80. Trigger: ecss, e-st-10c, requirement risk, risk register, risk analysis, technical risk, mitigation, m-st-80, risk index, likelihood severity.

Use when maintaining bidirectional requirement traceability under ECSS-E-ST-10C: keep the requirements traceability matrix (RTM) aligned across customer requirements, derived requirements, allocated products and verification records, and detect broken, missing or dangling trace links before review gates. ECSS-E-ST-10C clause 5.2.2 governs requirement traceability as part of system engineering requirement flow-down. Trigger: ecss, e-st-10c, requirement traceability, RTM, trace matrix, bidirect...

Use when every requirement in an ECSS-E-ST-10C requirements set needs a verification method (test, analysis, review-of-design, inspection) and a verification level (equipment, subsystem, element, segment, system) assigned before verification planning, consistent with E-ST-10-02 verification methods/levels and E-ST-10-03 testing. Trigger: verification method, review of design, ROD, verification level, test analysis inspection, verification matrix, E-ST-10-02, E-ST-10-03, requirement verificati...

Use when managing technical risk for a space project under ECSS-E-ST-10C clause 5.6.8: identify a risk, analyse it into a likelihood x severity risk class, plan and record mitigation actions for risks that require them, assess the residual risk left after mitigation, and escalate residual risk that remains above the acceptable band for formal acceptance, in coordination with the ECSS risk-management standard M-ST-80. Distinct from the sibling e10-req-risk-analysis leaf, which scores risk per ...

Use when compile or audit a Requirements Justification File against the ECSS-E-ST-10C Annex O Document Requirements Definition: validate each requirement's derivation basis, confirm a parent-derived requirement names its parent and that a top-level requirement rests on a standard or mission need instead, detect a rationale that merely restates the requirement it is meant to justify, confirm each rationale is attributed, and decide whether every requirement is justified. Trigger: ecss, e-st-10...

Use when build or audit a requirements traceability matrix against the ECSS-E-ST-10C Annex N Document Requirements Definition: confirm every row carries its DRD fields, trace each derived requirement upward to a parent that exists in the matrix, trace each requirement that must flow down to at least one child, detect parent-pointer cycles, and confirm each allocation names a real product-tree element and each verification method is one of the four recognized ones. Trigger: ecss, e-st-10-syste...

Use when preparing a System Concept Report (SCR) for a European space project per ECSS-E-ST-10C Annex C: validate that the required sections (candidate concepts, trade summary, feasibility assessment, recommended concept) are present, that every candidate concept carries a description, that the trade summary scores every candidate against all trade criteria (technical, programmatic, cost, risk), that every candidate carries a valid feasibility verdict, and that the recommended concept is a kn...

Use when manage the system engineering activities, responsibilities and interfaces of the SE function as defined in the System Engineering Plan (SEP) under ECSS-E-ST-10C clause 5.6.1: categorize each SE activity by kind, determine its assigned responsible role against the SEP responsibility assignment, verify each activity's required interfaces to other project functions (project management, product assurance, engineering disciplines, customer) are on record, and track activity status so a bl...

"Use when plan the systems engineering (SE) activities and

Use when you must generate or validate a System Engineering Plan (SEP) document against its document-requirements-definition (DRD) per ECSS-E-ST-10C Annex D: check the document carries every mandatory content block (introduction, applicable/reference documents, SE organisation, SE processes, SE tasks, DRD linkage), that every organisation interface (product assurance, AIV, risk management, configuration management, software engineering) is covered by an assigned role, that every task has a kn...

Use when you must produce or maintain the System Engineering Plan (SEP) for a European space project per ECSS-E-ST-10C: decide when a lifecycle event forces the SEP to be revised, check that lower-level plans (product assurance, AIV, risk management, configuration management, software management) stay baseline-consistent with the SEP, and assemble the SEP-derived support package the SE function hands the project manager (PM) at each review gate. Produces the maintenance-trigger verdict, the p...

Use when generate or validate a project specification tree against the ECSS-E-ST-10C Annex J Document Requirements Definition: confirm the tree is singly rooted, fully connected and free of duplicate identifiers, confirm each specification sits exactly one level below its parent, confirm every product-tree node carries exactly one specification, and confirm every non-root specification declares the parent it flows its requirements down from. Trigger: ecss, e-st-10-system-scope, specification-...

Use when establishing or maintaining the specification tree of a space product decomposition per ECSS-E-ST-10C clause 5.2.3.1c and Annex J: mirror the product tree with one technical specification per node (support specifications included), check the tree has no orphan or duplicate specs, and confirm every spec's parent link matches the product tree's parent-child structure. Trigger: specification tree, spec tree, product decomposition, support specification, ECSS-E-ST-10C 5.2.3.1c, Annex J.

Use when scoping and scheduling ECSS-E-ST-10C system analyses for a space project: classify a required system analysis as mission, functional, interface, environmental, or operational, determine which analysis types a given project phase requires, verify each analysis definition carries a non-empty objective and defined outputs, and check whether an analysis is scheduled early enough to feed the phase that first requires it. Trigger: ecss, e-st-10-system-scope, system-analysis, mission-analys...