modify agent and skill

.codex/skills/fesa-requirements-baseline/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: fesa-requirements-baseline
-description: Use when defining FESA solver feature requirements, acceptance criteria, tolerance decisions, verification quantities, and a requirement verification matrix before research, formulation, reference modeling, or implementation planning.
+description: Use when analyzing new FESA solver feature requirements, acceptance criteria, tolerance decisions, verification quantities, and a requirement verification matrix before research, formulation, reference modeling, or implementation planning.
 ---
 
-# FESA Requirements Baseline
+# FESA New Solver Feature Requirements Analysis
 
-Use this skill to turn a solver feature request into a verifiable baseline that downstream agents can use without guessing.
+Use this skill to turn a new solver feature request into a verifiable new solver feature requirements analysis baseline that downstream agents can use without guessing.
 
 ## Inputs
 
@@ -20,26 +20,26 @@ Read these first:
 ## Workflow
 
 1. Assign a stable `feature_id` in kebab case.
-2. Define purpose, included scope, excluded scope, and analysis definition.
-3. Convert requested behavior into `shall` statements with ids like `FESA-REQ-<FEATURE>-###`.
-4. Define verification quantities: displacement, reaction, element force, stress, strain, energy, or residual.
-5. Record Tolerance Policy values or mark them `needs-user-decision`.
-6. Record Reference Artifact Requirements under `references/<feature-id>/`.
-7. Build a Requirement Verification Matrix that maps requirement, source, verification method, acceptance criteria, tolerance, downstream agents, and status.
+2. Analyze purpose, included scope, excluded scope, and analysis definition.
+3. Convert requested behavior into analyzed `shall` statements with ids like `FESA-REQ-<FEATURE>-###`.
+4. Analyze and record verification quantities: displacement, reaction, element force, stress, strain, energy, or residual.
+5. Analyze and record Tolerance Policy values or mark them `needs-user-decision`.
+6. Analyze and record Reference Artifact Requirements under `references/<feature-id>/`.
+7. Build a Requirement Verification Matrix that maps analyzed requirement, source, verification method, acceptance criteria, tolerance, downstream agents, and status.
 8. Keep unresolved decisions visible as open issues; do not hide gaps behind vague wording.
 
 ## Output Contract
 
-Produce or revise `docs/requirements/<feature-id>.md` with:
+Produce or revise `docs/requirements/<feature-id>.md` as a new solver feature requirements analysis document with:
 
-- Metadata with `feature_id`, status, owner agent, and date
+- Metadata with `feature_id`, analysis status, owner agent, and date
 - Purpose, In Scope, Out Of Scope, and Analysis Definition
 - Input and Output Requirements
 - Verification Quantities
 - Tolerance Policy
 - Reference Artifact Requirements
 - Requirement Verification Matrix
-- Open Questions and Downstream Handoff
+- Open Questions and Downstream Handoff from the requirements analysis
 
 ## Boundaries
 
@@ -52,9 +52,9 @@ Produce or revise `docs/requirements/<feature-id>.md` with:
 
 ## Quality Gate
 
-- Every `must` requirement has a verification method and acceptance criteria.
-- Every numerical requirement has units, coordinate system, and tolerance or an explicit owner for the decision.
-- Every reference-comparison requirement names required artifacts.
+- Every `must` requirement analyzed in the document has a verification method and acceptance criteria.
+- Every numerical requirement analyzed in the document has units, coordinate system, and tolerance or an explicit owner for the decision.
+- Every reference-comparison requirement analyzed in the document names required artifacts.
 - Words like "accurate", "fast", and "Abaqus-like" are converted into measurable criteria or open questions.
 
 ## Handoff

.codex/skills/fesa-requirements-baseline/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
-  display_name: "FESA Requirements Baseline"
-  short_description: "Define solver requirements"
-  default_prompt: "Use $fesa-requirements-baseline to define verifiable FESA solver requirements."
+  display_name: "FESA Requirements Analysis"
+  short_description: "Analyze new solver requirements"
+  default_prompt: "Use $fesa-requirements-baseline to analyze new FESA solver feature requirements."