brief-next-steps

Writes a concise next-steps briefing file from session conclusions into the plans directory.

15|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/fprochazka/claude-code-plugins --skill brief-next-steps-fprochazka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brief-next-steps
Source: https://github.com/fprochazka/claude-code-plugins/tree/main/plugins/sdlc/skills/brief-next-steps
Command: npx skills add https://github.com/fprochazka/claude-code-plugins --skill brief-next-steps-fprochazka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long planning sessions end with conclusions buried in conversation history and lengthy source documents. This Skill compresses what the session landed on into one short briefing file that a user can read in ten minutes and act on, capturing the final proposal in implementation order rather than the argument that led to it. ## Core Features & Use Cases - Session-to-Briefing Compression: Distills the current conversation and existing plan documents into a single Markdown briefing with steps in implementation order. - Decision Tracking: Closes with mandatory sections listing decisions the user still owes and facts not yet verified, so blockers are explicit. - Style Enforcement: Applies the prose:technical-writing skill rules — short active sentences, plain language, no narration of change — with a hard ceiling of roughly 170 lines. - Use Case: After a long architecture discussion about fixing stale mirror data, invoke the skill to produce ./.claude/plans/mirror-refresh-briefing.md containing the agreed steps, open decisions, and unverified assumptions. ## Quick Start Ask the assistant to brief the next steps from this session into a plans file, optionally passing a scope hint or slug for the output filename.

Frequently Asked Questions about brief-next-steps

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

FAQPage Schema
How do I summarize a long planning session into next steps?▼

Invoke the brief-next-steps skill with an optional scope hint or slug. It writes a short Markdown briefing to ./.claude/plans/ containing the final proposal in implementation order, open decisions, and unverified facts.

What format does the next-steps briefing file use?▼

The briefing is a Markdown file capped at roughly 170 lines with two or three sentences of context, steps in implementation order named by problem, a closing list of decisions the user owes, and a not-yet-verified section.

Can the briefing skill research missing information?▼

No. The skill never explores for new material; missing facts go into the not-yet-verified section. Its sources are the current session, existing plan files, and docs already read.

Where is the briefing file saved?▼

It is written to the worktree-local ./.claude/plans/ directory as <slug>-briefing.md. Existing files with the same slug are overwritten wholesale since a briefing is a snapshot of current state.

When should I not use a session briefing?▼

Avoid it when you need the full reasoning, alternatives, or revision history — the briefing contains only the final proposal. The long source documents remain the reference for detailed argumentation.