Use codebase insight to choose the next engineering action.
Start from the local brief, relevant dependencies and prioritized candidates. Investigate selected candidates, decide what to change, and focus verification on the important paths. Reuse and refresh the analysis as work continues.
Example: plan a refactor around a shared routing component.
ILLUSTRATIVE TEAM WORKFLOW · SETSUMEI INFORMS; YOUR TEAM DECIDES
- PROPOSE
Start with an edit
You plan to change a routing component. Use the brief or an MCP query to orient to its role.
- TRACE
Inspect dependencies
Trace callers, dependencies and important paths. Check unresolved relationships before setting the review scope.
- CHECK
Review candidates
Inspect nearby findings and source. Optionally investigate selected candidates; decide what needs action or further evidence.
- VERIFY
Change, test, refresh
Record the chosen action, make and verify the edit, then refresh analysis after relevant changes.
Keep the evidence and action together.
Keep the selected evidence, open questions, owner and verification work in your team’s existing review tools. This illustrative checklist describes a useful team practice; it does not imply automatic work-tracker synchronization or shared decision-history storage in Setsumei.
ILLUSTRATIVE REVIEW CHECKLIST
status: accepted | revised | rejected
supporting evidence + next action
source state + analysis run + freshness
investigation run + available evidence
Test the workflow on a change your team is already reviewing.
Evaluate how your engineers use the local brief, relationships and coding-agent queries to orient, investigate and plan the work.