Retain a demonstrated procedural lesson

Read the shared workflow contract before substantive work. This skill is part of the locally installed Clarila suite. Its source is in ~/Developer/skills; resolve sibling skills relative to this directory.

Procedure

1. Read actual settled work, failure/correction evidence and existing procedures. Identify a repeated or materially reusable lesson rather than creating proposals to fill a quota.
2. First choose the highest effective corrective layer: eliminate the mistake with domain ownership/architecture, then types, lint or another executable check, then a behavior test. Demonstrate the chosen check rejects an actual prior mistake. Use a prose procedure for the remaining judgment that cannot be enforced; record why stronger layers do not fit. Prepare that concise repository/stage-scoped proposal with original evidence and a stable candidate hash. Keep it proposed until independently validated.
3. Use a separate authorized reviewer/verifier context to test the exact proposal against a relevant scenario. Self-validation or a saved note cannot activate it.
4. Record exact independent validation and activate only the unchanged scoped candidate when requested within the workflow. Preserve failed proposals and withdrawal history.
5. Apply only relevant active procedures under current instructions. Never change model settings, permissions, schedules, user memory or protected policy as a learning side effect.

Test the lesson's scope

State the triggering situation, the corrective action and the observable outcome a procedure is meant to improve. Give the independent assessor a relevant failure/correction case and a nearby case where the lesson should not apply. Compare the candidate with any existing scoped procedure before creating another.

Bind the assessment to the exact proposal bytes and retain its observations. Changed proposals, failed controls or evidence for another scope return the candidate to validation. The handoff identifies the current lifecycle state and the next permitted transition.

Synchronization and handoff

Resolve the same issue/workspace/session association before substantive work, including direct invocation. Read and update the private handoff described in the shared contract using available native file tools. Record the actual stage, source, findings, evidence, outcome and next action. If no native session identity is available, retain an unbound record.

Deliverable

Return the proposal, immutable evidence/validation identity, lifecycle status and exact permitted scope.

Load only the relevant specialist from the catalog. Missing tools change the available evidence, never its meaning.

Read the operation-specific reference when performing this responsibility.