ccoalm/ccl-skills / skills/skill-extraction-workflow
skill-extraction-workflow
Flagged复盘 / 沉淀 / 总结经验 / 补进技能 / 技能缺陷 / 流程优化 / would other teammates hit this / will we forget next time / teamwide recurrence / extract skill / post-mortem / 深度 review·审计技能仓库 / 对标外部技能包找 gap(benchmark superpowers·gstack 等) / 核查全局安装点(~/.config/opencode 等)旧快照是否遮蔽本仓技能 / 本仓(ccl-skills 等共享技能仓)OpenCode 项目配置·命令治理 → turn reusable lessons into durable CCL skills.
references/correction-routing-map.md
View on GitHub# Correction Routing Map
Use this when a retrospective, review follow-up, or user correction names tests, verifiers, coverage, test order, real/external evidence that was unavailable, blocked, deferred, skipped, or mock-substituted, or something the user asked for later in the task that closeout never reported. It decides which owner(s) the target-output map must name for that correction type; the extraction workflow itself still gets its prevention point per the entrypoint's always-land rule.
The two rules below were relocated verbatim from `SKILL.md`'s `Retrospectives, corrections & auto-triggered learning` Core Rules group (low-frequency detail per the entrypoint's content-placement rule); the entrypoint keeps a one-bullet summary that points here. Wording changes here go through the same shared-skill gates as an entrypoint edit.
## Deferred-evidence over-polishing corrections
- **Deferred-evidence over-polishing corrections** route to `product-rd-workflow`'s `DFE-CONT` rule: when a delivery keeps hardening tests/verifiers after the real/external evidence was unavailable, blocked, unreachable, deferred, skipped, or mock-substituted, or reports such real evidence as complete, the target-output map must name `DFE-CONT` (paraphrases like "why keep fixing tests when the cluster wasn't reachable" count — exact deferred/skipped wording is not required). A bare mention of runtime/external access is not enough: a test-hardening, coverage, or test-order correction with no unavailable/blocked/deferred real-evidence element and no deferral-as-terminal claim defaults to `testing-strategy`; when both a deferral signal and a test-order signal are present, map to both (`DFE-CONT` + `testing-strategy`, the test-case-first rule still mandatory). Validate by confirming the `DFE-CONT` block and its non-completion rule are present in the installed `product-rd-workflow` skill's `SKILL.md` (resolve via routing/skill discovery; inside the ccl-skills repo: `skills/product-rd-workflow/SKILL.md` — the file is not at that relative path on installed hosts), and keep this routing token in sync if that block is renamed.
## Tests-before-test-cases corrections
- If a retrospective correction says tests were run before test cases, or asks why test cases were not written first, the target-output map must include `testing-strategy` and any coordinating workflow such as `product-rd-workflow`. A final answer without a durable test-case-first prevention rule, validation command, and challenge or explicit no-update reason is only `interim`.
## Decision table
| Correction signal present | Owners the target-output map must name |
| --- | --- |
| Deferred / blocked / unreachable / mock-substituted real evidence, then continued test or verifier hardening, or such evidence reported as complete | `product-rd-workflow` (`DFE-CONT`) + this workflow |
| Test-hardening, coverage, or test-order correction with no deferral element and no deferral-as-terminal claim | `testing-strategy` + this workflow |
| Both a deferral signal and a test-order signal | `product-rd-workflow` (`DFE-CONT`) + `testing-strategy` + this workflow (test-case-first still mandatory) |
| Tests were run before test cases / why were test cases not written first | `testing-strategy` + the coordinating workflow (`product-rd-workflow`) + this workflow |
| Something the user asked for after the task started was dropped, or closeout reported only against the original task or handoff list | `product-rd-workflow` (later-message recheck, `pre-final-continuation-gate.md`) + this workflow. Check first whether the recheck fired: if it did, the reminder text failed; if not, read how the host recorded the message, because the hook only sees a message absorbed into a running turn |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |