القائمة
Scaffold and verify a new native Rust FSL language feature while keeping syntax, lowering, symbolic/concrete semantics, docs, skill reference, tests, and changelog coupled.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Shared FSL language and verifier reference for writing, checking, verifying, repairing, explaining, mutating, refining, replaying, generating scenarios/test scaffolds, and interpreting fslc JSON results. Use directly for FSL syntax, kernel specs, verifier errors, repair loops, and command usage. For role-specific authoring, prefer fsl-business for business flows, fsl-requirements for PM requirements/acceptance/NFR specs, and fsl-design for engineering design/refinement work.
Generate, edit, and re-verify a human-readable requirements document (Markdown) from a checked FSL requirements/spec dialect file, using fslc document generate/claims/check. The agent is a non-normative editor and review-support assistant, never a compiler — it may only fill in the document's editable slot (background, summary, review notes) and propose advisory findings; it must never rewrite a generated claim block or invent normative language FSL does not state. Use when the deliverable is a requirements document artifact for stakeholders, not FSL authoring (use fsl-requirements for that) or a verification audit ledger (use fsl for fslc ledger).
Operate FSL's GitLab Flow-inspired lifecycle from short-lived branches through main and production to an exact vX.Y.Z release tag. Use when adopting the branch flow, integrating post-merge quality improvements, promoting a release, cutting a release, or handling a production hotfix.
Write and verify FSL requirements-layer specs for PMs/PdMs from natural-language product requirements, acceptance criteria, forbidden flows, requirement IDs, traceability, and NFRs such as permissions, audit, capacity, reliability, and SLA/deadline behavior. Use when the deliverable is a requirements specification, not business process discovery, software architecture, internal design, or implementation conformance.
Reconcile tasks/active.md with Git, changed files, and observed verification before compaction, clearing, or handoff.
Create or refresh the verified, resumable task packet in tasks/active.md before substantial FSL repository work.
| name | add-language-feature |
| description | Scaffold and verify a new native Rust FSL language feature while keeping syntax, lowering, symbolic/concrete semantics, docs, skill reference, tests, and changelog coupled. |
The Rust workspace is authoritative. Before editing, classify the feature as surface-only lowering, typed Kernel behavior, evaluator semantics, CLI/report behavior, or public Kernel contract.
rust/fsl-syntax: tokens, parsing, AST, and locations when syntax changes.rust/fsl-core: validation, types, name resolution, dialect lowering, and Kernel projection.rust/fsl-runtime: concrete Monitor/BFS behavior for evaluable semantics.rust/fsl-verifier: symbolic BMC/induction/refinement/liveness behavior.rust/fsl-tools or rust/fslc: report/command/envelope behavior when applicable.rust/fsl-wasm: only when Worker-visible behavior or shared envelopes require it.docs/LANGUAGE.md, skills/fsl/reference.md, relevant docs/DESIGN-*.md, docs map, and
CHANGELOG.md [Unreleased].Do not update src/fslc by default. Record the explicit compatibility or LSP contract before changing
the frozen Python reference.
cargo run --manifest-path rust/Cargo.toml -p fslc-rust --bin fslc -- check <case> and the smallest relevant
verify command.Never widen an allowlist, hollow a spec, or hand-edit a generated artifact to make the gate pass.