Why use the Brief skill instead of jumping straight to building?

It prevents 'hallucinated' requirements and scope creep by ensuring Claude understands the business context and goals that code scanning alone cannot reveal.

Where is the finalized project brief stored?

Once confirmed, the brief is saved as a Markdown file in a .briefs/ directory within your repository for future reference and agent handoff.

How long does the adaptive interview take?

The interview is designed to be a conversation lasting under 5 minutes, typically involving only 2 to 6 targeted questions.

Does this skill ask about my technical stack or architecture?

No. The skill assumes autonomous agents will infer the tech stack from your codebase; it focuses strictly on business intent, audience, and success criteria.

Can I skip the interview if I already have a specification?

Yes. The skill is designed to detect detailed specs or direct build commands, in which case it will step aside and allow you to proceed directly to implementation.

Adaptive Project Briefing

Name: Adaptive Project Briefing
Author: izzzzzi

byizzzzzi

0•

생산성 및 워크플로

Conducts a targeted, adaptive interview to capture business intent and requirements before triggering autonomous code implementation.

The Brief skill acts as a strategic discovery layer for Claude Code, ensuring that autonomous agents understand the business goals and user needs before writing code. By conducting a short, 2-6 question interview, it bridges the gap between vague ideas and technical execution, preventing wasted development cycles. It leverages codebase research to suggest smart options, creates a formal project brief, and requires explicit user approval before handing tasks off to the build team, ensuring every feature aligns perfectly with stakeholder expectations.

주요 기능

01Mandatory approval gate with structured brief generation

020 GitHub stars

03Adaptive 2-6 question interviews based on initial input depth

04Smart button-based interaction for rapid requirement confirmation

05Automated codebase research to provide context-aware suggestions

06Business-centric discovery focusing on 'why' and 'who' over technical specs

사용 사례

01Gathering requirements for complex features where user intent is ambiguous

02Clarifying vague feature requests before starting development

03Aligning technical implementations with specific business success criteria

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add izzzzzi/izteam brief

For use in Claude.ai and ChatGPT