brainstorming
Structured design dialogue that validates ideas before implementation begins.
brainstorm-proof-of-concept-plan
Use when requirements specify risky technical assumptions, unfamiliar APIs, or complex integrations before implementing full features - creates sequential POC plans with parallel research validation, design documentation, and risk mitigation for incremental confidence building
Full skill instructions
Transform risky requirements into validated POC plans through parallel research, risk prioritization, and sequential validation. Use after design is complete but technical assumptions remain unproven.
Core principle: Validate riskiest assumptions first with minimal code, data-driven decisions, and clear go/no-go criteria.
Use this skill when:
Don't use for:
brainstorming (design) → brainstorm-proof-of-concept-plan (validation) → writing-plans (implementation)
Use TodoWrite to track each step:
Review requirements and extract technical risks:
Prioritize by:
Requirements often miss hidden assumptions. Use AskUserQuestion:
AskUserQuestion({
questions: [{
question: "Which risks should POC prioritize? I recommend [X] because [Y].",
header: "POC Priority",
multiSelect: false,
options: [
{ label: "Risk A First", description: "Foundation for others..." },
{ label: "Risk B First", description: "Highest uncertainty..." },
{ label: "All Sequentially", description: "Validate each in order..." },
{ label: "Research First", description: "Need investigation before deciding..." }
]
}]
})
Why: User may have domain knowledge that changes priority ("We already validated X, focus on Y").
Critical: Each research agent writes its own report file. Main agent does NOT write research reports.
For 3+ research areas, dispatch Task agents simultaneously:
// Each agent writes directly to design-docs/research/
Task({
subagent_type: "general-purpose",
prompt: `Research VitePress WebSocket integration patterns.
**Output:** Write findings to design-docs/research/vitepress-websocket-integration.md
**Format:**
# VitePress WebSocket Integration Research
**Research Date:** YYYY-MM-DD
**Sources:** [URLs]
## Key Findings
- Finding (Source: URL)
## Implications for POC
- What this means
## Recommendation
[Data-driven choice]
**Use elements-of-style:writing-clearly-and-concisely skill for writing.**`
})
Launch 3-4 agents in parallel:
Why parallel: 4x speed, each produces focused brief with citations.
Never: Write research reports yourself. Always delegate to Task agents.
After research agents complete:
You synthesize, but agents wrote the reports.
Critical: Document the COMPLETE POC strategy, not just the first POC.
Break validation into phases that build on each other:
Example:
For the FIRST POC only: Create detailed design with:
For REMAINING POCs: Document high-level:
Why: Complete strategy shows big picture. Detailed design for POC-1 enables immediate implementation.
Location: Same folder as whiteboard/requirements documents
Naming pattern: Append -poc{{N}}-{{short-slug}} to the base filename
diff-view-monaco-requirements.mddiff-view-monaco-poc1-validate-diff-view-builds.mddiff-view-monaco-poc2-props-and-theme.mdRequired sections:
Citation Requirements: Every design decision MUST be backed by:
[FR-2.1](./requirements-file.md#^FR2-1)[Research](./research/topic-research.md)[Source](https://url) with full URLFormat: Use markdown links with anchors for requirement references. Use relative paths ./ for same-folder files.
Example "Complete POC Strategy" section:
## Complete POC Strategy
### POC-1: Layout Override and Width Validation (This Document)
**Goal:** Prove we can disable right sidebar and achieve 600px+ per diff pane
**Timeline:** 2-3 days
**Status:** Detailed design below
### POC-2: File-Based Diff Loading
**Goal:** Validate SystemPromptDiff can load content from file paths
**Dependencies:** Requires POC-1 layout working
**Timeline:** 1-2 days
**Status:** Future
### POC-3: TOC Integration in Left Sidebar
**Goal:** Merge page TOC into left navigation sidebar
**Dependencies:** Requires POC-1 and POC-2 complete
**Timeline:** 3-4 days
**Status:** Future
Required: Use elements-of-style:writing-clearly-and-concisely skill for design doc.
Before this skill:
After this skill:
During this skill:
| Rationalization | Reality |
|---|---|
| "I'll write research reports myself" | Agents write their own reports. You synthesize. Delegate. |
| "Just document POC-1, others are future work" | Document complete strategy. Detailed design for POC-1 only. |
| "Parallel research is overkill" | Parallel = 4x speed with focused briefs. Always use for 3+ areas. |
| "User already specified risks" | User lists known risks. AskUserQuestion surfaces hidden ones. |
| "Documentation structure doesn't matter" | Same-folder location enables discovery. Always follow naming pattern. |
| "Writing skill slows me down" | Concise docs save implementation time. Required for all reports. |
| "POC planning is too formal" | POC without plan = random prototyping. Structure prevents waste. |
| "Citations are obvious from context" | Future readers need explicit links. Always cite requirements/research/sources. |
| "I'll add citations later" | Design decisions without citations = unverifiable claims. Add during writing. |
| "General approach doesn't need citations" | Every design choice needs backing. Cite requirements or research for all decisions. |
POC plan succeeds when you can answer:
All answers backed by research with citations (written by research agents).
| Step | Action | Tool | Who Writes |
|---|---|---|---|
| Identify risks | Extract from requirements | Analysis | You |
| Prioritize | Matrix (uncertainty × impact × cost) | Judgment | You |
| Elicit hidden risks | Ask which matters most | AskUserQuestion | You |
| Research | 3+ areas simultaneously | Task (parallel) | Agents write reports |
| Synthesize | Read reports, find themes | Read tool | You |
| Design POCs | ALL POCs + detailed POC-1 | docs/plans/ | You |
| Validate | Build minimal code, measure | Next step | Future |
Speed: Parallel research saves hours compared to serial investigation.
Quality: Research citations (from agent reports) enable verification.
Clarity: Complete POC strategy prevents "what comes next?" confusion.
Delegation: Research agents write reports while you orchestrate and synthesize.
Structured design dialogue that validates ideas before implementation begins.
Comprehensive design intelligence for web and mobile UI/UX across 10 technology stacks.
Comprehensive implementation plans for multi-step tasks, breaking down specs into bite-sized, testable steps.
Introduction to the obra skills system with mandatory skill invocation rules and best practices.
Execute a written implementation plan with critical review and task checkpoints.
Delegate independent tasks to specialized agents working concurrently with isolated context.
Isolated git worktrees with smart directory selection and safety verification.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Plan searchable and shareable content that drives traffic, builds authority, and generates leads.
README-first repository scanner that extracts commands and classifies reproduction candidates without executing them.
Brainstorm and prioritize marketing strategies tailored to your SaaS stage, budget, and goals.
Plan and optimize your website's page hierarchy, navigation, URL structure, and internal linking.
The world's fastest calendar for remote work
Capture, organize, and utilize your knowledge effortlessly.
Instant Summaries of Audio & Video Interviews with AnySummary
Transform PDFs into engaging mind maps.
Chat with any PDF instantly
Create an optimal daily plan using your voice
A productivity platform to centralize organizational knowledge and workflows with contextual AI assistance.
AskYourPDF Pricing Plans: Tailored to Your Needs