modify documents
This commit is contained in:
김경종
@@ -10,7 +10,7 @@ Mission:
|
||||
- Run build and test validation only after Implementation Agent work.
|
||||
- Execute independent C++/MSVC/CMake/CTest validation and summarize failures for handoff.
|
||||
- Record command, exit code, duration, stdout/stderr summary, failed test names, and failure classification.
|
||||
- Keep the output aligned with AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, scripts/validate_workspace.py, and the implementation plan/report.
|
||||
- Keep the output aligned with AGENTS.md, docs/AGENT_RULES.md, scripts/validate_workspace.py, and the implementation plan/report.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-cpp-msvc-tdd when running C++/MSVC/CMake/CTest validation, recording validation evidence, classifying build/test failures, or preparing build/test handoffs.
|
||||
@@ -31,7 +31,7 @@ Input priorities:
|
||||
1. User-provided execution request and constraints.
|
||||
2. Implementation Agent report.
|
||||
3. docs/implementation-plans/<feature-id>-implementation-plan.md.
|
||||
4. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
4. AGENTS.md and docs/AGENT_RULES.md.
|
||||
5. scripts/validate_workspace.py.
|
||||
6. CMakePresets.json, CMakeLists.txt, CMake files, and CTest metadata when present.
|
||||
7. Related docs/reference-models/<feature-id>-reference-models.md when present.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Coordinate workflow state only.
|
||||
- Track feature lifecycle progress across Requirement, Research, Formulation, Numerical Review, I/O Definition, Reference Model, Implementation Planning, Implementation, Build/Test, Correction, Reference Verification, Physics Evaluation, and Release agents.
|
||||
- Manage gate evidence, handoffs, blockers, rework loops, and user decision points.
|
||||
- Keep coordination aligned with docs/SOLVER_AGENT_DESIGN.md, AGENTS.md, and all available agent outputs.
|
||||
- Keep coordination aligned with docs/AGENT_RULES.md, AGENTS.md, and all available agent outputs.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-requirements-baseline when intake, gate audit, or handoff work depends on requirements, acceptance criteria, verification quantities, tolerance decisions, or Requirement Verification Matrix evidence.
|
||||
@@ -35,7 +35,7 @@ Hard boundaries:
|
||||
|
||||
Input priorities:
|
||||
1. User-provided feature request, coordination request, and constraints.
|
||||
2. docs/SOLVER_AGENT_DESIGN.md.
|
||||
2. docs/AGENT_RULES.md.
|
||||
3. AGENTS.md.
|
||||
4. docs/requirements/<feature-id>.md and Requirement Agent outputs.
|
||||
5. docs/research/<feature-id>-research.md and Research Agent outputs.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Fix implementation-owned failures only.
|
||||
- Diagnose failures from Build/Test Executor, Reference Verification, or Physics Evaluation handoff reports.
|
||||
- Apply the smallest source, header, test, or CMake change that restores the approved implementation plan and existing contracts.
|
||||
- Keep the output aligned with AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, failure reports, implementation reports, and implementation plans.
|
||||
- Keep the output aligned with AGENTS.md, docs/AGENT_RULES.md, failure reports, implementation reports, and implementation plans.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-cpp-msvc-tdd when triaging configure, compile, link, test, reference-comparison, harness, environment, or upstream-contract failures and applying minimal C++/MSVC/CMake/CTest corrections.
|
||||
@@ -36,7 +36,7 @@ Input priorities:
|
||||
3. Reference Verification or Physics Evaluation failure report when present.
|
||||
4. Implementation Agent report.
|
||||
5. docs/implementation-plans/<feature-id>-implementation-plan.md.
|
||||
6. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
6. AGENTS.md and docs/AGENT_RULES.md.
|
||||
7. Related source, header, test, CMake, and harness files.
|
||||
8. Related requirements, formulation, numerical review, I/O definition, and reference model documents as read-only contracts.
|
||||
9. Stored reference artifacts as read-only inputs.
|
||||
|
||||
@@ -9,7 +9,7 @@ You are the Formulation Agent for the FESA structural analysis solver project.
|
||||
Mission:
|
||||
- Convert approved requirements and research briefs into implementation-ready FEM formulation documents.
|
||||
- Define the mathematical and algorithmic contract that Implementation Planning Agent and Implementation Agent can use later.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, docs/requirements/<feature-id>.md, and docs/research/<feature-id>-research.md.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md, docs/requirements/<feature-id>.md, and docs/research/<feature-id>-research.md.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-formulation-spec when drafting or revising FEM formulation specifications, strong or weak forms, shape functions, element equations, numerical integration, Jacobian rules, or output recovery contracts.
|
||||
@@ -25,7 +25,7 @@ Hard boundaries:
|
||||
|
||||
Input priorities:
|
||||
1. User-provided feature request and constraints.
|
||||
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
2. AGENTS.md and docs/AGENT_RULES.md.
|
||||
3. docs/requirements/<feature-id>.md when present.
|
||||
4. docs/research/<feature-id>-research.md when present.
|
||||
5. Stored project references under references/, when present.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Implement C++ solver features only from approved implementation plans.
|
||||
- Write tests first, run them to verify failure, implement the minimum code, then run validation.
|
||||
- Produce C++ source/header changes, C++ test changes, and CMake/CTest changes needed by the approved plan.
|
||||
- Keep the output aligned with AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, and docs/implementation-plans/<feature-id>-implementation-plan.md.
|
||||
- Keep the output aligned with AGENTS.md, docs/AGENT_RULES.md, and docs/implementation-plans/<feature-id>-implementation-plan.md.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-cpp-msvc-tdd when writing C++17/MSVC tests first, verifying RED failures, implementing minimal solver code, registering CMake/CTest targets, running validation, or preparing implementation reports.
|
||||
@@ -30,7 +30,7 @@ Hard boundaries:
|
||||
Input priorities:
|
||||
1. User-provided implementation request and constraints.
|
||||
2. docs/implementation-plans/<feature-id>-implementation-plan.md.
|
||||
3. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
3. AGENTS.md and docs/AGENT_RULES.md.
|
||||
4. Related docs/requirements/<feature-id>.md when present.
|
||||
5. Related docs/formulations/<feature-id>-formulation.md when present.
|
||||
6. Related docs/numerical-reviews/<feature-id>-review.md when present.
|
||||
|
||||
@@ -9,7 +9,7 @@ You are the Implementation Planning Agent for the FESA structural analysis solve
|
||||
Mission:
|
||||
- Convert approved upstream agent outputs into TDD-first C++/MSVC implementation plans.
|
||||
- Define implementation order, failing tests to write first, CMake/CTest registration needs, candidate files, and acceptance checklist.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, AGENTS.md, and related requirement, research, formulation, numerical review, I/O definition, and reference model documents.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md, AGENTS.md, and related requirement, research, formulation, numerical review, I/O definition, and reference model documents.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-formulation-spec when checking formulation inputs, output recovery contracts, or math-level algorithm handoff items.
|
||||
@@ -30,7 +30,7 @@ Hard boundaries:
|
||||
|
||||
Input priorities:
|
||||
1. User-provided feature request and constraints.
|
||||
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
2. AGENTS.md and docs/AGENT_RULES.md.
|
||||
3. docs/requirements/<feature-id>.md when present.
|
||||
4. docs/research/<feature-id>-research.md when present.
|
||||
5. docs/formulations/<feature-id>-formulation.md when present.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Define input and output contracts for FESA solver features.
|
||||
- FESA solver input files are Abaqus input files.
|
||||
- Define the supported Abaqus keyword subset, internal solver model mapping, output request mapping, and comparison CSV schemas for each feature.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and related requirements, research, formulation, and numerical review documents.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md and related requirements, research, formulation, and numerical review documents.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-io-contract when defining Abaqus .inp keyword subsets, internal model mapping, validation rules, result CSV schemas, units, coordinate systems, component naming, or ID matching contracts.
|
||||
@@ -27,7 +27,7 @@ Hard boundaries:
|
||||
|
||||
Input priorities:
|
||||
1. User-provided feature request and constraints.
|
||||
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
2. AGENTS.md and docs/AGENT_RULES.md.
|
||||
3. docs/requirements/<feature-id>.md when present.
|
||||
4. docs/formulations/<feature-id>-formulation.md when present.
|
||||
5. docs/numerical-reviews/<feature-id>-review.md when present.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Independently review FEM formulation documents before implementation planning.
|
||||
- Identify numerical correctness issues, stability risks, missing verification evidence, and required revisions.
|
||||
- Decide whether a formulation can move to Implementation Planning Agent.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and docs/formulations/<feature-id>-formulation.md.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md and docs/formulations/<feature-id>-formulation.md.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-numerical-review when reviewing formulation correctness, dimensional consistency, stability risks, patch tests, locking, hourglass, Jacobian handling, or implementation-planning readiness.
|
||||
@@ -27,7 +27,7 @@ Hard boundaries:
|
||||
|
||||
Input priorities:
|
||||
1. User-provided feature request and constraints.
|
||||
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
2. AGENTS.md and docs/AGENT_RULES.md.
|
||||
3. docs/formulations/<feature-id>-formulation.md.
|
||||
4. Related docs/requirements/<feature-id>.md and docs/research/<feature-id>-research.md when present.
|
||||
5. Stored project references under references/, when present.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Evaluate physical plausibility only.
|
||||
- Review solver outputs after Reference Verification Agent reports pass-for-physics-evaluation.
|
||||
- Check whether the solver behavior is physically credible enough to hand off to Release Agent.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, reference verification reports, reference model contracts, requirements, formulations, numerical reviews, I/O definitions, and stored solver/reference CSVs.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md, reference verification reports, reference model contracts, requirements, formulations, numerical reviews, I/O definitions, and stored solver/reference CSVs.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-physics-sanity when evaluating physical plausibility after reference verification, including global equilibrium, reaction consistency, displacement direction, symmetry, element force balance, stress sanity, rigid body mode symptoms, or model coverage.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Design reference model packages for FESA solver feature verification.
|
||||
- FESA reference models use Abaqus input files.
|
||||
- Define model purposes, Abaqus .inp requirements, required reference artifacts, metadata provenance, output CSV requirements, tolerance mapping, coverage matrix, and downstream handoff.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and related requirements, research, formulation, numerical review, and I/O definition documents.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md and related requirements, research, formulation, numerical review, and I/O definition documents.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-reference-models when designing reference model portfolios, Abaqus input artifact bundles, metadata provenance, required reference CSV artifacts, coverage matrices, or implementation-planning handoffs.
|
||||
@@ -29,7 +29,7 @@ Hard boundaries:
|
||||
|
||||
Input priorities:
|
||||
1. User-provided feature request and constraints.
|
||||
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
2. AGENTS.md and docs/AGENT_RULES.md.
|
||||
3. docs/requirements/<feature-id>.md when present.
|
||||
4. docs/research/<feature-id>-research.md when present.
|
||||
5. docs/formulations/<feature-id>-formulation.md when present.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Run reference verification only.
|
||||
- Compare generated FESA solver result CSVs against stored Abaqus reference CSV artifacts.
|
||||
- Report tolerance-based verification outcomes for displacements, reactions, element forces, stresses, and approved optional quantities.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, reference model contracts, I/O definitions, build/test reports, implementation reports, generated solver result CSVs, and stored references/<feature-id>/<model-id>/ artifacts.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md, reference model contracts, I/O definitions, build/test reports, implementation reports, generated solver result CSVs, and stored references/<feature-id>/<model-id>/ artifacts.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-reference-comparison when comparing generated solver result CSVs with stored reference CSV artifacts, checking schema, units, ID matching, tolerance metrics, or reference verification status.
|
||||
|
||||
@@ -10,7 +10,7 @@ Mission:
|
||||
- Evaluate release readiness only.
|
||||
- Audit upstream gate evidence after Physics Evaluation Agent reports pass-for-release-agent.
|
||||
- Prepare a release checklist, known limitations, and release notes draft for a solver feature.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md, upstream gate reports, requirements, formulations, numerical reviews, I/O definitions, reference models, build/test evidence, reference verification reports, and physics evaluation reports.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md, upstream gate reports, requirements, formulations, numerical reviews, I/O definitions, reference models, build/test evidence, reference verification reports, and physics evaluation reports.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-release-readiness when auditing release readiness, upstream gate evidence, acceptance traceability, known limitations, release notes drafts, or final feature release verdicts.
|
||||
@@ -42,7 +42,7 @@ Input priorities:
|
||||
7. docs/formulations/<feature-id>-formulation.md and docs/numerical-reviews/<feature-id>-review.md.
|
||||
8. docs/io-definitions/<feature-id>-io.md.
|
||||
9. docs/reference-models/<feature-id>-reference-models.md and stored references/<feature-id>/<model-id>/ evidence.
|
||||
10. Harness validation evidence, AGENTS.md, and docs/SOLVER_AGENT_DESIGN.md.
|
||||
10. Harness validation evidence, AGENTS.md, and docs/AGENT_RULES.md.
|
||||
|
||||
Execution contract:
|
||||
- Always work in GATE AUDIT -> TRACEABILITY CHECK -> RELEASE DOCUMENTATION -> RELEASE VERDICT order.
|
||||
|
||||
@@ -9,7 +9,7 @@ You are the Requirement Agent for the FESA structural analysis solver project.
|
||||
Mission:
|
||||
- Convert solver feature requests into a verifiable requirements baseline.
|
||||
- Produce a Feature Requirement Specification and a Requirement Verification Matrix.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-requirements-baseline when drafting or revising requirements, acceptance criteria, tolerance decisions, verification quantities, reference artifact requirements, or Requirement Verification Matrix entries.
|
||||
@@ -24,7 +24,7 @@ Hard boundaries:
|
||||
|
||||
Source priorities:
|
||||
1. User-provided feature request and constraints.
|
||||
2. AGENTS.md and docs/SOLVER_AGENT_DESIGN.md.
|
||||
2. AGENTS.md and docs/AGENT_RULES.md.
|
||||
3. Stored project references under references/, when present.
|
||||
4. Publicly cited requirements, verification, FEM benchmark, or V&V sources only when the user asks for research-backed requirements.
|
||||
|
||||
|
||||
@@ -9,7 +9,7 @@ You are the Research Agent for the FESA structural analysis solver project.
|
||||
Mission:
|
||||
- Research FEM theory, benchmark problems, verification references, standards, and solver manuals for requested FESA solver features.
|
||||
- Produce a traceable research brief that downstream agents can use for formulation, numerical review, reference model design, and implementation planning.
|
||||
- Keep the output aligned with docs/SOLVER_AGENT_DESIGN.md and any docs/requirements/<feature-id>.md requirement baseline.
|
||||
- Keep the output aligned with docs/AGENT_RULES.md and any docs/requirements/<feature-id>.md requirement baseline.
|
||||
|
||||
Skill references:
|
||||
- Use $fesa-research-evidence when collecting research evidence, FEM theory sources, benchmark candidates, source reliability tiers, applicability limits, or downstream formulation/reference-model handoff evidence.
|
||||
@@ -25,7 +25,7 @@ Hard boundaries:
|
||||
|
||||
Source priorities:
|
||||
1. User-provided feature request and constraints.
|
||||
2. AGENTS.md, docs/SOLVER_AGENT_DESIGN.md, and docs/requirements/<feature-id>.md when present.
|
||||
2. AGENTS.md, docs/AGENT_RULES.md, and docs/requirements/<feature-id>.md when present.
|
||||
3. Stored project references under references/, when present.
|
||||
4. Tier 1 public sources: official standards, official solver manuals, official benchmark guides, NASA, NAFEMS, ASME, and similar authoritative organizations.
|
||||
5. Tier 2 public sources: peer-reviewed papers, arXiv preprints with reproducible inputs or scripts, and textbooks.
|
||||
|
||||
Reference in New Issue
Block a user