---
name: project-brainstorm
description: Use when starting or refining a project idea, feature concept, research direction, or product decision that should become traceable PRD, architecture, or implementation work. Produces brainstorm IDs and source material that later artifacts can cite.
---

# Project Brainstorm

Use this skill to turn early project discussion into stable brainstorm records.

## Rules

- Keep the process project-agnostic.
- Assign stable IDs to important requirements, decisions, risks, and questions.
- Do not jump to implementation planning until the user agrees the idea is clear.
- Store or recommend storage under `docs/brainstorm/`.
- Use `.prd_plugin/ID-SCHEME.md` when present; otherwise use the default PRD Plugin ID scheme.
- When the brainstorm creates durable agent-facing knowledge, propose `MEM-*`,
  `OBS-*`, or `TRK-*` records rather than silently updating project state.
- Keep raw session observations local unless they are promoted through the
  project memory promotion rules.
- Use `HLT-*` only for actionable project health issues, not ordinary open
  brainstorm questions.
- Use `REQ-*` when an outside agent proposes a change that needs owner review
  before becoming project truth.

## Staleness Coverage

Apply the shared policy in `.prd_plugin/method/staleness-rules.md`.


Before turning brainstorm output into PRD, tracking, memory, or request intake,
check whether existing `BR-Q-*`, `BR-RISK-*`, `TRK-*`, `REQ-*`, or `HLT-*`
records for the same idea are stale. Refresh the stale context with current
evidence or preserve the stale item as an explicit risk/follow-up.

## IDs

- `BR-REQ-###` for needs, goals, or requirements discovered in brainstorming.
- `BR-DEC-###` for decisions.
- `BR-Q-###` for open questions.
- `BR-RISK-###` for risks.
- `OBS-###` for source-backed observations discovered during the session.
- `MEM-###` for candidate promoted memory that future agents should rely on.
- `TRK-###` for candidate tracking records such as active open questions or
  follow-up work.
- `HLT-###` for candidate health findings when a discovered issue blocks or
  weakens project traceability.
- `REQ-###` for proposed changes that should enter request intake.

## Output Shape

Summarize:

1. Context
2. Goals
3. Non-goals
4. Decisions
5. Open questions
6. Risks
7. Candidate PRD requirements
8. Candidate memory/tracking updates, if any
9. Candidate health findings, if any
10. Candidate request intake records, if any

End with the next recommended artifact: `project-planning-lifecycle` for a full
brainstorm -> PRD -> architecture -> implementation plan chain, PRD,
architecture spike, research note, agent memory proposal, or implementation plan
only if PRD/architecture already exist.