KOKO\Mimi
2.4 KiB
name, description
| name | description |
|---|---|
| fem-requirements-baseline | Use when baselining a finite-element structural solver feature before research, formulation, interface definition, or implementation planning. |
FEM Requirements Baseline
Turn a structural-analysis solver request into a stable, verifiable contract without choosing downstream mathematics or implementation.
Inputs
- Project instructions and architecture decisions
- User request, constraints, exclusions, and existing feature artifacts
- Applicable standards or compatibility commitments already selected by the project
Workflow
- Use the stable kebab-case
feature_idand feature folder supplied by Coordinator; define purpose, scope, exclusions, analysis family, assumptions, units, coordinates, and compatibility boundary. - Write atomic
FEM-REQ-<FEATURE>-###shall-statements. Give each an observable acceptance criterion and verification method. - Define logical verification quantities and required physical behavior. Preserve acceptance fixed by the user or an applicable standard; otherwise delegate quantity details, metric, scale, blocking class, and numerical tolerance to Numerical Review under
docs/TOLERANCE.md. - Build the requirement-verification matrix and classify open issues using the project workflow.
Read workflow and decision authority when resolving ambiguity or deciding whether user input is critical. Use evidence and handoff for the returned envelope.
Output
Follow Feature document management: read the Coordinator's feature context, keep main reports concise, and link necessary owned details in the same feature folder.
Create or revise docs/<feature-id>/requirements.md with metadata, scope, analysis definition, requirements, acceptance criteria, verification intent, compatibility boundary, matrix, open decisions, and handoff.
Evidence
Every requirement traces to its source and an acceptance method. Numerical outputs state quantity, location, units, coordinates, and tolerance source when applicable.
Boundary
Do not derive the formulation, select a numerical algorithm, design APIs or storage schemas, implement code, calibrate tolerances, or claim compatibility beyond the approved boundary. Route missing theory, reference evidence, or physical acceptance choices to their owning stage.