Change Planning

Get the Codebase Overview

Start by reading the codebase map to understand the high-level structure:

"Show me the codebase map"

Uses: map://current resource

Look for:

• Community names and purposes
• Cohesion scores (how tightly coupled)
• Cross-community flows

Search for Relevant Code

Use semantic search to find code related to your task:

"Search for code related to user notifications"

Uses: noodlbox_query_with_context tool

This returns processes ranked by relevance with full context.

Explore the Target Community

Drill into specific modules to understand their boundaries:

"Show me details about the Notifications community"

Uses: map://current/community/{id} resource

Focus on:

• Entry points (where to hook in)
• Key symbols (important functions/classes)
• Internal processes

Trace Execution Flows

Understand how existing code executes:

"Trace the sendEmail process"

Uses: map://current/process/{id} resource

See the exact function call sequence to understand integration points.

Map Dependencies

Before planning your implementation, understand what code you'll depend on:

"What functions call EmailService.send?"

"What does NotificationManager depend on?"

Uses: noodlbox_raw_cypher_query tool

// Find callers of a function
MATCH (caller)-[:CALLS]->(target:Symbol {name: "send"})
RETURN caller.name, caller.file_path

// Find dependencies of a class
MATCH (source:Symbol {name: "NotificationManager"})-[:CALLS]->(dep)
RETURN DISTINCT dep.name, dep.kind

Understand Current State

"Show me the codebase map"

Find the Notifications community and note its cohesion score.

Find Existing Patterns

"Search for notification sending patterns"

Review how email notifications are currently implemented.

Identify Integration Points

"What calls NotificationService.notify?"

These callers will need to support push notifications too.

Map the Extension Points

"Show me the NotificationService community details"

Identify where to add push notification logic without breaking existing behavior.