brief

Capture project context and requirements through a guided interview process.

Updated May 7, 2026

Search Tags:#workflow #planning #development #documentation #orchestration #track-management

Ready to run

npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill brief-ataraxiaepiphany

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/AtaraxiaEpiphany/conductor/tree/main/skills/brief
Command: npx skills add https://github.com/AtaraxiaEpiphany/conductor --skill brief-ataraxiaepiphany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of poorly defined development tracks by enforcing a rigorous, interview-based process to capture project context, goals, and constraints before any planning begins.

Core Features & Use Cases

Guided Discovery: Uses a state-aware interview process to ensure all critical project dimensions are addressed.
Authoritative Planning: Generates a durable brief.md file that acts as the single source of truth for subsequent planning phases.
Use Case: When starting a new feature, use this skill to grill the requirements and generate a formal brief that prevents scope creep and ensures alignment with existing project documentation.

Quick Start

Invoke the brief skill with a short description of your new feature to begin the guided interview process.

Frequently Asked Questions about brief

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

FAQPage Schema

How do I create a structured project brief for software development?▼

A project brief is generated through an interactive, state-managed interview process that captures comprehensive project context and requirements. The resulting brief.md file serves as the authoritative source of truth for subsequent planning phases.

What is the best way to prevent scope creep when starting a new development track?▼

Preventing scope creep requires generating a formal project brief that captures all constraints and goals. This Skill enforces workflow discipline by requiring a shared understanding of project context before any planning phase begins.

How do I document project requirements before the planning phase begins?▼

Documenting project requirements before planning is achieved through a state-aware interview that integrates existing documentation and design constraints. This process captures all critical dimensions and outputs a formal brief.md file.

Can I use an interactive interview to integrate existing project documentation?▼

Yes, an interactive interview can integrate existing project documentation and design constraints. The state-managed interview process ensures all critical project dimensions are addressed before creating the brief.md file.

Why does my development workflow require a formal brief before track planning?▼

A development workflow requires a formal brief before track planning to ensure shared understanding and enforce workflow discipline. This prevents poorly defined development tracks by capturing comprehensive project context authoritatively.