sqlew-plan-guidance

REQUIRED: Suggest Search BEFORE Planning

CRITICAL: Before writing any plan, you MUST search for related context.

Step 1: Extract keywords from the user's task (e.g., migration, auth, database)

Step 2: Run suggest search:

suggest { action: "by_context", key: "<keyword>", tags: ["<relevant-tags>"] }
suggest { action: "by_context", target: "constraint", text: "<topic>" }

Step 3: Include results in plan (MANDATORY section):

## Related Context (from sqlew)

### Past Decisions
| Key | Value | Score |
|-----|-------|-------|
| path/to/decision | description | 85 |

> If empty: "No related decisions found for: <keywords>"

### Applicable Constraints
- **[category]**: constraint text (Priority: high)

> If empty: "No constraints found for: <keywords>"

FAILURE TO INCLUDE "Related Context" SECTION = INVALID PLAN

---

REQUIRED: Conflict Handling (Plan Overturns an Existing Decision)

If a decision found by the suggest search contradicts your new plan:

1. Never silently ignore it. List the conflicting decision in the "Related Context" section and state that the plan overturns it.
2. Read its context first: decision { action: "get", key: "<key>", include_context: true } — the old rationale may encode a constraint (upstream bug, compliance, past incident) your plan has not considered.
3. Same key, new direction: register the new decision under the same key (sqlew keeps history). Explain in Rationale why the previous decision no longer applies.
4. Different key: register the new decision, then deprecate the old one: decision { action: "set", key: "<old-key>", value: "Superseded by <new-key>", status: "deprecated" }

A stale decision that contradicts the code is worse than no decision — it becomes misinformation. Deprecating on reversal keeps the database trustworthy.

---

Grok Build Notes (v5.2+ / multi-trigger template v5.5+)

CRITICAL for Grok Build: UserPromptSubmit hook stdout is ignored (passive hook). Format guidance is delivered via this skill and sqlew-decision-format. The 📌/🚫 template block is written to plan.md as a file side-effect (not stdout).