Skip to content
Back to skills

Exploration Session Brief

ASecurity

Co-authors exploration session briefs at the wide end of the exploration funnel. Captures and refines core intent across software, business processes, or strategic roadmaps.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentstesting

Security analysis

A100/100

Pro scans all 8 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add richfrem/agent-plugins-skills --skill exploration-session-brief --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Exploration Session Brief?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Exploration Session Brief
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/richfrem-exploration-session-brief/badge)](https://www.skillsdirectory.com/skills/richfrem-exploration-session-brief)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: exploration-session-brief
description: Co-authors exploration session briefs at the wide end of the exploration funnel. Captures and refines core intent across software, business processes, or strategic roadmaps.
---

# Exploration Session Brief (exploration-session-brief)

Co-authors exploration session briefs at the wide end of the exploration funnel, capturing and refining core intent into structured, reader-tested briefs.

## Contents
- [Critical Constraints](#critical-constraints)
- [Quick start](#quick-start)
- [Workflow](#workflow)
- [Verification](#verification)
- [References](#references)

## Critical Constraints
- Remain solution-agnostic until domain requirements dictate otherwise.
- Never invent stakeholder personas, constraints, or unverified assumptions; flag gaps as `[UNCONFIRMED]`.
- Always write finalized briefs directly to `exploration/session-brief.md`.

## Quick start
1. Initiate context gathering with domain, trigger event, and raw material inputs.
2. Propose tailored outline: Problem Statement, Stakeholders, Current vs Desired State, Constraints, Open Questions.
3. Iteratively draft concise sections and perform reader blind-spot testing.

## Workflow
1. **Context Gathering**: Inquire in a single message regarding domain scope, trigger pain points, and existing transcripts or notes.
2. **Section Refinement**: Propose domain-tailored sections and draft iteratively (2–5 sentences per section).
3. **Reader Testing & Blind Spots**: Predict 3 specific unaddressed questions from the primary reader; resolve inline or record under `## Open Questions`.
4. **Finalization**: Package verified brief into `exploration/session-brief.md`.

## Verification
- Confirm `exploration/session-brief.md` exists and contains all required sections.
- Verify all unconfirmed assumptions are marked `[UNCONFIRMED]`.
- Ensure open reader questions are documented with explicit follow-up owners.

## References
- [acceptance-criteria.md](references/acceptance-criteria.md)
- [architecture.md](references/architecture.md)

Files in this skill

  • SKILL.md6.1 KB
  • acceptance-criteria.md175 B
  • evals/evals.json1.1 KB
  • evals/results.tsv60 B
  • intake-agent.md28 B
  • references/acceptance-criteria.md25 B
  • references/architecture.md35 B
  • scripts/execute.py53 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…