This skill should be used when the user asks to "frame a problem", "define a project idea", "create a problem brief", "scope a new project", "analyze a project concept", or needs to convert a raw idea into a structured problem statement with target users, success metrics, constraints, and non-goals.
From pm-architect-greenfieldnpx claudepluginhub nbkm8y5/claude-plugins --plugin pm-architect-greenfieldThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.
Transform a raw project idea into a structured PROBLEM_BRIEF.md artifact. This is the first step in the greenfield specification pipeline — it takes unstructured input and produces a well-defined problem statement that feeds into requirements decomposition.
[Raw Idea] → **PROBLEM FRAMING** → [PROBLEM_BRIEF.md] → Requirements Decomposition → ...
Input: Raw idea text (from user prompt or --idea flag)
Output: PROBLEM_BRIEF.md written to the project's artifacts directory
Read the raw idea and identify:
If the idea is too vague, identify what's missing and document in Open Questions.
Create a user type table with at least 2 user types:
Create measurable success metrics with IDs (SM-0001, SM-0002, ...):
Identify technical, business, regulatory, and resource constraints:
Explicitly state what is OUT of scope:
Synthesize all above into a clear, falsifiable problem statement:
Write the artifact following the template at ${CLAUDE_PLUGIN_ROOT}/reference/templates/PROBLEM_BRIEF.template.md.
The artifact must follow the standard artifact template structure:
# PROBLEM_BRIEF: [Project Name]
## Summary
[2-3 sentence summary of the problem being solved and why it matters]
## Inputs
- **Raw Idea**: [The original idea text provided by the user]
- **Additional Context**: [Any supplementary information provided]
## Outputs
- This document (PROBLEM_BRIEF.md)
- Feeds into: REQUIREMENTS.md (via requirements-decomposition skill)
## Assumptions
- [ASM-0001]: [Assumption text — sorted alphabetically, sequential IDs]
- [ASM-0002]: [Assumption text]
- ...
## Open Questions
- [OQ-0001]: [Question text — things that need clarification before proceeding]
- [OQ-0002]: [Question text]
- ...
## Main Content
### Problem Statement
[2-4 sentences. States the problem, who it affects, and the desired outcome.
Must be falsifiable. Must NOT prescribe a solution.]
### Target Users
| User Type | Description | Primary Need | Frequency of Use |
|-----------|-------------|--------------|------------------|
| [Type 1] | [Who they are] | [What they need] | [How often] |
| [Type 2] | [Who they are] | [What they need] | [How often] |
| [Type 3] | [Who they are] | [What they need] | [How often] |
### Success Metrics
| ID | Metric Name | Target Value | Measurement Method | Category |
|----|-------------|--------------|-------------------|----------|
| SM-0001 | [Name] | [Measurable target] | [How to measure] | [adoption/engagement/performance/business] |
| SM-0002 | [Name] | [Measurable target] | [How to measure] | [Category] |
| SM-0003 | [Name] | [Measurable target] | [How to measure] | [Category] |
### Constraints
| ID | Constraint | Category | Impact |
|----|-----------|----------|--------|
| CON-0001 | [Constraint text] | [Technical/Business/Regulatory/Resource/Timeline] | [How it affects the project] |
| CON-0002 | [Constraint text] | [Category] | [Impact] |
### Non-Goals
| ID | Non-Goal | Rationale |
|----|----------|-----------|
| NG-0001 | [What is explicitly out of scope] | [Why it is excluded] |
| NG-0002 | [Out of scope item] | [Rationale] |
## Acceptance Criteria
- [ ] Problem statement is clear, falsifiable, and does not prescribe a solution
- [ ] At least 2 target user types identified with descriptions
- [ ] At least 3 success metrics with measurable targets and measurement methods
- [ ] Constraints documented with categories and impact assessment
- [ ] Non-goals explicitly stated with rationale
- [ ] All IDs are sequential and items are sorted alphabetically by title/text
- [ ] Assumptions documented for any gaps in information
- [ ] Open questions listed for items requiring clarification
Output path: artifacts/greenfield/<project_name>/PROBLEM_BRIEF.md
When the raw idea is vague or incomplete:
| Input Quality | Action |
|---|---|
| Clear and detailed | Proceed normally, minimal assumptions |
| Moderate detail | Proceed with documented assumptions, 2-3 open questions |
| Vague (1-2 sentences) | Proceed with heavy assumptions, 5+ open questions, flag for review |
| Extremely vague | Generate minimal brief, list all gaps as open questions, recommend user interview |
The PROBLEM_BRIEF.md is referenced by downstream artifacts:
Ensure all IDs are stable — once assigned, they should not change across regenerations unless the underlying content changes.
Before completing, verify:
"Small-to-medium real estate agencies (5-20 agents) lose an average of 3-5 hours per agent per week on manual lead qualification, resulting in delayed follow-ups and an estimated 15-20% loss in potential conversions. There is no standardized process for scoring and routing incoming leads across the team."
"We need an AI-powered CRM with automatic lead scoring, email integration, and a mobile app for real estate agents." (This prescribes a solution, not a problem.)