---
name: snipara-context-workflow
description: "Use Snipara Hosted MCP for project context, reviewed memory, source-grounded answers, code graph context, workflow mode selection, and durable task closeout. Use when an agent starts a task, resumes work, answers project-specific questions, edits code, or needs to distinguish source truth from memory."
---

# Snipara Context Workflow

## Source Order

Start from Hosted MCP at `https://api.snipara.com/mcp/YOUR_PROJECT_SLUG`, then local files and tests for exact current state.

1. Validate Snipara tool availability with `snipara_help`, `snipara_settings`, or a lightweight context query.
2. Use `snipara_recall` for durable decisions, preferences, validated learnings, and session carryover.
3. Use `snipara_context_query` for documents, product truth, runbooks, architecture notes, source material, and answer packs.
4. Use `snipara_get_chunk` before relying on precise wording from returned references.
5. Use local `rg`, file reads, git commands, lint, type-checks, and tests for exact working-tree truth.

## Workflow Modes

- LITE: small known-file work with low risk.
- STANDARD: normal project work that benefits from context and code graph follow-up.
- FULL: multi-file, risky, release/deploy, auth, billing, schema, migration, architectural, or compaction-prone work.
- Orchestrated FULL: work that needs htasks, production proof gates, routing, or parallel workers.

Use Companion for managed workflow state when available:

```bash
npx -y snipara-companion@latest workflow start --goal "<goal>" --plan-file <plan.json>
npx -y snipara-companion@latest workflow phase-start <phase_id>
npx -y snipara-companion@latest workflow phase-commit <phase_id> --summary "<outcome>" --files <files...>
npx -y snipara-companion@latest workflow resume --include-session-context
```

## Code Graph And Impact

Use exposed `snipara_code_*` tools for structural questions such as callers, imports, neighbors, paths, symbol cards, and impact. When Companion is installed and the local worktree may be dirty or ahead, prefer Companion code commands because they can select a local overlay and report `sourceSelection`.

Run impact before risky multi-file changes, PR reviews, route/service/job changes, auth, billing, deployment, schema, migrations, or explicit gap analysis.

## Memory Closeout

End substantial work with `snipara_end_of_task_commit` or a managed Companion phase/final commit. Store only durable decisions, learnings, preferences, todos, and reusable context. Never store secrets, raw logs, transient command output, or guesses.