oprogramadorreal/optimus-claude / skills/brainstorm
brainstorm
VerifiedRuns 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 4.1 KB |
| SKILL.md | skill md | 9.3 KB |
| agents/openai.yaml | config | 198 B |
| references/plan-mode-handoff.md | markdown | 4.8 KB |
| references/scenario-style.md | markdown | 2.6 KB |
| templates/product/mvp-prd.md | markdown | 1.7 KB |
| templates/product/product-context.md | markdown | 1.7 KB |
| templates/product/tech-stack.md | markdown | 1.8 KB |
templates/product/product-context.md
View on GitHub# Product Context
> **Altitude & precedence.** This document is part of a docs-first cascade, in decreasing altitude:
> **product vision → MVP PRD → target tech-stack → active build spec**. Higher docs set long-term
> direction; the active build spec (in `docs/specs/`) governs what to build right
> now. When they conflict about current work, **the active build spec wins.**
> Siblings: [MVP PRD](./mvp-prd.md) · [target tech-stack](./tech-stack.md).
>
> **What this document is.** The long-term product vision — the destination, not the next build. For
> what to build now, follow the active build spec in `docs/specs/`; for the first
> product slice, see [mvp-prd.md](./mvp-prd.md).
## Big picture
> TODO — not yet decided. In one paragraph: what is the product, who is it for, and what does it let
> them do?
## Product vision
> TODO — not yet decided. The longer-term direction — what this becomes over time, and why it matters.
## Target users
> TODO — not yet decided. The primary users and what they care about. Note how technical they are.
## Core product principles
> TODO — not yet decided. The handful of principles every product decision should honor.
## What it is / what it is not
> TODO — not yet decided. Bullet what the product is, and — just as important — what it is not.
## North star
> TODO — not yet decided. One sentence: the single outcome everything built should support.
## Guidance for AI coding agents
> TODO — not yet decided. How an agent should treat this doc. Typically: this is vision, not current
> scope; build the smallest thing that validates the idea; when the vision and the active build spec
> conflict about what to build now, the spec wins.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |