operational-constraints

What problem does it solve?

Operational drift and inconsistent execution cause LLM agents to waste tokens, misuse tools, duplicate work, and produce unreliable plans—especially during complex multi-step or long-horizon sessions.

Core Features & Use Cases

• Token & context efficiency guardrails: reduces verbosity, encourages context compaction at thresholds, and prevents redundant confirmations.
• Research & tools protocol: standardizes how documentation and current info are retrieved (e.g., Context7-first with fallback) and when to use pattern vs structural search.
• Parallel execution mandate: explicitly requires evaluating independent subtasks and parallelizing when beneficial.
• Development discipline: enforces engineering standards, TDD (RED → GREEN → REFACTOR), and requires impact analysis for ALL code changes.
• System mapping pre-flight: provides a 5-point checklist to understand architecture, flows, logging, dependencies, and environment before modifications.
• Planning output protocol: requires approval gating and a structured plan output including the Engineering Standards Declaration.

Quick Start

Invoke operational-constraints at session start by giving the instruction: "Enable operational-constraints constraints using /ops-mode for disciplined execution."