devflow-collision-acknowledged

Skill: devflow-collision-acknowledged

Knowledge-Hook 1 implementation. This skill is the gatekeeper for planning → approval under the upcoming agent_with_discipline policy. It guarantees that nothing in the topic-scope was forgotten or silently overridden.

When to use

Trigger this skill once per planning session, after the implementation plan has been drafted but before submitting to approval. It complements devflow-planning (brainstorming + plan-writing) — this skill makes sure the plan acknowledges everything the project already knows about the scope.

Process

1. Pull the awareness list

Call pending_work({ tags, paths, excludeFlowId: <currentFlowId> }) — the four buckets:

• proposed ADRs — proposed status, tag-overlap with the current flow
• open intents — DF-265 forward-intents that haven't been resolved yet
• in-flight flows — flows in planning / in_progress / review with shared scope
• pending drafts — knowledge-drafts auto-extracted by harvest

Also call planning_context({ flowId }) for the related-ADRs, parallel-flows, and architecture-module excerpts.

2. Present items to the user

Render the four buckets as a checklist. Never auto-accept. For each item, the user decides:

• ✓ keep → Pick a resolutionType:
  • extend (DF-310, preferred) if a related entry already exists and this flow refines it. Pass entityType + entityId + body + rationale. Backend appends a dated update section.
  • adr / pattern / runbook if the item already covers the topic. Pass the entity id. Hook 1 will inject [[DisplayName]] into the implementation plan and create a knowledge_links edge automatically.
  • intent_defer if the item is real but out of scope here — provide a horizon (next-sprint, next-quarter, eventually) and an optional reason.
• ✗ irrelevant → ⚠ Iron Law (DF-310): never dismiss without first checking if this is a recurring false-positive. If the topic-detection misfires repeatedly (e.g. invalidation in a non-cache project), extend an existing convention page with a one-line note instead — that auto-resolves future flows via DF-314 project-conventions.
• ↺ later → equivalent to intent_defer with no specific decision yet.