One-click install
npx skills add https://github.com/Dicklesworthstone/eidetic_engine_cli --skill situation-framing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: situation-framing
Source: https://github.com/Dicklesworthstone/eidetic_engine_cli/tree/main/skills/situation-framing
Command: npx skills add https://github.com/Dicklesworthstone/eidetic_engine_cli --skill situation-framing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps coding agents classify tasks and select an evidence-backed set of eidetic memory (ee) commands, while preventing the agent from making unsupported judgments inside the Rust CLI.

Core Features & Use Cases

  • Task classification & framing: Produces a structured task frame (e.g., bug fix, feature, investigation) suitable for agent handoff.
  • Evidence-driven command selection: Drives the agent to fetch readiness, context packs, and targeted search/why explanations from ee using machine-readable JSON.
  • Degraded-mode safety: Detects degraded or unavailable ee capabilities and stops conclusions that would require missing evidence, with explicit repair commands.
  • Privacy and prompt-injection guardrails: Enforces redaction checks and quarantine-aware handling of prompt-injection-like evidence.
  • Output packaging for downstream implementation: Returns a compact YAML artifact including risk checks, evidence gaps, and nextAction.

Quick Start

Use the situation-framing skill to turn a user task into an evidence-backed task frame by first running ee status, then pulling context or searching for missing facts, and finally producing the YAML handoff artifact without claiming judgment from the CLI.

Frequently Asked Questions about situation-framing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create evidence-backed task plans for coding agents?

Evidence-backed task plans are created by transforming coding-agent requests into a structured task frame that classifies the work, then selecting relevant memory commands to gather supporting facts before producing a YAML handoff artifact.

What is degraded mode handling for coding agents and when is it needed?

Degraded mode handling detects when memory capabilities are unavailable or incomplete, stopping the agent from drawing unsupported conclusions and providing explicit repair commands to restore evidence access.

How do I prevent prompt injection in coding agent evidence gathering?

Prompt injection is prevented through redaction checks and quarantine-aware handling that isolates suspicious evidence, ensuring the agent processes only validated inputs within strict JSON interaction boundaries.

Can I use JSON command orchestration to frame bug fixes and refactoring tasks?

JSON command orchestration frames bug fixes, features, refactors, investigations, docs updates, and deploy preparations by driving the agent to fetch readiness, context packs, and targeted search explanations using machine-readable JSON.

What's the best way to package a coding agent task frame for downstream implementation?

The best way is producing a compact YAML artifact that includes risk checks, evidence gaps, and nextAction fields, creating a self-contained handoff package suitable for agent-to-agent or human-to-agent implementation transfer.

Why does my coding agent make unsupported judgments without evidence?

Unsupported judgments occur when agents lack evidence-driven command selection; the solution requires enforcing strict interaction boundaries that mandate evidence gap reporting and prevent conclusions requiring missing facts.