brief

Append timestamped context briefs to plan brief.md files.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill brief-ddaanet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/brief
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill brief-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write a brief.md capturing context (scope changes, decisions, conclusions) for a plan or task. This enables cross-tree context transfer and consistent handoffs between worktrees.

Core Features & Use Cases

  • Captures scope changes, design decisions, and conclusions for a target task.
  • Appends timestamped briefs to plans/<plan>/brief.md, preserving existing content.
  • Used by worktree agents to surface context during task pickup and handoff.

Quick Start

Run /brief <slug> to create a new, timestamped context brief for the target plan.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I capture and share task context across different worktrees?

You can capture and share task context by appending a timestamped brief to plans/<plan>/brief.md, which preserves existing content and enables cross-tree context transfer during handoffs.

What is the best way to document scope changes and design decisions for a task?

Documenting scope changes and design decisions involves writing a context brief that records conclusions and metadata, appending it to a target plan directory for later retrieval.

How do I create a timestamped context brief for a specific plan directory?

Creating a timestamped context brief requires resolving the target plan directory under plans/<arg>/ and appending an entry to brief.md, deriving the plan name from task metadata when needed.

Does writing a brief automatically commit the changes to my repository?

Writing a brief does not automatically commit changes; briefs are not auto-committed and are instead surfaced during the next hc cycle for review.

Can I use context briefs to transfer scope changes between worktree agents?

Yes, context briefs are used by worktree agents to surface task context during pickup and handoff, ensuring consistent cross-tree context transfer for target plans.