devflow-knowledge-completer

Skill: devflow-knowledge-completer

LLM-Wiki guarantor. Pattern from Karpathy's LLM-Wiki and OmegaWiki. The wiki is not a side-effect of work — it is the work's compounding artifact. This skill ensures that every flow leaves the wiki at least as complete as it found it.

When to use

• After devflow-planning and devflow-collision-acknowledged, before submitting plan to approval — so the plan cites the wiki.
• Again at review → done — so any knowledge unearthed during implementation is captured.

Process

1. Pull the wiki context

GET /api/flows/:id/wiki-context

Returns { relatedAdrs, relatedDocs, parallelFlows, gaps, briefing }. The gaps array is the list of topics that still have no coverage in the wiki.

2. For each gap — decide extend vs create vs intent_defer

For every gap topic, scan relatedAdrs and relatedDocs first. Prefer extend if a related entry exists:

• extend — a related ADR/pattern/runbook already exists; this flow uncovered something the entry should now mention. Pass entityType + entityId + body (the section to append) and rationale (1–2 sentences why). Backend appends ## Update YYYY-MM-DD — extended by DF-XXX + body to the entry's content. Hook 1 also injects the wikilink into the plan.

• adr / pattern / runbook — no related entry exists; create a new one via knowledge_check_resolve orchestrator (title + body + rationale). Tag it with the topic AND the broader area (e.g. ["auth", "auth/passkeys"]).

• intent_defer — the gap is real but genuinely out of scope. Provide horizon and a substantive reason. The intent will resurface in pending_work for a future flow.

Never dismiss. The dismiss resolution-type still exists for backwards compat but is forbidden by this skill — if the gap is irrelevant, it's because the topic-detection misfired, in which case the right move is to extend an existing entry with a one-line "this codebase does not use X" note (so the next flow doesn't trip on the same false positive).