Detect and enforce battle plan execution discipline across timelines and verification gates.
npx skills add https://github.com/unheaded/unheaded --skill unheaded-marshal
Please help me install this Agent Skill. Skill: unheaded-marshal Source: https://github.com/unheaded/unheaded/tree/main/skills/unheaded-marshal Command: npx skills add https://github.com/unheaded/unheaded --skill unheaded-marshal
The Marshal provides real-time enforcement and drift detection to keep sessions aligned with plans, ensuring velocity and reducing waste by preventing scope creep and verification gate skips.
Enable the Marshal on the current session to automatically detect drift and enforce the battle plan.
High-intent search queries and answers about installing and using this skill.
To prevent scope creep and enforce project timelines, you need real-time drift detection that triggers redirects when tangents occur. This approach applies policy enforcement across battle plans, timelines, and verification gates to sustain velocity and reduce waste.
Drift detection in project management is the process of monitoring sessions for plan deviations. It works by applying strict adherence checks to timelines, verification gates, and scope boundaries, automatically routing tangents to a parking-lot backlog to prevent wasted effort.
You can enforce verification gates and require justification for plan amendments by applying execution discipline policies to your project. This mechanism ensures strict adherence to scope boundaries and triggers alerts when verification gate skips or unauthorized plan changes occur.
Yes, execution discipline enforcement integrates with Warmonger, Timeguru, and Micromanager to sustain velocity and accuracy. This coordination allows for real-time policy enforcement, commit cadence management, and tangent detection across your battle plans.
The best way to handle tangents and unauthorized scope changes is to use parking-lot backlog routing combined with real-time alerts. This method enforces scope boundaries by detecting scope creep as it happens and redirecting the session back to the original plan.
You should use automated enforcement for project plans during sessions requiring strict adherence to timelines and scope boundaries. It is specifically needed when you must enforce commit cadence, prevent verification gate skips, and ensure plan amendments require formal justification.
brewpirateAudits claim quality and scope drift in AI migration reviews using runtime-evidence scrutiny.
inbharataiGenerate structured meeting minutes with attendance, decisions, action items, and parking lot items.
mrjuguyIntegrate Supabase backend services for authentication, real-time updates, and edge functions.
EojEdredMonitor validators and analyze SSH logs for security threats.
