KOKO\Mimi
1.1 KiB
name, description
| name | description |
|---|---|
| fem-requirements-baseline | Define a durable, verifiable structural FEM feature scope and acceptance contract when one is needed. |
FEM Requirements Baseline
Turn the assigned request into observable scope, exclusions, assumptions, compatibility boundary, and acceptance intent. Use an existing PRD when it is sufficient; create a separate requirements document or matrix only when the feature needs that separation.
Write atomic requirements with a measurable acceptance method. State quantities, locations, units, coordinates, and physical behavior where relevant. Preserve user- or standard-defined acceptance; leave formulation choices, implementation, schema design, and numerical tolerance selection to their owners.
Read workflow-and-decisions.md only for a material ambiguity or authority question. Return the document path, decisions, verification intent, and unresolved critical choice. Do not invent physics, compatibility, or acceptance promises.
Use evidence notes when a separate durable evidence record is needed.