grounding-brief

Gathers evidence from memory, code search, logs, and tickets into a structured context brief.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/Zhachory1/autopraxis --skill grounding-brief-zhachory1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grounding-brief
Source: https://github.com/Zhachory1/autopraxis/tree/main/skills/grounding-brief
Command: npx skills add https://github.com/Zhachory1/autopraxis --skill grounding-brief-zhachory1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often commit to a direction before collecting enough context, leading to invented facts, duplicated infrastructure, and missed prior decisions. This Skill standardizes the context-gathering step so every workflow starts from sourced facts, explicit assumptions, and a clear readiness gate. ## Core Features & Use Cases - Multi-source evidence collection: Pulls facts from long-term memory MCP, code RAG, git history, PR metadata, logs, tickets, and agent-fleet journals with preserved source pointers. - Capability reuse inventory: Requires checking for existing brokers, services, and platform capabilities before proposing new infrastructure, returning reuse, cannot-satisfy, or clarify-first verdicts. - Proceed gate and telemetry: Emits a ready, clarify-first, council-first, or blocked status plus run-telemetry metrics on source counts, latency, and confidence. - Use Case: Before starting a debug investigation or feature plan, run this Skill to produce a grounding brief that lists relevant prior decisions, conflicting docs, open questions, and whether work can proceed. ## Quick Start Ask the agent to create a grounding brief for your goal, providing any linked docs, tickets, repos, and a time budget before starting the main workflow.

Frequently Asked Questions about grounding-brief

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

FAQPage Schema
How do I gather context before starting an AI agent workflow?▼

Run a grounding brief as step zero: state the goal, supply linked docs, tickets, repos, and a time budget. The skill queries memory, code search, git, and logs, then returns sourced facts, assumptions, open questions, and a readiness gate.

What sources does a grounding brief collect evidence from?▼

It pulls from long-term memory MCP, code RAG or repo indexes, agent-fleet journals, git and GitHub CLI data, logs, traces, metrics, and user-supplied artifacts. Every important claim must carry a source pointer such as a path, URL, or command.

Can the grounding brief propose new infrastructure directly?▼

No. It must first complete a capability reuse inventory of existing services, SDKs, and platform abstractions. Candidates with unknown ownership or access return clarify-first, and new infrastructure proposals are blocked until that inventory resolves.

When should I stop collecting context for a brief?▼

Stop when the evidence supports the next workflow stage or further searching becomes low-yield. The skill enforces a time budget and a proceed gate with statuses ready, clarify-first, council-first, or blocked to prevent unbounded lookup.

What are the limitations of a grounding brief?▼

It depends on the availability and freshness of memory and code RAG sources, so stale decisions or missing indexes can reduce confidence. It also does not execute downstream work; it only prepares context and a readiness decision.