framework-context

name	framework-context
description	Load and synthesize framework architecture context for reflection and planning tasks.
version	1.1.0
model	sonnet
invoked_by	both
user_invocable	true
tools	["Read","Skill"]
error_handling	graceful
streaming	supported
verified	true
lastVerifiedAt	"2026-02-22T00:00:00.000Z"
source	builtin
trust_score	100
provenance_sha	2d1d97ef8eef4f7e

Framework Context

Overview

Provide a consistent, source-anchored model of this framework so agents can reason about system-level behavior without guessing.

When to Use

• System-level reflection or metacognitive assessment
• Planning tasks that depend on routing/memory/workflow architecture
• Capability-gap analysis before recommending ecosystem evolution

Iron Laws

1. ALWAYS load framework context before any system-level reflection, planning, or capability-gap analysis — reasoning about architecture without grounding produces hallucinated paths and phantom agents.
2. NEVER fabricate file paths or agent names that are not confirmed by reading canonical sources — invented paths break downstream agents that try to use them.
3. ALWAYS scope the context load to only what the consuming task needs (memory, agents, workflows, hooks, or all) — loading all sources for a narrow task wastes tokens and buries relevant signals.
4. NEVER write or modify framework files from within this skill — framework-context is read-only; mutations require the appropriate creator/updater skill.
5. ALWAYS report missing sources explicitly as missing source: <path> rather than silently omitting a section — silent omissions cause downstream agents to make decisions on incomplete context.

Anti-Patterns

Anti-Pattern	Why It Fails	Correct Approach
Skipping context load before reflection	Reflection uses stale or hallucinated routing/memory assumptions	Always invoke framework-context first; never reflect from memory alone
Loading full all scope for a narrow task	Token budget consumed by irrelevant sections; key signal buried	Pass --scope memory or --scope agents to limit output to what's needed
Inferring file paths from naming conventions	Paths change; inferred paths break agent pipelines	Always read canonical sources and report actual paths found
Writing to framework files inside this skill	Bypasses creator workflow and post-creation integration steps	Use appropriate creator/updater skill for any write operations

Framework grounding skill for memory architecture, routing, workflows, hooks, and directory layout. - Produce scoped context summaries (`memory`, `agents`, `workflows`, `hooks`, `all`) - Anchor every section to concrete repository paths - Standardize framework context output for reflection/planning consumers **Example Invocations**: