Preserve project context and navigate repository code

Preserve the decisions and work context an agent needs in My Architect, then use repository navigation to inspect the implementation. These serve different purposes: a project checkpoint explains the task and its ownership; a code index helps locate candidate files and symbols.

Make the project context retrievable

Link requirements, accepted decisions, canonical documents, and implementation evidence to the relevant feature and work. Record a concrete next step when progress changes. Keep uncertain outcomes and unresolved questions explicit.

When an agent resumes, it should read the checkpoint and refresh the live context and claims. It should not reconstruct the project solely from an old conversation or assume that a saved next step remains outstanding. Follow resume and handoff.

Use scoped context to retrieve the relevant manifest and complete source records. A compact summary helps choose what to read, but does not replace mandatory details, specification variants, or source gaps.

Use a code index as a navigation aid

The workflow plugin includes recursive-context guidance for large inputs and optional code-graph navigation. When a repository already has a supported index, the agent can use it to find candidate regions before reading the current code.

For the documented Graphify workflow, freshness uses the index’s built_at_commit value compared with the repository’s current commit. File modification time alone does not identify the indexed revision. Also account for relevant uncommitted changes before relying on a candidate.

Verify each important claim against current source files. A graph relationship is a lead, not proof that behavior exists or that every caller has been found. Missing symbols, stale indexes, generated files, and dynamic behavior may require ordinary search and targeted reads.

If no index is available, continue with scoped searches and source inspection. Installation or rebuilding uses the applicable tool and project instructions; connecting My Architect does not silently build a graph for every repository.

Measure whether indexing helps your task

Indexing can reduce repeated discovery for some repository questions. It does not remove the need to inspect requirements, implementation, or test results. There is no universal token, latency, or cost reduction promised by this workflow.

Compare the actual task, coverage, and total effort—including delegated agents—when evaluating the benefit. A shorter answer or fewer visible tool calls is not sufficient evidence of complete or cheaper work.

Prompt to copy

Resume the task from its My Architect records. Refresh the relevant sources and ownership. Use an existing code index to find candidate files when useful, check its freshness, and verify conclusions in current code. Preserve decisions, evidence, gaps, and the next step for the next session.

Continue with read project context or project workflow.

Verified against app/MCP 1.11.0 and workflow plugin 2.6.0 on October 13, 2026. Confirm the connected server’s capabilities before applying a procedure.