mpx-add-requirements

To keep your project specification up to date, you can add or refine requirement checklists incrementally. This approach converts ambiguous input into precise, testable items while preserving your original details and marking implemented scope as complete.

You can automatically regenerate a roadmap after updating requirements by invoking a spec analyzer workflow. This mechanism updates derived roadmap artifacts and phase checklists immediately after any specification changes are made.

Normalizing and deduplicating requirement checklists for TDD planning involves converting raw user input into precise, testable items. This ensures your specification remains a single source of truth without redundant or ambiguous acceptance details.

Yes, the mpx-add-requirements workflow supports markdown specifications by using a SPEC.md file as the single source of truth. It preserves user-provided details and maintains checkbox-style requirements for clear tracking.

Yes, you can clarify missing acceptance details before writing a specification checklist. The workflow is designed for specification authoring where requirements are provided incrementally and ambiguous details must be resolved beforehand.

Phase checklists fall out of sync with a project specification when updates are made manually without regenerating derived artifacts. Automatically invoking a spec analyzer after every change ensures roadmap and phase checklists stay consistent.