Claude Skills by ashfordeOU

Use when scoping or gating European space systems engineering per ECSS-E-ST-10C: determine the lifecycle phase (0 through F), map each phase to its review gate (MDR, PRR, SRR, PDR, CDR, QR, AR, FRR, CRR, ER), and validate that a phase is ready to exit when its required review records are complete. The phase-gate sequence drives program planning and procurement milestones for space systems, from mission analysis through disposal. Trigger: ecss, e-st-10c, lifecycle phases, phase gate, mdr, prr,...

Use when generating or validating the Technology Matrix deliverable per ECSS-E-ST-10C Annex F: check the document carries the required DRD sections, each listed technology carries the required matrix fields (name, current TRL, target TRL, mission applicability), TRL values are valid (integer 1-9) and non-regressing (target TRL at or above current TRL), and mission applicability is resolved rather than left blank or TBD. Trigger: ecss, e-st-10c, technology matrix, trl, technology readiness lev...

Use when identifying critical technologies for a space project under ECSS-E-ST-10C clause 5.6.7, assessing their Technology Readiness Level (TRL) per E-AS-11 (ISO 16290), building the technology matrix, and defining the development plan that closes the gap to the TRL required for the project. Trigger: ecss, e-st-10c, technology plan, technology matrix, trl, technology readiness level, iso 16290, e-as-11, technology risk, critical technology, annex e, annex f.

Use when you must generate or validate the Technology Plan (TP) for a European space project per ECSS-E-ST-10C Annex E: check the draft TP against the required DRD content blocks, assess each critical/enabling technology's TRL entry (current vs. target TRL, assessment-due date vs. need-by date), roll up the technology development schedule, and decide whether the TP is ready to submit or needs revision. Produces the completeness verdict, per-technology TRL/schedule verdicts, and the overall TP...

Use when produce or review a trade-off report against the ECSS-E-ST-10C Annex L Document Requirements Definition: validate that the criterion weights form a normalized set, confirm every option carries a score against every criterion rather than defaulting a gap to zero, compute the weighted ranking and the margin to the runner-up, test whether shifting any single weight flips the winner, and decide whether the report reaches a defensible recommendation. Trigger: ecss, e-st-10-system-scope, t...

Use when comparing candidate solutions to a system engineering decision under ECSS-E-ST-10C clause 5.3.3 and Annex L: define the evaluation criteria and their weights, score each candidate against every criterion on a common scale, gate any candidate that fails a mandatory pass/fail criterion, rank the remaining candidates by weighted score, and flag when the recommendation is a close call sensitive to the weighting assumptions rather than a clear-cut winner -- then record the result as a tra...

Use when flowing customer technical requirements down to next-lower-level technical requirements specifications (TRS) per ECSS-E-ST-10C clause 5.2.3.1: check every customer TS requirement reaches at least one child TRS, that no child TRS value contradicts the parent TS or a sibling TRS, and that each TRS carries the document structure expected by E-ST-10-06. Trigger: ecss, e-st-10c, trs flowdown, technical requirements specification, requirement flow-down, customer TS, next-lower-level requir...

Use when plan and manage system-level product verification under ECSS-E-ST-10C clause 5.5.1, consistently with the verification process of E-ST-10-02 and the testing scope of E-ST-10-03: assign recognized verification methods to a system requirement, link its approach back to the verification policy in the System Engineering Plan, track each method to a status, require an evidence reference before any method counts as closed, and aggregate the methods into the requirement's verification statu...

Use when running the acceptance stage of ECSS-E-ST-10-02C verification for a flight (or protoflight) article: gate the article on flight-standard workmanship/configuration eligibility, apply the acceptance-article rules distinguishing a dedicated acceptance test (prototype philosophy) from protoflight credit, guard against an acceptance test overstepping its qualified margin, disposition the workmanship/performance outcome, and close out the stage across a product set. Anchor: E-ST-10-02C cla...

Use when determine whether an analysis report actually verifies its requirement under ECSS-E-ST-10-02 clause 5.3.2.2: confirm the analysis was run against the design baseline under verification rather than a superseded model, confirm every case the requirement's envelope demands was analysed and flag cases that drifted outside it, confirm each case carries a verdict and that a case not run states why, and roll the case results up to a requirement verdict. Trigger: ecss, e-st-10-02c, analysis-...

Use when defining the verification approach under ECSS-E-ST-10-02C clause 5.2.1: decide which requirements enter verification, check whether a chosen method is applicable at a given life-cycle stage, assess the risks for requirements that cannot be verified by test and the mitigations for them, validate a per-requirement strategy, roll closure status up by verification level, and confirm the plan is complete. Trigger: ecss, e-st-10-02c, verification approach, verification strategy, method app...

Use when consolidate verification close-out documentation under ECSS-E-ST-10C §5.4.4.2: gather all verification reports at the applicable review milestone, merge per-requirement verification statuses into a consolidated register, identify requirements that failed or were not verified and determine whether each needs a waiver or a deviation, draft register entries with technical justification and risk-level tag, and confirm every requirement carries a final disposition (Pass, Fail, Waived, or ...

Use when control and close out product verification under ECSS-E-ST-10-02 clause 5.4.1: confirm every verification control document row reached a closed status with evidence cited, confirm each closure taken against a waiver names a waiver the authority actually approved, confirm no nonconformance is still open, and confirm the verification database was delivered machine-readable in the agreed format covering every row the control document holds. Trigger: ecss, e-st-10-02c, verification-close...

Use when execute verification activities against the verification plan and control document under ECSS-E-ST-10-02 clause 5.3.1: confirm every readiness condition holds before an activity starts, suspend it while any nonconformance raised against it stays open, confirm each departure from the approved procedure was authorized before execution rather than after, reconcile the as-run steps against the as-planned steps, and derive the activity's true state from its own record. Trigger: ecss, e-st...

"Use when qualifying an integration and test facility or a test

Use when ground support equipment (GSE) will interface with flight hardware during verification and needs to be qualified as verification tooling before use, consistent with ECSS-E-ST-10-02C clause 5.2.6.2 (GSE qualification) and the general tool-qualification regime of clause 5.2.6.1. Classifies GSE as mechanical (MGSE) or electrical (EGSE) and determines the required qualification actions (interface control document, proof test, periodic re-proof, interface safety verification, calibration ...

Use when a flight item has requirements that cannot be fully closed on the ground and must be verified once on orbit under ECSS-E-ST-10-02C clause 5.2.4.5: identify which requirements need the in-orbit stage, close them out against commissioning evidence, and reopen a previously closed requirement for re-verification when an in-orbit anomaly affects it. Trigger: in-orbit verification, commissioning, on-orbit performance, anomaly re-verification, post-launch checkout, e-st-10-02, verification ...

Use when produce or audit an inspection report against the ECSS-E-ST-10-02 clause 5.3.2.4 and Annex E Document Requirements Definition: judge each variable characteristic against its own tolerance band with the limits included, take an attribute characteristic's recorded result, confirm the measuring equipment held a calibration valid on the day the measurement was taken, confirm the inspector appears on the qualified roster, and separate characteristics never inspected from those inspected a...

Use when a product tree needs its verification levels defined and every requirement needs a verification level assigned before verification planning under ECSS-E-ST-10-02C: build the equipment/subsystem/element/segment/system hierarchy, assign each requirement to the level of the component(s) it is allocated to, and check whether a level is ready to close out. Trigger: verification level, verification levels, equipment subsystem element segment system, product tree, common ancestor, level clo...

Use when determine which ECSS-E-ST-10-02C clause 5.2.2.3 analysis technique (worst-case, statistical, qualitative, classical calculation, or similarity) applies to a requirement being verified by analysis, validate the heritage conditions that must all hold before a case can close by similarity to a previously verified reference item -- verified reference item, design/manufacturing equivalence, and an enveloped operating environment -- check an analysis plan for the fields a closure review re...

Use when you need to determine which verification method or combination of methods -- test, analysis, review-of-design, inspection -- satisfies a requirement under ECSS-E-ST-10-02C clause 5.2.2.1: categorize the requirement, filter to the methods eligible for that category, enforce that a safety-critical requirement always carries test, apply the test-over-analysis-over-review-of-design-over-inspection precedence rule with a stated rationale whenever a more rigorous eligible method is skipped...

Use when applying the inspection verification method under ECSS-E-ST-10-02C clause 5.2.2.5: categorize each checklist item as a visual or measurement inspection technique, decide whether inspection may be used for a given requirement, evaluate a visual item outcome and a measurement item outcome against their criteria, check the inspection programme's completeness in the verification plan, and roll the item statuses up to an overall inspection verdict. Trigger: ecss, e-st-10-02c, inspection m...

Use when verify a requirement's compliance under the review-of-design method of ECSS-E-ST-10-02C clause 5.2.2.4: classify each design-evidence item (drawing, analysis report, design description, supplier certificate, heritage data, similarity data) as direct or heritage evidence, apply the admissibility rule for a safety-critical requirement backed only by heritage evidence, roll up each item's compliant, non_compliant, open, or not_applicable disposition into an overall requirement status, a...

"Use when determine whether the test method can serve as the

Use when a space project must define its verification model philosophy under ECSS-E-ST-10-02C: choosing prototype vs protoflight, listing the physical models (STM, EM, QM, PFM, FM, EQM) with purpose/configuration/stages for the Verification Plan, checking a model is representative of the item it stands in for, and flagging re-verification after a design change. Trigger: model philosophy, prototype model, protoflight, qualification model, flight model, engineering model, model list, verificati...

Use when determine which other ECSS-E-ST-10-02C verification planning documents (the interface to the AIT plan, the analysis plans) are required for a set of requirements based on the verification method assigned to each one, check every required document against its minimum content fields and against full cross-reference coverage of the requirement identifiers assigned to its method, track each document's draft/in_review/approved status, and roll up an overall other-planning-documents readin...

Use when decide whether a verification activity needs documentation beyond the four report DRDs under ECSS-E-ST-10-02 clause 5.3.2.6, and check what is produced: derive the need from the activity's own trigger conditions rather than preference, confirm any additional report carries the minimum identification that makes it citable, confirm its author did not also approve it, and flag a report that restates the scope of a DRD report already produced for the same activity. Trigger: ecss, e-st-10...

Use when phasing verification activities with the project life cycle under ECSS-E-ST-10-02C clause 5.2.7: locate a life-cycle phase in the project phase sequence, decide whether a phase carries a verification output requirement, list the outputs that phase owes and the gaps against them, check entry readiness for a target phase, rank per-requirement verification maturity, roll that up to a project-wide status, and run the full phasing review. Trigger: ecss, e-st-10-02c, verification phasing, ...

Use when an element's mission profile includes physical return of hardware to Earth (descent capsule, sample-return canister, recoverable payload, splashdown-recovered stage) and the post-landing verification stage of ECSS-E-ST-10-02C must be run: confirm applicability, assess each recovered item's condition against its pre-flight baseline, flag safety-critical findings, and track items that could not be recovered for alternate evidence. Trigger: post-landing verification, recovery, returned ...

Use when a flight item needs a pre-launch readiness go/no-go before launch under ECSS-E-ST-10-02C: transport-induced damage check, storage/shelf-life and environmental-excursion check, launch-site health/functional checks, and as-built launch configuration vs qualified/accepted baseline. Trigger: pre-launch readiness, launch readiness review, LRR, transport check, shelf life, storage excursion, launch-site checkout, launch configuration, as-built vs baseline, verification stage, E-ST-10-02, e...

Use when apply the ECSS-E-ST-10-02C §6 pre-tailoring matrix to a space product type: determine the applicability level (applicable, recommended, optional, or not applicable) for each clause-5 verification requirement for the product category under assessment, identify every applicable requirement that must be covered, flag any applicable verification requirement absent from the project's captured requirement set, and produce the per-requirement applicability record for engineering review. Pro...

Use when running the verification process as a customer-supplier activity under ECSS-E-ST-10-02C clause 5.1: validate the product level, life-cycle phase, activity status and document type of each verification activity, assign the executor and the closure approver by role, determine which documents a phase still owes before it can close, roll individual activity statuses up to a single process status, and verify a closure sign-off against the activity's required evidence. Trigger: ecss, e-st-...

Use when running the qualification stage of an ECSS-E-ST-10-02C verification programme: closing design qualification against requirements before acceptance/QR, tailoring the qualification scope by product heritage category (Table 5-1: new design, unmodified heritage within envelope, modified or envelope-exceeding heritage), and confirming every product in scope is closed with matching evidence. Trigger: qualification stage, design qualification, heritage product category, Table 5-1, qualifica...

"Use when determine whether a previously verified hardware item

Use when produce or audit a review-of-design report against the ECSS-E-ST-10-02 clause 5.3.2.3 and Annex D Document Requirements Definition: confirm the review panel exists and is independent of the design authors by identity rather than by declaration, confirm every reviewed document is pinned to a revision, confirm each checklist item carries a result with an adverse item dispositioned and a not-applicable item justified, and close the review only when nothing adverse remains open. Trigger:...

Use when a simulator (functional, real-time, or closed-loop / hardware-in-the-loop) is used to generate verification evidence under ECSS-E-ST-10-02C and its own qualification status needs to be established before that evidence can be credited: which fidelity evidence a simulator's role requires, whether it is currently qualified, and whether a design or interface change triggers re-qualification. Trigger: simulator qualification, functional simulator, real-time simulator, closed-loop simulato...

Use when defining verification stages for a product under ECSS-E-ST-10-02C: qualify, accept, verify pre-launch, in-orbit (incl. commissioning) and post-landing each with its objective and applicability to the product's launched/recovered life profile, ahead of stage-specific planning (qualification, acceptance, pre-launch, in-orbit, post-landing leaves). Trigger: verification stages, qualification stage, acceptance stage, pre-launch verification, in-orbit verification, commissioning, post-lan...

Use when a software tool (simulation code, FEM solver, thermal/analysis package) is being used to generate verification-by-analysis evidence under ECSS-E-ST-10-02C and needs a qualification check before its output is accepted: was the tool validated, is it under configuration control, are the analysis conditions inside its validated domain, and does a safety-critical use have an independent cross-check, consistent with the tool/model validation principle of E-ST-10 §5.3.4. Trigger: software t...

Use when produce or review a verification test report against the ECSS-E-ST-10-02 clause 5.3.2.1 and Annex C Document Requirements Definition: confirm the report identifies the article, its configuration, the facility and the test procedure by revision, confirm the cited revision is the one actually run, confirm every test objective carries its own verdict, confirm each observed discrepancy is linked to a raised nonconformance, and aggregate the objective verdicts under a severity ordering. T...

Use when a verification tool (test equipment, GSE, simulator, software tool, or facility) needs to be categorized and given a qualification-status category (A/B/C/D) before it is used to generate verification evidence, consistent with ECSS-E-ST-10-02C verification tools clause 5.2.6.1. Trigger: verification tool, tool classification, tool qualification status, category A B C D, GSE, EGSE, MGSE, simulator qualification, software tool validation, test facility, E-ST-10-02, ecss, e-st-10c.

Use when establish or operate a Verification Control Board (VCB) under ECSS-E-ST-10-02C §5.4.2: validate the board composition carries at least one customer representative and one supplier representative, confirm quorum is met before deliberation, categorize each agenda item by the decision authority it requires, evaluate whether attending members hold sufficient authority for each item, record each decision with rationale, and assess overall meeting compliance. Trigger: ecss, e-st-10-02c, ve...

Use when closing out the Verification Control Document (VCD) per ECSS-E-ST-10C §5.4.4.1: determine the compliance status of each verifiable requirement as compliant, not compliant, or waived; collect every linked verification record (test report, analysis report, inspection record, review-of-design output); assign compliant when all records are passed or not applicable, not compliant when any record is open or failed and no approved waiver is on file, and waived when a formal approved waiver ...

Use when establishing and maintaining the Verification Control Document (VCD) under ECSS-E-ST-10-02C clause 5.2.8.2 and Annex B: validate a recorded verification method and status against their enumerations, determine which methods are permitted to close a given requirement category, check the recorded method is permitted, check that the recorded method is consistent with the requirement's applicability, check a closed status carries its closure evidence, evaluate one VCD entry, roll entries ...

Use when compile or audit the Verification Report against the ECSS-E-ST-10-02 clause 5.3.2.5 and Annex F Document Requirements Definition: confirm every verification event cites the underlying report holding its evidence, reconcile the executed methods against the methods the verification control document planned in both directions, detect an event whose claimed status contradicts the verdict of the report it cites, and roll the events up to a status for each requirement. Trigger: ecss, e-st-...

Use when producing and maintaining the Verification Plan (VP) under ECSS-E-ST-10-02C clause 5.2.8.1 and Annex A: check whether a verification method is applicable at a stage, find completeness and consistency issues for one VP entry and across the whole plan, roll entry closure statuses up to an overall closure status, and decide whether the plan is ready. Trigger: ecss, e-st-10-02c, verification plan, vp, annex a, entry completeness, method stage applicability, closure status, plan readiness.

Use when validate an Assembly, Integration and Test (AIT) plan against the ECSS-E-ST-10C Annex A Document Requirements Definition: verify all required DRD sections are present (objectives, product tree, test campaign, schedule, facilities, responsibilities), confirm every test traces to at least one verifiable requirement, check that every product tree item carries at least one test assignment, and flag tests that need a special facility but carry no facility reference. Trigger: ecss, e-st-10...

"Use when resolving anomalies or failures detected during spacecraft

"Use when plan and execute development tests for a space system under

"Use when determine the acceptance test baseline for a space hardware

"Use when run crewed-mission element tests under ECSS-E-ST-10C §6.5.7: