plan-docs-author

Plan-docs structure project planning by guiding section-by-section creation of outcomes, acceptance criteria, halts, smoke tests, and provenance. This enforces traceability and methodology alignment for feature releases and process improvements.

Manage scope and dependencies by drafting per-cycle and master plan decomposition within your plan-docs. This approach ensures scope tightening and dependency management are explicitly documented for comprehensive project clarity and traceability.

Log decisions and cite provenance in dev project plan-docs using structured validation of required sections. This enforces explicit documentation of key decision points and provenance citations, ensuring stakeholder review has full traceability.

You can use this for process improvements as well as new feature rollouts. The plan-doc creation applies to planning cycles, feature releases, and process improvements, providing detailed section-by-section guidance across all these development workflows.

Yes, this planning approach validates required sections within your plan-docs. It ensures comprehensive creation by checking mandatory sections like outcomes, acceptance criteria, halts, smoke tests, and provenance are explicitly documented.