project-brief-writer

Project-brief-writer transforms rough ideas into problem-focused briefs that define *what* to build and *why*, while deferring technical decisions. It guides you through structured ideation to capture goals and requirements without prematurely locking in implementation choices, preserving learning opportunities for downstream planning skills.

A project brief defines the problem, goals, and functional requirements—the *what* and *why*. A technical specification details *how* to solve it. This skill keeps briefs problem-focused to avoid the PRD Quality Paradox, where premature technical decisions stifle exploration and bias future choices.

Project briefs work for both learning and delivery workflows. The skill automatically creates PROJECT-MODE.md to align your entire workflow with learning or delivery goals, ensuring briefs adapt to your context and support the structured steps that follow.

Project-brief-writer exports structured artifacts—brief.json, PROJECT-MODE.md, and project-specific markdown files—that capture functional requirements and non-binding user preferences while quarantining premature technical details for later refinement by downstream skills.

Use project-brief-writer at the crucial first step of structured project workflow, during early-stage ideation and non-technical planning. It serves as the foundation that feeds seamlessly into subsequent planning and setup skills like tech-stack-advisor.

Over-specification detection identifies and isolates premature technical decisions—deployment choices, stack preferences, or architectural assumptions—so they don't constrain learning opportunities. This preserves flexibility for downstream skills to make informed technology choices based on problem definition.