briefing

To conduct a structured project discovery briefing, you answer a guided interview that captures project vision, stakeholders, scope, constraints, and technical context. This process organizes the initial project context into a usable markdown document for downstream artifacts.

Structured discovery for project initiation is a guided workflow that collects and organizes project context through an interview. It captures critical elements like vision, users, priorities, tech stack, and quality criteria to generate a comprehensive briefing document.

You capture project requirements and stakeholder scope by responding to a structured briefing interview. The workflow extracts vision, constraints, and technical context, organizing the details into a markdown-based synthesis template for downstream use.

Yes, the briefing workflow supports markdown and YAML metadata. It generates a document utilizing YAML-frontmatter driven metadata and markdown-based synthesis templates to satisfy structured governance requirements.

To generate a project briefing for downstream artifacts, you need to provide project context details during a guided discovery interview. The Skill requires no external dependencies and outputs a structured markdown briefing to serve as a base for specs and plans.

Yes, you can use this structured interview for technical context and constraints. It is specifically designed to extract tech stack details, quality criteria, priorities, and project restrictions during the initial discovery phase.