process-defect-report
Turn repeated slips on the same step into a named process defect with one concrete change to try, rather than another round of chasing individuals. TRIGGER: the same thing keeps going wrong, or the slip count crosses the repeat threshold. SKIP: chasing today's outstanding items (use owner-sweep) or running the weekly review (use cadence-review).
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-22
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- process-defect-report
- version
- 1.0.0
- description
- Turn repeated slips on the same step into a named process defect with one concrete change to try, rather than another round of chasing individuals. TRIGGER: the same thing keeps going wrong, or the slip count crosses the repeat threshold. SKIP: chasing today's outstanding items (use owner-sweep) or running the weekly review (use cadence-review).
02 资源文件 2
- 参考文档examples/handoff-defect.md2.6 KB
- 参考文档validation/quality-checklist.md727 B
03 SKILL.md 正文
Files
validation/quality-checklist.md— the bar the report must clear before it is delivered.examples/handoff-defect.md— a worked report turning three slips into one structural fix.
Contract
Given the slip history in workspace/ops/slips/, produce a report such that:
- The defect is stated as a property of the process, never as a property of a person.
- The evidence is the specific slip instances: dates, the commitment, and the step.
- The step where work actually stalls is identified — usually a handoff, not a task.
- Exactly ONE change is proposed. Not a list of improvements.
- The proposed change names what would be observed if it worked, and by when.
- Capacity problems are distinguished from process problems and labelled as such.
Findings are written back with
ops_log_processwhen the process definition is corrected.
Knowledge
- Three misses on the same step is not bad luck. It is a defect, and treating the third instance as an incident guarantees a fourth.
- Most operational defects live at handoffs, not inside tasks. The person doing the work is rarely the constraint; the moment work changes hands usually is.
- A defect caused by one person carrying too much is a capacity problem. Proposing a process change for a capacity problem fixes nothing and adds ceremony.
- One change at a time. Two simultaneous changes make the result unattributable, and the next report cannot tell which one worked.
- Adding a checklist is the default non-answer. Prefer removing a step, moving a decision earlier, or making an owner explicit.
Steps
- Run
ops_slip_patternsto get the repeat counts. Gate: state the threshold and the counts. - Pull the individual slip instances behind the count. Gate: list dates, commitments, and steps.
- Locate where work actually stalls — name the handoff or step. Gate: state it precisely.
- Test the capacity hypothesis: is one person the common factor? Gate: state process or capacity.
- State the defect as a property of the process. Gate: re-read it — if a name appears, rewrite.
- Propose exactly one change, with its observable and a date. Gate: confirm one, not several.
- Run the quality checklist. Gate: report pass/fail.
Output
A markdown report: # Process defect — <process>/<step>, then sections The pattern
(instances with dates), Where it stalls, The defect (stated structurally),
Process or capacity, The one change, What we should observe, and by when.
Red Flags & Rationalizations
- The report names a person as the defect — that is a performance conversation, not an ops report.
- Four improvements are proposed — nothing will be attributable next month.
- The change is "add a checklist" or "communicate better" with no structural edit.
- The evidence is a count with no instances behind it.
| Rationalization | Rebuttal | | "It really is that one person." | Then it is a capacity or role problem. Say that, and do not dress it as process. | | "Let's fix all three while we're here." | Then next month you cannot tell which fix worked. One change. | | "A reminder will solve it." | Reminders decay. Change the structure, not the volume. | | "We just need to be more disciplined." | Discipline is not a mechanism. Name the step and change it. |
Validation
Pass when the checklist in validation/quality-checklist.md is all checked, the defect
statement survives a read with no person named, and exactly one change is proposed with a
dated observable. Claims of "done" require the rendered report pasted, not described.
Examples
examples/handoff-defect.md— three slips traced to one handoff, fixed by moving a decision earlier.
04 同仓库更多 Skills
notes
Read a note back with the notes_echo tool.
workflow-builder
Turn a repeatable business process described in conversation into a named, validated ArcFlow workflow draft.
update-tool
Update an existing @tool source file in workspace/capabilities/, bumping its semver per major/minor/patch.
update-skill
Update an existing skill's SKILL.md body in workspace/capabilities/skills/, bumping its frontmatter semver.
create-tool
Author a new @tool-decorated Python file in the agent workspace, validate it, and register it via reload().
create-skill
Scaffold a new skill folder under workspace/capabilities/skills/ with frontmatter and the seven required sections.