id = "product-spec"
name = "Product Spec Writer"
description = "Turn a product idea or feature request into a complete PRD: user stories, acceptance criteria, technical notes, and open questions."
category = "business"
tags = ["product", "prd", "planning", "engineering"]

[i18n.zh]
name = "产品需求文档撰写"
description = "将产品想法或功能需求转化为完整 PRD：用户故事、验收标准、技术备注和待确认事项。"

[[parameters]]
name = "feature_idea"
description = "Feature idea or problem statement to spec out"
param_type = "string"
required = true

[[parameters]]
name = "context"
description = "Product context, target users, and any constraints"
param_type = "string"
required = false
default = ""

[[steps]]
name = "problem_definition"
prompt_template = """
You are a senior product manager. Define the problem clearly:
1. **Problem statement** — one precise sentence
2. **Who has this problem** — user segments and their specific pain
3. **Current workarounds** — how users cope today
4. **Why now** — why is this worth solving now
5. **Success looks like** — quantifiable outcomes
6. **Out of scope** — what this will deliberately not solve

Idea: {{feature_idea}}
Context: {{context}}
"""

[[steps]]
name = "user_stories"
prompt_template = """
Write user stories in the format: As a [user type], I want to [action] so that [outcome].

For each story:
- Given / When / Then acceptance criteria (3-5 criteria)
- Priority: P0 (must-have) / P1 (should-have) / P2 (nice-to-have)
- Estimated complexity: S / M / L / XL

Write at least 6 user stories covering happy paths, edge cases, and error states.

Problem definition:
{{problem_definition}}
"""
depends_on = ["problem_definition"]

[[steps]]
name = "prd"
prompt_template = """
Write a complete Product Requirements Document:

## Overview
## Problem Statement
## Goals & Non-Goals
## User Stories
(from above)
## Functional Requirements
Numbered list of specific behaviours the system must exhibit.
## Non-Functional Requirements
Performance, security, accessibility, internationalisation.
## Technical Considerations
Known constraints, integration points, migration needs.
## Metrics
How success will be measured (leading and lagging indicators).
## Open Questions
Decisions still needed, with suggested owners.
## Timeline Sketch
Phases with rough scope.

Problem definition:
{{problem_definition}}

User stories:
{{user_stories}}
"""
depends_on = ["problem_definition", "user_stories"]

[i18n.zh-TW]
name = "產品規格撰寫"
description = "將產品想法或功能需求轉化為完整 PRD：使用者故事、驗收標準、技術備註與待確認事項。"

[i18n.ja]
name = "プロダクトスペックライター"
description = "製品アイデアや機能要望を完全な PRD に変換：ユーザーストーリー、受け入れ基準、技術メモ、未解決事項。"

[i18n.ko]
name = "제품 스펙 작성"
description = "제품 아이디어나 기능 요청을 완전한 PRD로 변환: 사용자 스토리, 수락 기준, 기술 노트, 미해결 질문."

[i18n.de]
name = "Product-Spec-Autor"
description = "Produktidee oder Feature-Anfrage in ein vollständiges PRD verwandeln: User Stories, Akzeptanzkriterien, technische Notizen und offene Fragen."

[i18n.es]
name = "Redactor de especificaciones de producto"
description = "Convierte una idea o solicitud en un PRD completo: historias de usuario, criterios de aceptación, notas técnicas y preguntas abiertas."

[i18n.fr]
name = "Rédacteur de spec produit"
description = "Transformer une idée ou une demande en PRD complet : user stories, critères d’acceptation, notes techniques et questions ouvertes."