feat(mcp): S5 — issue-kind guidance across all instruction surfaces

Plan #825 (T2 — Issues task_kind) shipped S1–S4 but its S5 docs slice never landed, so every behavioral surface the plugin pushes to the agent still described the pre-kind convention ("tag `issue`" on a create_note). Result: agents fixed bugs without reaching for kind=issue and dumped the work as logs on unrelated open tasks. - _INSTRUCTIONS: rewrite the "record a problem" bullet to create_task(kind="issue") with symptom→cause→fix + arose_from_id / system_ids, and an explicit "not a work-log on an unrelated task"; add Issue + System to the hierarchy section. - skills/systematic-debugging, verification: drop "tag `issue`" / create_note-issue, point at create_task(kind="issue"). - skills/using-scribe: add issues/systems to the entity list + reflex #6. - hooks/scribe_static_context: fix → its own issue on the keyless floor. Instance-agnostic, prose-only; no schema or tool-behavior change. Pairs with always-on rule #118. Issue: #855. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-14 23:22:17 -04:00
parent 4f31890bde
commit 5fbee18a94
5 changed files with 44 additions and 16 deletions
@@ -23,8 +23,9 @@ task `done`, confirm it against reality and record what you checked.
  part of the record, not a private step.
 - Only then set the task `done`. Never mark finished work you haven't confirmed,
  and never leave confirmed work sitting at `in_progress`.
- If verification surfaced a problem, capture it (tag `issue`) and keep the task
-  open — a found problem is a pivot to record, not something to quietly skip.
+- If verification surfaced a problem, capture it as its own issue
+  (`create_task(kind="issue")`) and keep the task open — a found problem is a
+  pivot to record, not something to quietly skip.

 ## Honesty over optimism