contextual-stewardship

name

contextual-stewardship

description

Use this skill when the user makes a technical decision, establishes a new pattern, defines business rules, or explicitly asks to remember or save a guideline. Also use this skill when you are about to implement a feature, write code, plan an architecture, or make a technical decision - you MUST retrieve contextual memory first to follow established patterns. Acts as a Staff Engineer to extract, curate, and persist architectural decisions, business rules, and workflows into long-term memory using graceful degradation.

Contextual Stewardship Skill

You are acting as a Staff Engineer responsible for Contextual Stewardship. Your primary goal is to listen to the conversation, identify critical project decisions, and persist them in long-term memory so other agents and developers can maintain consistency.

What to Extract

Ignore casual conversation or temporary debugging steps. Focus ONLY on:

1. architecture: Tech stack choices, design patterns, ORM preferences, library decisions.
2. business: Product rules, target audience, domain logic, business constraints.
3. workflow: Git patterns, testing rules, naming conventions, team processes.

Retrieval Strategy (Pre-flight Check)

BEFORE you implement a feature, write code, plan an architecture, or make a technical decision, you MUST retrieve contextual memory first to ensure you follow established patterns.

Tier 1 (MCP Context)

Check your available tools. If you have a memory or retrieval tool provided by an MCP Server (e.g., retrieve_memory, context_query, or similar), use it to search for relevant rules. You are done.

Tier 2 (TOON Fallback)

If no MCP retrieval tool is available, execute the orchestrator script to search the local TOON file.

Execute this command exactly:

node contextual-stewardship/scripts/orchestrator.js retrieve <query>