goal-mode-tag-discipline

Enforce exact regex and quoting rules for goal-mode tag emission.

3|1|Updated May 9, 2026
One-click install
npx skills add https://github.com/lokafinnsw/claude-code-goal-mode --skill goal-mode-tag-discipline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: goal-mode-tag-discipline
Source: https://github.com/lokafinnsw/claude-code-goal-mode/tree/main/skills/goal-mode-tag-discipline
Command: npx skills add https://github.com/lokafinnsw/claude-code-goal-mode --skill goal-mode-tag-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of unreliable goal-mode automation when complex tags (evidence, verdicts, status, and review requests) are emitted with formatting issues that cause the engine to silently drop or misinterpret them.

Core Features & Use Cases

  • Exact tag emission semantics: Know the precise regex matches, required attributes, quoting rules, and what is silently ignored.
  • Engine-aligned pre-parsing behavior: Understand fenced-code and inline-backtick stripping so tags aren’t accidentally removed before parsing.
  • Safety/guardrail guidance for verdicts: Avoid fabricated audit-verdicts by matching reviewer independence and using the correct escape-hatch wording.
  • Ordering and application rules: Ensure tags appear in a form that the engine’s parse-and-apply pipeline will actually consume as intended.

Quick Start

Use goal-mode-tag-discipline before you emit a multi-line evidence or audit-verdict block to confirm your tags are parseable and will not be silently dropped.

Frequently Asked Questions about goal-mode-tag-discipline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my Claude Code goal-mode tags silently dropped during parsing?

Goal-mode tags are silently dropped when formatting issues, incorrect quoting, or invalid attributes fail the engine's exact regex requirements. This skill provides authoritative parseTags semantics to ensure tags are recognized and applied.

How do I emit goal-mode evidence and audit verdicts that the engine will parse correctly?

To emit goal-mode evidence and audit verdicts correctly, follow exact tag emission semantics including required attributes, quoting rules, and proper ordering. This skill validates tags against the engine's parse-and-apply pipeline to prevent misinterpretation.

Does fenced-code stripping remove inline goal-mode tags before parsing?

Fenced-code and inline-backtick stripping can accidentally remove goal-mode tags before parsing if not handled correctly. This skill provides engine-aligned pre-parsing behavior to ensure tags survive code-region stripping constraints.

What is the REVISE escape-hatch prefix in goal-mode workflows?

The REVISE escape-hatch prefix is a detection mechanism in goal-mode workflows to bypass automated processing. This skill enforces correct escape-hatch detection to prevent fabricated audit-verdicts and validate reviewer independence.

How do I validate reviewer independence for goal-mode audit verdicts?

Validating reviewer independence for goal-mode audit verdicts requires matching specific guardrail criteria and avoiding fabricated verdicts. This skill provides safety guidance to ensure verdicts meet the engine's reviewer-independence validation rules before emission.

Can I use goal-mode tag discipline with legacy v2 tag-emission paths?

Yes, this skill applies to legacy v2 tag-emission paths in Claude Code goal-mode workflows. It enforces exact regex requirements and quote-aware attribute parsing to make legacy tags parseable and prevent silent engine drops.