wds-1-project-brief

Guides collaborative discovery to produce a structured product brief document.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill wds-1-project-brief-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wds-1-project-brief
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/wds-1-project-brief
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill wds-1-project-brief-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Starting a design or product project without a shared strategic foundation leads to misaligned stakeholders, vague requirements, and rework. This Skill walks a project owner through a structured discovery workflow to capture vision, positioning, business model, target users, success criteria, competitive landscape, constraints, tone of voice, SEO strategy, visual direction, and platform requirements in one consistent Product Brief. ## Core Features & Use Cases - Guided multi-step discovery: A 36-step complete flow (or a 5-10 minute simplified flow) covering client profile, vision, positioning, business model, users, success criteria, competition, constraints, content strategy, visual direction, and platform requirements. - Validation mode: A separate validation workflow checks brief completeness, trigger-map consistency, SEO strategy, content, visual direction, and platform requirements, producing a validation report. - Ready-made templates: Includes templates for the project brief, client profile, content & language, visual inspiration analysis, platform requirements, pitch, contract, service agreement, and signoff documents. - Use Case: A consultant kicking off a website redesign activates the Skill, answers conversational prompts about the client and market, and receives a complete project-brief.md plus supporting documents saved to the output folder, ready for Phase 2 trigger mapping. ## Quick Start Ask the agent to start the Phase 1 Product Brief workflow and answer its discovery questions about your project vision, users, and constraints.

Frequently Asked Questions about wds-1-project-brief

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

FAQPage Schema
How do I create a product brief for a design project?

Activate the workflow and answer its guided discovery questions covering vision, positioning, business model, target users, success criteria, competition, and constraints. The Skill generates a project-brief.md in the output folder using its built-in template.

What is the difference between the simplified and complete brief?

The simplified brief captures only scope, challenge, design goals, and constraints in about 5-10 minutes. The complete brief runs a 36-step flow adding client profile, positioning, business model, SEO, content, visual direction, and platform requirements.

How do I validate an existing product brief?

Invoke the workflow with the validate option. It loads the validation workflow, which checks brief completeness, trigger-map consistency, SEO strategy, content, visual direction, and platform requirements, then writes a validation report.

What configuration does the product brief workflow need?

It reads a config.yaml from the project's _bmad/wds folder for project name, output folder, user name, and languages, plus a brief_level value from the workflow status file to choose simplified or complete mode.

What documents does the brief workflow produce?

It produces a project brief plus optional supporting artifacts from templates: client profile, content and language guide, visual direction, platform requirements, pitch, contract, service agreement, and signoff documents.