reflect

# Reflect ## Contract | Field | Bound contract | |---|---| | Trigger | Reflect on a completed task to improve invoked skills. | | Authority | Human-only: explicit invocation required before any mutation. | | Side effect | Edits approved skills and may file backlog items. | | Done | Approved improvements applied and rejections explained. | ## Refusals - Edits without explicit human approval: rejected. Every "apply now" or "apply on approval" proposal requires explicit human sign-off before any file change. - Analysis beyond the named skills: rejected. Do not widen the analysis beyond the invoked skills the human supplied. - **Remote, credential, publish, deploy, or irreversible changes**: rejected. ## Inputs The human must supply: - The completed task context (what was attempted, what happened, what remains). - The list of invoked skill slugs or names. Optional: evidence of failure patterns, specific lines or sections to target, or scope constraints. ## Procedure 1. Collect context. Gather the task context and the list of invoked skills from the human. Identify which skill files are reachable in the workspace. **Done when**: the task context and skill list are gathered and reachable files are identified. 2. Analyze. Examine the invoked skills for failure patterns, missing coverage, unclear scope, or improvement opportunities. Do not widen the analysis beyond the named skills. **Done when**: each skill has been examined and findings are listed. 3. Propose. Present each...