woos-product-research

Estrellas7

Forks1

Actualizado16 de junio de 2026 a las 10:16

Research the market, competitors, feasibility, and existing solutions to produce a product discovery research document.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

zero-click

zero-click/zero-ratchet

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Especialistas en gestión de proyectosOperaciones empresariales y financieras·SOC 13-1082

Explorador de archivos

3 archivos

SKILL.md

readonly

name	woos-product-research
description	Research the market, competitors, feasibility, and existing solutions to produce a product discovery research document.
version	1.0.0
author	Hermes Profile
license	MIT
metadata	{"hermes":{"tags":["product","discovery","research","competitive-analysis"],"related_skills":["woos-product-discovery"]}}

Product Research

Output Language

Author all user-facing prose (narratives, findings, summaries) in the user's most recent input language (e.g. if the user is writing in Chinese, write the PRD body, review findings, and summaries in Chinese).
Keep these tokens verbatim in English regardless of the user's language, because they are contract identifiers consumed by other skills and gates:
- Verdict tokens: PASS, REQUEST_CHANGES, BLOCKED, NOT_RUN
- Severity tokens: critical, high, medium, low, warning
- Tag tokens: [ASSUMPTION: ...], [NEEDS CLARIFICATION: ...], [NEEDS INPUT: ...]
- Phase / dimension IDs: P0 … P11, P2a, Phase A, Phase B
- Shape values: internal-tool, single-operator, consumer-product, multi-stakeholder, CLI
- P0 rating values: strong, adequate, thin, broken
- Section headings declared in templates (e.g. ## Background, ## Functional Requirements, ## Assumptions Index) — translations break downstream structural checks
- Field labels inside templates (e.g. **Consequences (testable):**, **Out of Scope:**, **User value:**, Given … When … Then …)
Code, file paths, IDs, and quoted PRD excerpts stay in their original form.

Purpose

Produce the research document that discovery uses to justify roadmap and architecture choices.

Required Load Set (mandatory)

references/framework-market-research.md
references/framework-competitive-analysis.md
ideas/<slug>/00-idea-capture.md

If any required file is not loaded, return BLOCKED.

Output

docs/research/<topic>.md

Required Coverage

Market landscape
Competitive analysis
Technical feasibility
Existing solutions or reusable components
Risks and unknowns

Research must cite sources and include a recommendation.

Más de este repositorio

mismo repositorio

woos-architecture-overview

zero-click/zero-ratchet

Produce the high-level architecture overview used by downstream product design and engineering.

2026-06-167

woos-architecture-review-gate

zero-click/zero-ratchet

Independent high-level architecture review gate for discovery.

2026-06-167

woos-idea-capture

zero-click/zero-ratchet

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.

2026-06-167

woos-idea-to-design

zero-click/zero-ratchet

Entry-point product workflow from raw idea to validated product design artifacts. Stops at reviewed PRD readiness and does not include engineering implementation.

2026-06-167

woos-prd-authoring

zero-click/zero-ratchet

Write the per-feature PRD from the ranked requirements contract using the mandatory PRD template.

2026-06-167

woos-prd-consistency-audit

zero-click/zero-ratchet

Dedicated analyze gate for PRD and UI brief consistency. Runs script extraction first, then semantic review with evidence-backed findings.

2026-06-167

Product Research

Output Language

Author all user-facing prose (narratives, findings, summaries) in the user's most recent input language (e.g. if the user is writing in Chinese, write the PRD body, review findings, and summaries in Chinese).

Keep these tokens verbatim in English regardless of the user's language, because they are contract identifiers consumed by other skills and gates:

Verdict tokens: PASS, REQUEST_CHANGES, BLOCKED, NOT_RUN
Severity tokens: critical, high, medium, low, warning
Tag tokens: [ASSUMPTION: ...], [NEEDS CLARIFICATION: ...], [NEEDS INPUT: ...]
Phase / dimension IDs: P0 … P11, P2a, Phase A, Phase B
Shape values: internal-tool, single-operator, consumer-product, multi-stakeholder, CLI
P0 rating values: strong, adequate, thin, broken
Section headings declared in templates (e.g. ## Background, ## Functional Requirements, ## Assumptions Index) — translations break downstream structural checks
Field labels inside templates (e.g. **Consequences (testable):**, **Out of Scope:**, **User value:**, Given … When … Then …)

Code, file paths, IDs, and quoted PRD excerpts stay in their original form.

Purpose

Produce the research document that discovery uses to justify roadmap and architecture choices.

Required Load Set (mandatory)

references/framework-market-research.md

references/framework-competitive-analysis.md

ideas/<slug>/00-idea-capture.md

If any required file is not loaded, return BLOCKED.

Output

docs/research/<topic>.md

Required Coverage

Market landscape

Competitive analysis

Technical feasibility

Existing solutions or reusable components

Risks and unknowns

Research must cite sources and include a recommendation.