guide-updater

To update project guidelines from conversations without breaking structure, apply incremental patches that add 1-3 bullets per update and introduce no new headings. The guide-updater enforces these constraints and runs a validation script to verify structural integrity before publishing.

Maintaining terminology consistency in living project documentation is achieved by extracting actionable insights from team conversations and consolidating them into the guide. This approach enforces writing consistency and validates the document structure before any changes are committed.

Yes, you can apply incremental patches to markdown guidelines without creating new headings. The process strictly enforces a requirement where no new headings are allowed, ensuring that existing document flow and structural stability are preserved during updates.

Yes, the guide-updater validates document structure before publishing updates. It uses a dedicated validation script called validate_guide.py to ensure that the incremental patches and terminology updates do not disrupt the established project guidelines framework.

You push real-time dialogue insights into a team collaboration guidelines document by running the updater with the guide path argument. This extracts conversation insights and consolidates them into living documents as auditable, incremental bullet-point updates.

Yes, there are limitations on how many bullets you can add per update to project guidelines. The patching process restricts updates to 1-3 bullets per iteration to preserve the flow of the guide and ensure verifiable, incremental document consolidation.