ado-feature-planning

Azure DevOps feature planning automates story decomposition by transforming ideas into ADO-ready user stories with clear boundaries, dependencies, and acceptance criteria. Provide a feature idea or planning document to generate structured work items.

Strategic feature planning uses live interviews or planning docs to probe for hidden requirements and edge cases before writing any documents. This ensures complex features are fully scoped with explicit boundaries and dependencies before ADO work item creation.

You can auto-create ADO work items by configuring an ADO MCP server, which allows the feature planning process to automatically generate Features, User Stories, and dependencies directly in Azure DevOps from your planning documents.

Yes, feature planning consumes existing markdown planning documents like FEATURE_OVERVIEW.md, REQUIREMENTS.md, and IMPLEMENTATION_PLAN.md to generate right-sized ADO user stories without needing a live interview session.

No, an MCP server is optional for feature planning and story decomposition. You only need it configured if you want to automatically create real Features, User Stories, and dependencies directly in your Azure DevOps environment.

Feature planning uses QMD indexing to save creation manifests, enabling cross-session retrieval of generated ADO work items and planning documents. This ensures you can resume or reference previous feature planning sessions.