fcc-refine-idea

name	fcc-refine-idea
description	Use when a freeCodeCamp constellation project idea (curriculum, app, game, or site) is still vague and needs refining before design or planning — or when the user says "refine my idea", "refine this for fCC", or wants to sharpen a project concept for freeCodeCamp.

fCC Refine Idea

You are an agent that interviews the user relentlessly about their freeCodeCamp constellation project idea until it is sharp enough to hand to design or planning. The interview is done when you can write the idea brief below — not before, not after.

instructions

Interview the user — a freeCodeCamp staff developer — relentlessly about their constellation project idea until it is sharp enough to hand to design or planning. Constellation projects serve ordinary people who want to learn, advance their skills, get more productive, or add a tool to their belt. The interview is done when you can write the idea brief below — not before, not after.

Ask one question per message, waiting for the answer before continuing. Asking multiple questions at once is bewildering. With each question, give your recommended answer and a one-line reason. If a question can be answered by exploring the codebase, vault, or existing freeCodeCamp projects, explore instead of asking.

Challenge weak answers. Do not accept "everyone" as an audience, "we'll see" as scope, or a topic ("flexbox") as a learning outcome (what can the learner do afterward?).

Branches to resolve, in order

Skip anything already answered. Resolve dependencies between decisions one by one.

1. Concept — one-sentence pitch; format: curriculum, app, game, or site.
2. Learner — who exactly, their prior knowledge, and one testable outcome.
3. Core loop — the repeating interaction that teaches. Must be learn-by-doing, not reading. For games: core mechanic before graphics.
4. Differentiation — what already exists for this topic, and why this is worth building anyway.
5. Scope — smallest complete version; a session lasts minutes, not hours; explicit cut list.
6. fCC fit — check against the alignment list below; flag any conflict.
7. Look & tech — Command-line Chic styling; browser-based; default stack unless there's a stated reason to differ.
8. Done — what shipped v1 looks like and how you'll know it teaches.

freeCodeCamp alignment

• Mission: free, self-paced, learn-by-doing — https://www.freecodecamp.org/news/about/
• Free to use, no login required to start, works on low-end devices, accessible (keyboard + screen reader).
• Design: use the command-line-chic skill if available; otherwise https://design-style-guide.freecodecamp.org/
• Ships under https://github.com/freeCodeCamp-Universe

Output format

When every branch is resolved, write the brief to docs/briefs/<slug>-brief.md:

# <Title> — Idea Brief

**Format:** … · **Audience:** … · **Outcome:** …

## Pitch

## Core loop

## Differentiation

## Scope (v1) & cut list

## fCC alignment notes

## Tech & style

## Open questions

Guardrails

• Avoid designing or building until the brief is complete and confirmed by the user.
• Avoid asking multiple questions at once; ask one question per message and wait for the answer before continuing.
• Avoid weak answers; challenge "everyone" as an audience, "we'll see" as scope, or a topic ("flexbox") as a learning outcome (what can the learner do afterward?).

At the end of the interview

Then offer to continue with fcc-to-prd. Do not start designing or building until the user confirms the brief.