Menu
Reconcile and save the current FSL task state before compaction, clearing, handoff, or ending substantial work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 | checkpoint |
| description | Reconcile and save the current FSL task state before compaction, clearing, handoff, or ending substantial work. |
| disable-model-invocation | true |
| allowed-tools | ["Read","Grep","Glob","Bash(git status *)","Bash(git diff *)"] |
Update .claude/work/active.md. If it does not exist, create it from the template only when a substantial
task is actually active.
Verify the current conversation's claims against:
git status --shortgit diff --stat and the relevant diffPreserve the goal, authority surface, invariants, decisions with reasons, exact evidence, changed files, completed work, failed approaches, exact test outcomes, remaining work, and one next action. Remove superseded hypotheses, raw logs, conversational narration, completed plans, and machine-specific paths.
Do not claim a test passed because it was planned, started, or passed in an earlier tree state. Do not use the checkpoint to introduce a new design decision or expand scope silently.