ce-brainstorm

To brainstorm feature ideas into a requirements document, provide a topic and let the tool guide collaborative exploration to surface constraints and alternatives, producing a durable PRD-like artifact with YAML frontmatter and phase-scoped structure.

Defining feature scope for ambiguous requests requires collaborative brainstorming to align on success criteria and trade-offs. This approach generates a scoped requirements brief that defers implementation details to later planning phases.

Yes, you can generate a PRD-like artifact without writing code. The brainstorming process focuses on decisions and scope alignment first, explicitly deferring implementation details to downstream planning artifacts.

Collaborative brainstorming handles file references by keeping them repo-relative. This ensures all surfaced decisions and constraints remain properly linked and accessible to downstream planning artifacts within your repository.

Use a structured brainstorm instead of jumping to planning for high-ambition requests or when showing uncertainty about scope. It helps explore requirements and align on success criteria before committing to a specific implementation plan.

No specific dependencies are required for product management brainstorming. You simply provide a topic to explore, and the workflow generates a structured requirements artifact to guide subsequent planning and alignment.