FG-0210 Standing Orders
Description
Maintain persistent directives that remain in effect across all sessions. Standing Orders are instructions that don't need to be repeated every session: they are always active. They cover recurring requirements like commit message format, code style, documentation standards, and behavioral expectations. Standing Orders reduce session startup overhead and ensure consistency even when context is limited.
Implementation
Document 10-20 standing orders that cover the most common recurring requirements. Place them where agents read them at session start (project configuration files, system prompts, or reference documents). Review quarterly: remove orders that are no longer relevant, add orders for recurring issues. Keep each order to one actionable sentence.
Success Indicators
- Agents follow standing orders without being reminded
- Common tasks are executed consistently across sessions
- Session startup time decreases because standing context is already established
- Standing orders evolve based on observed patterns, not assumptions
Failure Modes
- Too many standing orders: cognitive overload prevents internalization
- Standing orders that conflict with session-specific instructions
- Orders never reviewed or updated: become stale and ignored
- Standing orders used as a substitute for proper session context