Phase 1: Missing Code Detection

Phase 1: Missing Code Detection validates whether documented requirements are implemented in the connected code repository. In this phase, User Stories act as the baseline, and WalnutAI verifies whether corresponding functionality exists in the selected code branches.

• Before starting the analysis:

  • The project must contain User Stories in the Action Items.

  • Ensure all required stories are created and available, these stories will be used as the reference for comparison against the codebase.

• To start the analysis:

  • Click Start Analysis.

  

  • Select one or more connected repositories (repositories that were linked during project creation).

  

  • Click "Start Analysing" to begin evaluation and start Analysing.

  
• During analysis:

  • WalnutAI compares each user story with the selected repository branches.

  • It checks whether the requirement is fully implemented.

  • It detects partially implemented functionality.

  • It identifies requirements that are not implemented at all.

• After the analysis completes, the Analysis Summary section displays:

  • Stories Analysed – Total number of user stories evaluated.

  • Gaps Found – Total number of gaps identified.

  • Coverage % – Overall implementation coverage based on analysis.

  • A breakdown of Missing, Incomplete, and Outdated counts.

  

  
• When a user clicks on a specific user story, the AI Recommendations panel displays suggestions such as:

  • Implementation suggestions

  • Displays estimated effort (if available).

  • Highlights missing elements.

  • Shows related code references with match percentage.

  • Recommends an approach to close the identified gap.

• The Confidence Score indicates how strongly the implementation aligns with the requirement based on WalnutAI’s semantic comparison.

• Click Run New Analysis to re-evaluate the selected user stories against the latest code changes and update the analysis results accordingly

Phase 1 ensures every user story is validated against the codebase, clearly identifies missing or incomplete implementations, maintains requirement-to-code traceability, and enables teams to proactively resolve gaps before release.