STEP 01 OF 04
Choose one real problem
Identify a specific bit of repeated friction faced by 10 people you can talk to directly. Write the problem statement without proposing features.
EXPECTED STEP ARTIFACT
Problem statement: "Independent designers spend 45 minutes manually synchronizing hex codes between Figma and code on every release."
specs/problem-brief.md
+9-4
Narrow problem statement to one real audience and eliminate feature scope creep.
--- a/specs/problem-brief.md |
+++ b/specs/problem-brief.md |
@@ -1,4 +1,8 @@ |
-# Product Spec: Draft V0 |
-- What we are building: A platform for all designers and developers to connect. |
-- Features: Login, Marketplace, Chat, AI Copilot, Payment Gateway, Forums. |
-- Target: Everyone on the internet. |
+# Product Spec: Problem Brief V1 |
+## Target Audience |
+10 independent product designers and front-end developers maintaining Next.js 16 projects. |
+ |
+## Specific Friction |
+Manual token synchronization takes 45 minutes on every release, leading to inconsistent hex values and broken dark mode contrast. |
+ |
+## The Single Core Promise |
+Paste a Figma token JSON or URL, receive a typed Tailwind CSS v4 @theme inline block in 3 seconds. Zero configuration. |
CHECKPOINT VERIFICATION
Action RequiredDefine the target user and the specific friction they experience.
COMMAND / IMPLEMENTATION
npx @abeta.dev/cli@latest init-spec --template=problem-briefSTEP REFLECTION
Who are the 3 real people you will show this solution to first?
Discussion on Step 01 (1)
Ask questions or share tips with fellow builders
Pro tip for step 1: Narrow the audience to 10 specific people you can message directly. Avoid broad "everyone who codes" targets.