/brief

Distill project intent into a timestamped brief with YAML frontmatter.

Updated Apr 9, 2026

Search Tags:#design #planning #process #project-management #briefing #brief #decision-record

Ready to run

npx skills add https://github.com/fnkydcks-lab/dt-foundry --skill brief-fnkydcks-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /brief
Source: https://github.com/fnkydcks-lab/dt-foundry/tree/main/brief
Command: npx skills add https://github.com/fnkydcks-lab/dt-foundry --skill brief-fnkydcks-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distills project intent into a concise brief before any code is written, ensuring early alignment and clarity.

Core Features & Use Cases

Produces a single, timestamped brief capturing problem, person, promise, and constraint.
Ensures the brief is created at the start of any feature, sprint, or product decision to guide design and engineering.
Serves as a decision-record that can be referenced to validate decisions and scope.

Quick Start

Run /brief at the start of a feature or sprint to generate the brief.

Frequently Asked Questions about /brief

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

FAQPage Schema

What is a project brief and why do I need one before writing code?▼

A project brief distills project intent into a concise record before development begins. It ensures early alignment by capturing the core problem, target user, and constraints, preventing scope creep and miscommunication.

How do I create a design brief for a new feature or sprint?▼

To create a design brief for a new feature, run a briefing process at the start of the sprint. This generates a timestamped record with YAML frontmatter capturing the design intent, problem, and constraints.

Can I use a brief as a decision record for project management?▼

Yes, you can use a brief as a decision-record. The timestamped project brief serves as a reference document to validate scope and engineering decisions throughout the project lifecycle.

What is the best way to document project intent and constraints early?▼

The best way to document project intent is to capture a concise brief before any code is written. This ensures alignment on the problem, user, promise, and constraint, guided by YAML frontmatter.

When should I generate a project brief in the development process?▼

You should generate a project brief at the start of any feature, sprint, or product decision. Applying the briefing process early ensures alignment on the design intent before engineering work begins.

Does the project brief format support YAML frontmatter for metadata?▼

Yes, the project brief format supports YAML frontmatter. The generated brief is a timestamped document that uses YAML frontmatter to define the design intent, including the project name and description.