planning-implementation

Standardize agent planning by enforcing a structured plan.md template that maps vertical slices to specific file modifications and acceptance tests. This methodology breaks complex features into actionable, file-level steps to prevent implementation drift.

Prevent implementation drift by generating a scannable, scoped tactical plan that enforces strict rules for atomic commits. This structured methodology requires precise file-level steps and acceptance test mappings to keep the implementer agent focused.

Generate a tactical plan by invoking the planning skill to create a structured playbook for the current feature request. The plan maps vertical slices to specific file modifications, keeping the document under 300 lines for scannable verification.

Yes, tactical planning implements strict scope enforcement rules that ensure atomic, verifiable commits for each vertical slice. This approach maintains a working codebase throughout the software development process by mapping acceptance tests to file modifications.

A key limitation is that structured tactical plans must stay under 300 lines to remain scannable, which may restrict use on exceptionally large features. The methodology specifically targets complex software development workflows requiring precise file-level steps.

Autonomous agents lose scope due to ambiguity in development tasks. A rigorous, scannable methodology that maps vertical slices to specific file modifications and acceptance tests provides the step-by-step playbook needed to avoid scope creep.