Menu
Capture and structure raw ideas through guided interview or quick note. Produces a structured idea document ready for research or PRD pass. Focuses purely on product intent โ no technical decisions.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Produce the high-level architecture overview used by downstream product design and engineering.
Independent high-level architecture review gate for discovery.
Entry-point product workflow from raw idea to validated product design artifacts. Stops at reviewed PRD readiness and does not include engineering implementation.
Write the per-feature PRD from the ranked requirements contract using the mandatory PRD template.
Dedicated analyze gate for PRD and UI brief consistency. Runs script extraction first, then semantic review with evidence-backed findings.
Validate whether the captured problem is real, painful, frequent, and worth pursuing before broader discovery work begins.
| name | woos-idea-capture |
| description | Capture and structure raw ideas through guided interview or quick note. Produces a structured idea document ready for research or PRD pass. Focuses purely on product intent โ no technical decisions. |
| version | 3.0.0 |
| author | Hermes Profile |
| license | MIT |
| metadata | {"hermes":{"tags":["idea","capture","interview","product","ideation"],"related_skills":["woos-product-discovery","woos-product-design-flow"]}} |
PASS, REQUEST_CHANGES, BLOCKED, NOT_RUNcritical, high, medium, low, warning[ASSUMPTION: ...], [NEEDS CLARIFICATION: ...], [NEEDS INPUT: ...]P0 โฆ P11, P2a, Phase A, Phase Binternal-tool, single-operator, consumer-product, multi-stakeholder, CLIstrong, adequate, thin, broken## Background, ## Functional Requirements, ## Assumptions Index) โ translations break downstream structural checks**Consequences (testable):**, **Out of Scope:**, **User value:**, Given โฆ When โฆ Then โฆ)Transform a raw idea or feature request into a structured document that can feed into research, PRD, or product planning.
This skill focuses exclusively on product intent: what problem to solve, for whom, and what success looks like. It does NOT make technical decisions โ those belong in later stages.
Use when:
Skip when:
woos-product-design-flowNote: Capture itself always runs the same way, but mode selection happens in two places:
- Lite may branch immediately after Capture if the idea is obviously trivial and the user confirms.
- Standard / Strict are inferred later, after Product Discovery, from the approved roadmap.
Two capture depths based on idea complexity:
For: single-line fixes, obvious improvements, user already has full clarity.
Process:
ideas/<slug>.mdQuick Note template:
# <Idea Title>
## Summary
One paragraph: what and why.
## Problem
Who has this problem? What pain does it cause?
## Proposed Solution
What should we build?
## Constraints (if any)
- Time, budget, technical, or compatibility constraints
## Success Signal
How do we know it worked?
For: features, product initiatives, anything requiring design thinking.
Process:
GREENLIGHT NEXT STAGE to skip remaining questionsideas/<slug>/00-idea-capture.mdAsk sequentially. Skip if user already provided the information unprompted.
Users often volunteer technical opinions during capture ("I want to use Go", "let's use SQLite", "no React"). This is natural โ but it must NOT become a hard constraint in this phase.
Rules:
## Technical Preferences (Deferred) sectionOutput format for deferred preferences:
## Technical Preferences (Deferred)
> โ ๏ธ These are user preferences expressed during idea capture. They are NOT confirmed
> technical decisions. They will be evaluated during the Discovery architecture
> steps (Step 4 / Step 4R), where trade-offs can be properly assessed.
- "Backend in Go" โ user preference, to be evaluated in architecture
- "SQLite for storage" โ user preference, to be evaluated in architecture
# <Idea Title>
## Capture Date
YYYY-MM-DD
## Source
How did this idea come up?
## Problem Statement
Who: [target users]
Pain: [what hurts]
Current workaround: [how they cope today]
## Vision
Ideal experience: [describe]
## Core Behaviors
1. [behavior 1]
2. [behavior 2]
## Success Criteria
- [observable outcome 1]
- [observable outcome 2]
## Out of Scope
- [explicitly excluded]
## Constraints
- Time: [deadline or "none"]
- Resources: [team size or "flexible"]
- Dependencies: [integration points or "none"]
- Security: [concerns or "standard"]
## Technical Preferences (Deferred)
> โ ๏ธ User preferences only. NOT decisions. Evaluated in Discovery Step 4 / Step 4R (Architecture).
- [preference]: user preference, to be evaluated in architecture
- (or "None expressed")
## Risks
- [risk]: [mitigation or "accepted"]
## Open Questions
- [unresolved question]
## Interview Status
- Questions answered: N/13
- GREENLIGHT used: yes/no
ideas/<slug>.mdideas/<slug>/00-idea-capture.mdSlug: lowercase, hyphens, max 50 chars, from idea title.
After capture is complete, assess complexity:
Is it obviously trivial? (typo, 1-liner, single obvious change, user explicitly says it's simple)
โ Yes โ Propose Lite to user: "This looks straightforward. I suggest Lite mode โ go directly to a lightweight PRD package. Agree?"
โ User confirms โ `woos-product-design-flow` Lite
โ User says no โ proceed to Discovery
โ No โ proceed to `woos-product-discovery` (research needed)
Rules:
woos-product-design-flow