DangQuangSE/team-development-skills / .cursor/skills/ck-brainstorm
ck-brainstorm
UnverifiedExplore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.5 KB |
| agents/openai.yaml | config | 230 B |
| references/spec-template.md | markdown | 1.4 KB |
references/spec-template.md
View on GitHub# Spec: {feature name}
**Date:** YYYY-MM-DD
**Status:** Draft | Ready | Approved
---
## Problem Statement
{1–2 sentences: what pain does this solve, for whom, why now}
---
## User Stories
<!-- P1 = MVP (must ship), P2 = nice-to-have, P3 = future/out-of-scope -->
- **[P1]** As a {role}, I want to {action} so that {value}.
Accepted when: {specific, testable condition}
- **[P1]** As a {role}, I want to {action} so that {value}.
Accepted when: {specific, testable condition}
- **[P2]** As a {role}, I want to {action} so that {value}.
Accepted when: {specific, testable condition}
- **[P3]** _(out of scope — noted for future)_
---
## Functional Requirements
<!-- Number each. Be specific. "User can upload file ≤ 5MB (jpg/png/pdf)" not "user can upload files" -->
1. FR-01:
2. FR-02:
3. FR-03:
---
## Non-Functional Requirements
<!-- Use numbers, not adjectives. "p95 latency < 500ms" not "fast" -->
- Performance:
- Security:
- Availability:
---
## Success Criteria
<!-- Measurable outcomes. Each must be independently verifiable. -->
- [ ] {metric}: {target value} (e.g. "Export completes in < 2 minutes for 10k rows")
- [ ] {metric}: {target value}
---
## Out of Scope
- {explicit exclusion 1}
- {explicit exclusion 2}
---
## Assumptions
- {assumption 1 — if wrong, this spec changes}
- {assumption 2}
---
## [NEEDS CLARIFICATION]
<!-- Remove section when empty. Items here block /ck:plan. -->
- [ ] {ambiguity 1}
- [ ] {ambiguity 2}
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 |