Artifact: brainstorm doc
Compound Engineering’s front-of-loop artifact — a requirements-only unified plan under docs/brainstorms/, produced by ce-brainstorm from a collaborative Q&A dialogue. It captures what something should become — goals, constraints, requirements — and deliberately omits HOW (implementation is ce-plan’s job). It is grounded in the strategy and prior docs/solutions/ learnings.
The requirements-only discipline is the point: keeping the brainstorm free of implementation lets ce-plan own the clean WHAT→HOW enrichment downstream. It is the Compound Engineering counterpart to GSD’s decision-capture artifact-phase-context and, at the requirements level, to artifact-prd/artifact-spec-md — but lighter and earlier, a dialogue output rather than a formal spec.
Produced by (backlinks)
- ce-brainstorm — the dialogue that writes it.
See Also
- artifact-plan-md — the implementation-ready plan ce-plan enriches this into.
- artifact-phase-context — GSD’s decision-capture analogue; artifact-prd — the heavier requirements spec.
- stage-align — the stage this artifact supports.