Start with Reqode
Build & Change

Product Understanding

Understand the system before delegating a feature. Trace its current behavior, implementation, dependencies, and the reasons behind earlier changes.
Start with Reqode
Start with Reqode
PR-41 · 1 / 5
Ask in your own words
1 of 5

Ask in your own words

Why can't I cancel a work order after dispatch? A short question is enough; the expert finds the project context.

One Product Map for Humans and AI

Use linked specifications, implementation, and history to answer the question at hand.

Structured specs

Requirements, data entities, API operations, user interfaces, wireframes, tests, revisions, and branch-effective views.

Software units

A catalog of subsystems, units, files, dependencies, implementation guidelines, and unit-to-spec relations.

Change reasons

Change Requests connect goals, branches, affected specs, revisions, affected subsystems, and AI session summaries.

Problem signals

Findings and alignment checks show where code, specs, unit ownership, or architecture rules need attention.
Ask the Product

AI Product Expert answers with evidence

Ask AI Product Expert a question or start from a module, specification, unit, or file. Its read-only investigation returns references, source files, limitations, and suggested next actions.

It returns a structured answer with referenced artifacts, related source files, limitations, and recommended next actions.

Questions teams can ask

How does this flow work today?
Which specs, units, and files define this behavior?
Why was this API or UI behavior changed?
What could break if we change this rule?
Should the fix be in code, specs, units, or a Change Request?
FieldDesk REQ-1 Assign a technician to a visit, Code view: linked Software Units in BACKEND and OFFICE with synchronization and alignment status.
REQ-1 → Code: find the Software Units that implement technician assignment.
More views
REQ-1 Code view with linked Software Units and OFFICE commit 129c8fe5 and BACKEND commit 982090ff, including dates and author.

Follow the requirement to its implementation commits across subsystems.

U-43 AssignTechnicianAction opened from REQ-1: source path /app/Actions/Scheduling/AssignTechnicianAction.php, synchronized dev file, and consumer U-206 VisitController.

U-43: inspect the source-file path and the controller that uses this unit.

FieldDesk source viewer for app/Actions/Scheduling/AssignTechnicianAction.php, showing the PHP implementation and synchronized file status.

Open the synchronized source file to inspect the assignment logic.

Traceability

Trace from intent to files and back

Follow specifications through software units to the files that implement them.

Navigate behavior, files, commits, Findings, and change context in either direction.

Product Understanding Workflow

Start from a question or a known artifact.

1

Choose a starting point

Use a module, requirement, API operation, UI, data entity, unit, source file, Change Request, Finding, issue, or test.

2

Explore the product map

Move through catalogs and relations to see current behavior, architecture, implementation, known problems, and change history.

3

Ask AI Product Expert

Use AI Product Expert when context spans multiple artifacts or code areas and the team needs references and source files.

4

Decide next action

Keep the answer, update specs with AI Analyst, hand off keys to a coding agent, adjust unit links, or create a Change Request.

5

Preserve the decision trail

Use Change Requests for meaningful changes so reasons, affected specs, branches, and AI sessions stay visible.

6

Verify after action

Use alignment checks and Findings to confirm that specs, units, files, and product behavior still match.

Product Knowledge Use Cases

Use the same context for onboarding, planning, review, and support.

Onboard faster

New developers and analysts can inspect modules, artifacts, units, files, and known findings without waiting for a long handover.

Answer how it works

Ask AI Product Expert to explain current behavior with references to requirements, APIs, UIs, data entities, units, and source files.

Understand why it changed

Open Change Requests, affected specs, revisions, branch context, and linked AI sessions to reconstruct product decisions.

Plan product changes

Investigate affected requirements, API operations, UI screens, data entities, units, tests, risks, and implementation options.

Start from code

Trace a source file back to its software unit, linked specs, product behavior, and unit-specific implementation guidelines.

Investigate mismatches

Open Findings to see evidence, severity, affected artifacts, and solution paths for code, specs, units, or architecture.