goal-mode-tag-discipline

v3.0 Status: Optional / Legacy Path

In v3.0+, tag emission is OPTIONAL. The preferred path is explicit CLI verbs:

• <evidence/> tag → /goal-mode:goal-evidence-add --criterion N --file path[:line] --note "..."
• <task-status>achieved</task-status> → /goal-mode:goal-achieve
• <audit-verdict agent="X" status="GO">text</audit-verdict> → /goal-mode:goal-submit-verdict --agent X --status GO --text "text"
• <review-request agents="X"/> → /goal-mode:goal-review-request then dispatch via Agent tool

The tag-emission path described below remains authoritative for:

• Codex /goal and non-Claude-Code agents that can't invoke slash commands.
• Users who opt in to legacy v2 driver behaviour via stopHookDriver: true config.

For all other Claude Code users in v3.0+, prefer the explicit CLI workflow — it removes the entire class of bugs around tag parsing, fenced-code stripping, attribute quoting, and silent-loop traps that this document spends most of its space describing.

---

Goal-mode tag emission — exact semantics

This skill is the precise reference for the parser in engine/parse-tags.mjs. Use it when you need to know:

• Which exact regex matches a tag
• How code regions are stripped (engine/stop-hook.mjs::stripCodeRegions)
• What attribute quoting rules apply
• What the parser silently drops
• How escape-hatch is detected

For high-level behavior + when-to-emit guidance, use the using-goal-mode skill instead.

Pre-parse: code-region stripping

Before parsing tags, engine/stop-hook.mjs strips:

text.replace(/```[\s\S]*?```/g, '')   // fenced blocks (multiline)
    .replace(/`[^`\n]+`/g, '');       // inline spans (single line)

Implication:

• Tags inside ``` fenced blocks ARE removed before parsing.
• Tags inside inline backticks ARE removed before parsing.
• Tags inside <details>...</details> are NOT stripped — these are HTML, not Markdown code.

Rule for emission: put your machine-parsed tags in prose or inside <details> blocks. Never inside code fences.