Skip to content

oprogramadorreal/optimus-claude / skills/brainstorm

brainstorm

Verified

Runs a structured design conversation — clarifies intent, proposes 2-3 approaches with trade-offs, iterates the design — and writes a user-approved engineering spec to docs/specs/ that /optimus:tdd auto-detects. No implementation happens until the spec is approved. With the scaffold argument, creates docs/product/ steering skeletons instead (never overwrites, authors no content). Recommends /optimus:init first.

templates/product/mvp-prd.md

View on GitHub
# MVP — Product Requirements (PRD)

> **Altitude & precedence.** Part of a docs-first cascade — **product vision -> MVP PRD -> target tech-stack -> active build spec**. The full statement of what that means lives in [product vision](./product-context.md); the short version is that when these conflict about current work, the active build spec (in `docs/specs/`) wins.
> Siblings: [product vision](./product-context.md) · [target tech-stack](./tech-stack.md).
>
> **What this document is.** The first product slice (the MVP) — narrower than the
> [product vision](./product-context.md), broader than any single build. What to build *right now* is
> the smaller active build spec in `docs/specs/`.
>
> **How to use it.** Each section holds a guiding question. Resolve a section by replacing its `TODO`
> with the decision and a short note on *why*.

## 1. Problem statement

> TODO — not yet decided. What exact problem does the MVP solve, and for which user first?

## 2. MVP scope

> TODO — not yet decided. The smallest slice that delivers and validates the core value.

## 3. Non-goals / out of scope

> TODO — not yet decided. What the MVP deliberately excludes (and defers to the vision).

## 4. Primary use cases

> TODO — not yet decided. The core things a user can do; mark the single "hero" use case to nail first.

## 5. Functional requirements

> TODO — not yet decided. What the system must *do*.

## 6. Non-functional / product requirements

> TODO — not yet decided. How the product must feel and behave, beyond features.

## 7. Success metrics

> TODO — not yet decided. How you will know the MVP is working — make each signal measurable.

## 8. Risks and open questions

> TODO — not yet decided.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall