update agent, skill and scripts

2026-09-07 01:15:26 +09:00
parent 42a4847da5
commit d7e9629640
38 changed files with 476 additions and 2946 deletions
@@ -1,39 +1,10 @@
 ---
 name: fem-release-readiness
-description: Use when a structural FEM solver feature has completed technical gates and needs an evidence-based release-readiness audit.
+description: Audit a structural FEM feature's evidence and limitations when the user explicitly requests release readiness.
 ---

 # FEM Release Readiness

-Audit closure evidence and prepare a release recommendation without modifying technical contracts or performing a release.
+Use only for an explicit release-readiness audit. Review the requested feature's relevant contracts, validation/reference evidence, known limitations, deferred work, and risks. Check that blocking requirements have credible evidence and that unsupported behavior is explicit; report contradictions or missing evidence rather than waiving them.

-## Inputs
-
- All lifecycle artifacts for one `feature_id` and contract revision
- Passing configured full validation and required comparison evidence
- Passing physics review
- Correction history, accepted risks, and project release policy
-
-## Workflow
-
-1. Inventory required artifacts and verify identity, revision, freshness, ownership, outcome, and absence of contradictions.
-2. Trace every blocking requirement through acceptance criteria, implementation/tests, required numerical or reference evidence, physics review, and final disposition.
-3. Confirm unresolved defects, deferred scope, compatibility limits, unsupported behavior, accepted risks, and environment limits are explicit.
-4. Produce the checklist, known limitations, release-notes draft, and readiness verdict. Return missing or failed evidence to its owning stage.
-
-Use [evidence and handoff](../fem-requirements-baseline/references/evidence-and-handoff.md) to validate stage envelopes. Read [toolchain and verification](../fem-implementation-tdd/references/toolchain-and-verification.md) when auditing command or comparison evidence. Use [workflow and decision authority](../fem-requirements-baseline/references/workflow-and-decisions.md) for release-scope decisions.
-
-## Output
-
-Follow [Feature document management](../../../docs/FEATURE_DOCUMENTATION.md): 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>/release.md` with release scope, gate inventory, requirement traceability, validation summary, known limitations, deferred items, release-notes draft, readiness verdict, residual risks, and handoff.
-
-## Evidence
-
-A ready verdict requires complete, passing, current evidence for every blocking gate. Record artifact paths and hashes, configuration/toolchain identity, test and comparison summaries, approved exceptions, and the exact contract revision audited.
-
-## Boundary
-
-Do not implement or correct code, edit tests or upstream contracts, waive missing evidence, change acceptance or tolerance, or reinterpret a failed gate. Do not commit, tag, package, publish, deploy, or externally release anything unless the user explicitly authorizes that separate action. Readiness is a recommendation, not publication approval.
+Produce a concise readiness recommendation with evidence paths, commands/exit codes where relevant, limitations, and residual risks. This is not a mandatory lifecycle stage and does not authorize code changes, commits, tags, packages, publication, deployment, or release.
@@ -1,4 +1,4 @@
 interface:
  display_name: "FEM Release Readiness"
  short_description: "Audit structural FEM release readiness"
-  default_prompt: "Use $fem-release-readiness to audit release readiness for a completed structural FEM solver feature."
+  default_prompt: "Use $fem-release-readiness to audit the requested structural FEM feature's release readiness."