Verified:GitHub

brief

Write a cold-start task briefing file to /tmp/<descriptive-slug>-task.md.

4|1|Updated Mar 11, 2026

Search Tags:#agent handoff #git workflows #task briefing #safety gating #priority execution #tmp artifacts #commit authorization

Ready to run

npx skills add https://github.com/jcdendrite/claude-config --skill brief-jcdendrite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/jcdendrite/claude-config/tree/main/claude/.claude/skills/brief
Command: npx skills add https://github.com/jcdendrite/claude-config --skill brief-jcdendrite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an abandoned or settled piece of work into a cold-start briefing that a fresh session can safely execute without relying on prior conversation context.

Core Features & Use Cases

Cold-start task briefing generator: Writes an operational task file to /tmp/<descriptive-slug>-task.md with a consistent structure and required preamble.
Clear separation of states: Distinguishes when to use /brief versus /handoff (mid-flight continuation) and versus /plan-it (design/planning outputs).
Safety-first execution guidance: Enforces a split between autonomously safe steps and steps requiring explicit engineer authorization, including irreversible/shared-state actions.

Quick Start

Ask the agent to run the brief skill to create a new execution-ready task file for a settled, abandoned PR or ticket.

Frequently Asked Questions about brief

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

FAQPage Schema

How do I create a task briefing for a fresh agent session without prior conversation context?▼

To create a task briefing for a fresh agent session, use the brief skill to generate a cold-start task file at /tmp/<descriptive-slug>-task.md. This artifact enables a new session to resume well-scoped execution without relying on conversation memory.

How does a cold-start task briefing separate safe autonomous steps from irreversible actions?▼

A cold-start task briefing separates execution by structuring the task file into reversible autonomous steps and irreversible actions. The irreversible actions require explicit engineer authorization, ensuring safety gating before any shared-state modifications occur.

When should I use a task briefing versus a mid-flight handoff for an abandoned PR?▼

Use a task briefing for abandoned PRs or settled tickets needing a cold-start execution artifact. A mid-flight handoff is for continuing active work, while a task briefing resumes well-scoped work without prior conversation memory.

What is the required file format and structure for generating a task briefing artifact?▼

The task briefing artifact requires writing to /tmp/<descriptive-slug>-task.md. This file must include a required preamble and structured sections that separate autonomously safe steps from irreversible actions needing explicit engineer authorization.

Do I need any dependencies to generate a task briefing for abandoned git work?▼

No dependencies are required to generate a task briefing for abandoned git workflows. The skill operates independently to produce the cold-start task file in the /tmp directory for your settled tickets or follow-up work.

Why does task briefing execution fail without explicit engineer authorization for shared-state actions?▼

Task briefing execution gates shared-state actions because the skill enforces a safety-first execution model. It splits reversible autonomous steps from irreversible actions, requiring explicit engineer authorization to prevent unintended modifications.