Skip to content

Arc Skills / Technical management and design reviews

Prepare a preliminary design review

Use Arc Skills to prepare a preliminary design review around whether the chosen architecture can credibly meet its requirements. The packet identifies unresolved interfaces, budget assumptions and maturation evidence that could change the design direction.

Use this skill

Use Arc Skills to prepare a preliminary design review.

Inputs:
- Selected architecture and trade rationale
- Allocated requirements, interfaces and preliminary budgets
- Hazard controls, maturity evidence, verification concepts and review criteria

Return a PDR readiness matrix and board questions with evidence, gaps and owner actions. Focus on whether detailed design can proceed; distinguish measured results from preliminary estimates.

Set up the toolkit · Read the skill instructions

What you provide and what you get

Inputs and outputs
What you haveHow it is usedWhat you get
Architecture and trade evidenceCheck the selected directionDecisions and unresolved alternatives
Allocations, interfaces and budgetsCheck preliminary feasibilityTechnical assumptions and gaps
Risk controls and verification conceptsCheck credible next-phase workAn evidence-backed PDR packet

A selected architecture has power allowance but an open reset contract

Illustrative engineering example.

The payload design uses two processor boards. Preliminary estimates fit the power allowance, while their shared reset and fault-control behavior remain unsettled.

Architecture A selected in TRADE-3. Budget: 40 W source, 32 W loads, 4 W estimated growth, leaving 4 W.
INT-06 reset line ownership [TBD]. Hazard H-2 needs controlled output shutdown.
Sensor technology report covers laboratory conditions only. Verification concepts exist for critical timing obligations.
A selected architecture has power allowance but an open reset contract
Review questionAvailable evidenceFindingRequired action / owner
Architecture rationaleTRADE-3 records criteria and alternativesDirection traceable; assumptions need configuration alignmentArchitecture owner confirms trade inputs match the proposed design
Power feasibility40 − 32 − 4 = 4 W preliminary allowancePositive estimated allowance under stated modeElectrical owner bounds load growth and checks all required modes
Reset interfaceINT-06 ownership [TBD]Could alter subsystem design and recovery behaviorEndpoint owners agree reset authority and transition behavior
Hazard controlH-2 shutdown concept onlyImplementation and verification path need allocationSafety and design owners assign the control and its evidence plan
Technology maturityLaboratory sensor reportRelevant-use maturity unresolvedTechnology owner defines representative demonstration and fallback

The PDR finding is about the credibility of the design direction. A 4 W preliminary allowance is useful evidence, but it is not a measured all-mode power result or proof that future growth is bounded.

The reset agreement can affect both boards and the hazard-control design. It deserves a board question before detailed design, whereas fabrication-ready drawings are not the principal question in this packet.

Test whether the architecture supports detailed design

  1. Trace the selected architecture to major requirements and trade assumptions.
  2. Review function allocation, interface agreements and failure behavior.
  3. Check preliminary budgets, hazard-control paths, maturity and verification concepts.
  4. Present decisions that could invalidate detailed design, with an owner and evidence plan for each.

Questions about this task

Does PDR require every detailed drawing to be released?

Use the project’s criteria, but the central question is whether the preliminary design can support detailed design. A polished block diagram alone is also insufficient.

Sources and further reading

References inspected on 3 October 2026. The worked output is an authored example using the stated inputs.