ECSS Q-ST-20C Pre-Tailoring (space-systems/ecss/q20-pretailoring)
Use when the task is the clause 6 pre-tailoring of ECSS-Q-ST-20C: the standard
already states, per space product type, which of its clause 5 requirements
apply as written, which do not apply, and which apply in a modified form, and
a project has to work out what its own requirement set actually is.
Domain quick reference
- The matrix is the baseline, not the proposal. What a project ends up working
to is the matrix as the project modified it, and the two are compared line by
line rather than assumed to agree.
- A row that is silent about a product type is not a row that says not
applicable. Silence is the defect, and it is caught at the matrix rather than
discovered at the review.
- Modified is not a softer word for not applicable. A modified requirement
stays in the set, it is verified, and the modification it stands for is
written down or the disposition means nothing.
- The two directions of a departure are not symmetric. Relaxing below the
baseline takes a justification and an approval; tightening above it is the
project's own business and is recorded rather than challenged.
- The applicable fraction is the number the tailoring argument is really about.
A set at four fifths and one at one half are different programmes, and the
fraction is what makes the difference visible.
- A requirement nobody pre-tailored is not a requirement that dropped out. It
is a gap in the matrix, and it is reported against the matrix rather than
silently applied or silently ignored.
Workflow
- Validate the matrix: every covered requirement carries a disposition for
every declared product type, each disposition sits in the closed vocabulary,
and a modified entry carries the modification it stands for.
- Validate the product type against the closed list before anything is read
out of the matrix for it.
- Apply the matrix to the requirement set, keeping applicable and modified
requirements in the tailored set and listing what dropped out.
- Name each requirement with no matrix entry as its own finding rather than
defaulting it either way.
- Reconcile the project's proposed dispositions with the baseline, separating
relaxations from tightenings by their position in the vocabulary.
- Raise a relaxation with no approved justification behind it, and record a
tightening without raising one.
- Compute the applicable fraction over the full requirement set and return the
tailored set, the findings and whether the tailoring may be adopted.
Pitfalls
- Reading the matrix as the finished requirement set. It is the starting point;
what the project proposed on top of it is where the argument lives.
- Dropping a modified requirement. It stays in, it is verified, and the
modification is what the verification is against.
- Accepting a modified disposition with no modification written down. The
disposition then means whatever the reader assumes, which is the failure the
matrix exists to prevent.
- Treating every departure the same way. Challenging a project for being
stricter than the baseline wastes the review on the one deviation that is
never a risk.
- Reporting a count of applicable requirements. The fraction is what is
comparable between product types and between projects; the count is not.
- Letting an uncovered requirement fall through quietly. Whichever way it
falls, nobody decided it, and that is the finding.
Behavior contract (gate 3)
The matrix validation including product-type completeness and the modification
note, product-type validation, application of the matrix to the requirement
set, uncovered-requirement findings, the relaxation-versus-tightening
reconciliation with approved justifications, the applicable fraction and the
adoption verdict are exercised by the gate 3 contract test:
scripts/test_q20_pretailoring.py against scripts/q20_pretailoring_logic.py
(stdlib unittest, offline). Run:
python3 scripts/test_q20_pretailoring.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: q20-pretailoring3description: "Derive the tailored clause 5 requirement set from the ECSS-Q-ST-20C clause 6 pre-tailoring matrix for one space product type: refuse a matrix row that says nothing about a product type or calls a requirement modified without stating the modification, keep each surviving requirement with its disposition, name every requirement the matrix does not cover, reconcile the project's own proposal against the baseline so a relaxation needs an approved justification while a tightening does not, and report the share of the set that still applies. Use when a project has to justify which quality requirements it works to. Trigger: ecss, q-st-20c-clause-6, pre-tailoring-matrix, space-product-type-applicability, tailored-requirement-set, requirement-relaxation-justification, applicable-requirement-fraction."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/q20-pretailoring15 domain: space-systems16 subdomain: ecss17 tags: [ecss, q-st-20c-quality-assurance-scope, q20-pretailoring, pre-tailoring-matrix, space-product-type-applicability, tailored-requirement-set, requirement-relaxation-justification, applicable-requirement-fraction]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS Q-ST-20C Pre-Tailoring (space-systems/ecss/q20-pretailoring)2324Use when the task is the clause 6 pre-tailoring of ECSS-Q-ST-20C: the standard25already states, per space product type, which of its clause 5 requirements26apply as written, which do not apply, and which apply in a modified form, and27a project has to work out what its own requirement set actually is.2829## Domain quick reference3031- The matrix is the baseline, not the proposal. What a project ends up working32 to is the matrix as the project modified it, and the two are compared line by33 line rather than assumed to agree.34- A row that is silent about a product type is not a row that says not35 applicable. Silence is the defect, and it is caught at the matrix rather than36 discovered at the review.37- Modified is not a softer word for not applicable. A modified requirement38 stays in the set, it is verified, and the modification it stands for is39 written down or the disposition means nothing.40- The two directions of a departure are not symmetric. Relaxing below the41 baseline takes a justification and an approval; tightening above it is the42 project's own business and is recorded rather than challenged.43- The applicable fraction is the number the tailoring argument is really about.44 A set at four fifths and one at one half are different programmes, and the45 fraction is what makes the difference visible.46- A requirement nobody pre-tailored is not a requirement that dropped out. It47 is a gap in the matrix, and it is reported against the matrix rather than48 silently applied or silently ignored.4950## Workflow51521. Validate the matrix: every covered requirement carries a disposition for53 every declared product type, each disposition sits in the closed vocabulary,54 and a modified entry carries the modification it stands for.552. Validate the product type against the closed list before anything is read56 out of the matrix for it.573. Apply the matrix to the requirement set, keeping applicable and modified58 requirements in the tailored set and listing what dropped out.594. Name each requirement with no matrix entry as its own finding rather than60 defaulting it either way.615. Reconcile the project's proposed dispositions with the baseline, separating62 relaxations from tightenings by their position in the vocabulary.636. Raise a relaxation with no approved justification behind it, and record a64 tightening without raising one.657. Compute the applicable fraction over the full requirement set and return the66 tailored set, the findings and whether the tailoring may be adopted.6768## Pitfalls6970- Reading the matrix as the finished requirement set. It is the starting point;71 what the project proposed on top of it is where the argument lives.72- Dropping a modified requirement. It stays in, it is verified, and the73 modification is what the verification is against.74- Accepting a modified disposition with no modification written down. The75 disposition then means whatever the reader assumes, which is the failure the76 matrix exists to prevent.77- Treating every departure the same way. Challenging a project for being78 stricter than the baseline wastes the review on the one deviation that is79 never a risk.80- Reporting a count of applicable requirements. The fraction is what is81 comparable between product types and between projects; the count is not.82- Letting an uncovered requirement fall through quietly. Whichever way it83 falls, nobody decided it, and that is the finding.8485## Behavior contract (gate 3)8687The matrix validation including product-type completeness and the modification88note, product-type validation, application of the matrix to the requirement89set, uncovered-requirement findings, the relaxation-versus-tightening90reconciliation with approved justifications, the applicable fraction and the91adoption verdict are exercised by the gate 3 contract test:92scripts/test_q20_pretailoring.py against scripts/q20_pretailoring_logic.py93(stdlib unittest, offline). Run:94python3 scripts/test_q20_pretailoring.py9596## Compliance9798- ECSS standards are freely downloadable (ESA); cite the source and99 paraphrase per standards-map.yaml.100- compliance: STANDARDS-REF, gated: false.