{"id":"04fcd9ba-b0e8-495e-a650-4433ce31bf26","entityType":"agent","slug":"clawhub-phy041-phy-prd-writer","name":"Phy Prd Writer","canonicalUrl":"https://www.xpersona.co/agent/clawhub-phy041-phy-prd-writer","canonicalPath":"/agent/clawhub-phy041-phy-prd-writer","generatedAt":"2026-10-11T20:57:18.443Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T16:20:13.571Z","emptyReason":null},"description":"Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete,... Skill: Phy Prd Writer Owner: phy041 Summary: Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete,... Tags: latest:1.0.2, product:1.0.0, requirements:1.0.0 Version history: v1.0.2 | 2026-03-22T14:03:37.298Z | auto - Documentation updated in SKILL.md with clearer formatting. - No changes to code or functionality; co","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s175g2rty8e4mw6h9zcwwgxmfn884t23:phy-prd-writer","sourceUrl":"https://clawhub.ai/phy041/phy-prd-writer","homepage":"https://clawhub.ai/phy041/skills/phy-prd-writer","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/phy041/phy-prd-writer","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/phy041/skills/phy-prd-writer","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete,..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:13.571Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:13.571Z","emptyReason":null},"stars":null,"forks":null,"downloads":1029,"packageName":null,"latestVersion":"1.0.2","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T16:20:13.509Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T16:20:13.571Z","lastCrawledAt":"2026-10-11T16:20:13.509Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T16:20:13.509Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.2","createdAt":"2026-03-22T14:03:37.298Z","changelog":"- Documentation updated in SKILL.md with clearer formatting. - No changes to code or functionality; content remains the same. - Version bump likely for maintenance or documentation clarity.","fileCount":3,"zipByteSize":6542},{"version":"1.0.1","createdAt":"2026-03-22T12:13:03.454Z","changelog":"- Added a homepage link (`homepage: https://canlah.ai`) to SKILL.md. - No other functional or content changes in this version.","fileCount":2,"zipByteSize":5304},{"version":"1.0.0","createdAt":"2026-03-07T10:47:13.594Z","changelog":"Initial release","fileCount":2,"zipByteSize":5282}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s175g2rty8e4mw6h9zcwwgxmfn884t23:phy-prd-writer","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T20:57:18.442Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-phy041-phy-prd-writer/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T16:20:13.571Z","emptyReason":null},"readme":"Skill: Phy Prd Writer\n\nOwner: phy041\n\nSummary: Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete,...\n\nTags: latest:1.0.2, product:1.0.0, requirements:1.0.0\n\nVersion history:\n\nv1.0.2 | 2026-03-22T14:03:37.298Z | auto\n\n- Documentation updated in SKILL.md with clearer formatting.\n- No changes to code or functionality; content remains the same.\n- Version bump likely for maintenance or documentation clarity.\n\nv1.0.1 | 2026-03-22T12:13:03.454Z | auto\n\n- Added a homepage link (`homepage: https://canlah.ai`) to SKILL.md.\n- No other functional or content changes in this version.\n\nv1.0.0 | 2026-03-07T10:47:13.594Z | user\n\nInitial release\n\nArchive index:\n\nArchive v1.0.2: 3 files, 6542 bytes\n\nFiles: skill-card.md (1985b), SKILL.md (11209b), _meta.json (133b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: prd-writer\ndescription: \"Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete, professional PRD. Use when starting a new feature, product, or project. Triggers on 'write PRD', 'create PRD', 'new feature', 'product requirements', or '/prd'.\"\nhomepage: https://canlah.ai\nmetadata: {\"openclaw\": {\"emoji\": \"📋\", \"os\": [\"darwin\", \"linux\"]}}\n---\n\n# PRD Writer - Multi-Turn Requirements Gathering\n\n## Overview\n\nGuide users through creating a professional PRD by asking focused questions one at a time. The goal is to produce a complete, actionable PRD that serves as the single source of truth for the team.\n\n## The Process\n\n### Phase 1: Problem Discovery (2-3 questions)\n\nStart by understanding the core problem:\n\n1. **Problem Statement**: \"What specific problem are you trying to solve? Describe the user pain point.\"\n2. **Why Now**: \"Why is this important to solve now? What happens if we don't solve it?\"\n3. **Existing Solutions**: \"How are users currently solving this problem (workarounds, competitors)?\"\n\n### Phase 2: User & Market (2-3 questions)\n\n4. **Target Users**: Ask who the primary users are. Offer common persona types:\n   - End consumers (B2C)\n   - Business users (B2B)\n   - Internal team members\n   - Developers/Technical users\n   - Other (specify)\n\n5. **User Context**: \"In what context will users encounter this? (e.g., mobile on-the-go, desktop at work, specific workflow)\"\n\n6. **Market Size/Impact**: \"How many users will this affect? Is this a core feature or nice-to-have?\"\n\n### Phase 3: Success Metrics (1-2 questions)\n\n7. **Definition of Success**: Ask what success looks like. Offer metric types:\n   - User engagement (DAU, retention, time spent)\n   - Business metrics (revenue, conversion, cost reduction)\n   - Technical metrics (performance, reliability, error rates)\n   - User satisfaction (NPS, CSAT, support tickets)\n\n8. **Specific Targets**: \"What specific numbers would indicate success? (e.g., 'reduce load time to <2s', 'increase conversion by 15%')\"\n\n### Phase 4: Scope Definition (2-3 questions)\n\n9. **Core Features**: \"What are the MUST-have features for v1? List the absolute minimum for launch.\"\n\n10. **Out of Scope**: \"What should we explicitly NOT build in this phase? (This prevents scope creep)\"\n\n11. **Future Considerations**: \"What features might come in v2/v3? (Park these for later)\"\n\n### Phase 5: Constraints & Dependencies (1-2 questions)\n\n12. **Technical Constraints**: Ask about limitations:\n    - Existing tech stack requirements\n    - Integration dependencies\n    - Performance requirements\n    - Security/compliance needs\n    - Budget/resource constraints\n\n13. **Timeline**: \"What's the target launch date or deadline? Any external dependencies?\"\n\n### Phase 6: Prioritization (1 question)\n\n14. **MoSCoW Ranking**: Present the collected features and ask user to categorize:\n    - **Must**: Essential for launch\n    - **Should**: Important but can defer if needed\n    - **Could**: Nice-to-have\n    - **Won't**: Explicitly excluded\n\n## Questioning Guidelines\n\n- **One question at a time** - Never overwhelm with multiple questions\n- **Use AskUserQuestion tool** with multiple choice options when categories are clear\n- **Offer \"Other\" option** for open-ended responses\n- **Summarize understanding** after each phase before moving on\n- **Allow backtracking** - If user wants to revise earlier answers, accommodate\n- **Skip if already answered** - If user provided info upfront, don't re-ask\n\n## Example Question Flow\n\n```\nQ1: \"What problem are you solving?\"\n→ User describes pain point\n\nQ2: \"Why is solving this urgent now?\"\n→ User explains timing\n\n[Summary]: \"So we're solving [X] because [Y]. Correct?\"\n→ User confirms or corrects\n\nQ3: \"Who are the primary users?\"\n→ [Multiple choice with AskUserQuestion]\n\n... continue through phases ...\n```\n\n## Output: PRD Document\n\nAfter gathering all information, generate a complete PRD with this structure:\n\n```markdown\n# PRD: [Product/Feature Name]\n\n## Metadata\n| Field | Value |\n|-------|-------|\n| Author | [User name] |\n| Status | Draft |\n| Created | [Date] |\n| Last Updated | [Date] |\n\n## 1. Problem Statement\n[Clear description of the problem and why it matters]\n\n### Why Now?\n[Urgency and timing rationale]\n\n## 2. Goals & Success Metrics\n### Objectives\n- [SMART goal 1]\n- [SMART goal 2]\n\n### Success Metrics (KPIs)\n| Metric | Current | Target | Timeline |\n|--------|---------|--------|----------|\n| [Metric 1] | [Baseline] | [Goal] | [When] |\n\n## 3. User & Market\n### Target Users\n[Primary persona description]\n\n### User Stories\n- As a [user type], I want [action] so that [benefit]\n\n### Competitive Landscape\n[How users solve this today]\n\n## 4. Scope\n### In Scope (v1)\n- [Must-have feature 1]\n- [Must-have feature 2]\n\n### Out of Scope\n- [Explicitly excluded 1]\n- [Explicitly excluded 2]\n\n### Future Considerations (v2+)\n- [Deferred feature 1]\n\n## 5. Feature Requirements\n### Feature: [Name]\n**Priority**: Must/Should/Could\n**Description**: [What it does]\n**Acceptance Criteria**:\n- [ ] [Criterion 1]\n- [ ] [Criterion 2]\n\n## 6. Technical Constraints\n- [Constraint 1]\n- [Constraint 2]\n\n### Dependencies\n- [External dependency 1]\n\n## 7. Timeline & Milestones\n| Milestone | Target Date |\n|-----------|-------------|\n| Design Complete | [Date] |\n| Development Start | [Date] |\n| Beta/Testing | [Date] |\n| Launch | [Date] |\n\n## 8. Open Questions\n- [Unresolved question 1]\n- [Unresolved question 2]\n\n## 9. Appendix\n[Any additional context, wireframes references, research links]\n```\n\n## After PRD Generation\n\n### Step 1: Save & Share\n1. **Save PRD**: Ask where to save (`docs/prd/`, `docs/specs/`, or custom path)\n2. **Commit to git**: Create a commit with the PRD document\n3. **Share for review**: Suggest sending to stakeholders for feedback\n\n### Step 2: Design (if UI/UX involved)\nAsk: \"Does this feature need UI design?\"\n- **Yes** → Suggest using `/brainstorming` skill to explore design approaches\n- **Yes + need mockups** → Suggest `/frontend-design` for wireframes/prototypes\n- **No** → Skip to implementation planning\n\n### Step 3: Technical Architecture\nAsk: \"Is this feature complex enough to need a technical architecture design?\"\n- **Complex feature** → Use `architect` subagent for system design\n  - Output: component breakdown, data flow, tech selection, interface design\n- **Simple feature** → Skip to task breakdown\n\n### Step 4: Break into Tasks\nAsk: \"Do you want to break the PRD into development tasks?\"\n- **Yes** → Use `planner` subagent to create implementation plan\n  - Break down based on architecture design\n  - Generate TaskCreate items with:\n    - Clear acceptance criteria from PRD\n    - Dependencies marked (blockedBy)\n    - Priority from MoSCoW ranking\n\n### Step 5: Implementation\nOnce tasks are created:\n1. `planner` → Detailed implementation plan per task\n2. Write code\n3. `code-reviewer` → Auto-review before commit\n4. `test-creator` → Generate tests\n5. `security-reviewer` → If sensitive code\n\n### Step 6: Validation\nBefore shipping:\n1. `e2e-runner` → Automated testing\n2. Compare against PRD success metrics\n3. Update PRD status to \"Shipped\"\n\n## Workflow Cheatsheet\n\n```\nPhase 0: Requirements\n/prd-writer          → Multi-turn Q&A to gather requirements, generate PRD\n\nPhase 1: Planning\narchitect agent      → Technical architecture design (how to build it)\nplanner agent        → Break into implementation tasks (what to build)\n\nPhase 2: Implementation\n[write code]\n\nPhase 3: Quality Assurance (parallel)\ncode-reviewer + security-reviewer  → simultaneous review\ntest-creator                       → add tests\n\nPhase 4: Validation\ne2e-runner           → end-to-end validation\ndoc-updater          → update documentation\n\nPRD status → Shipped\n```\n\n## Handoff Prompts\n\nAfter PRD is complete, offer these next actions:\n\n```\nPRD generated! What would you like to do next?\n\n1. UI/UX Design Exploration (/brainstorming) - if there's an interface\n2. Technical Architecture Design (architect) - decide how to build it\n3. Break into Development Tasks (planner) - decide what to build\n4. Save for now, continue later\n```\n\nUse AskUserQuestion to let user choose.\n\n## Key Principles\n\n- **Problem before solution** - Never jump to features before understanding the problem\n- **Quantify success** - Vague goals lead to vague outcomes\n- **Explicit exclusions** - What you DON'T build is as important as what you do\n- **Living document** - Remind user to update as requirements evolve\n- **YAGNI** - Ruthlessly cut features that aren't essential for v1\n\n---\n\n## Lenny's Podcast Wisdom Integration\n\nWhen writing PRDs, automatically surface relevant wisdom from top product leaders. Use these to enrich the PRD process:\n\n### Phase 1: Problem Discovery\n> **April Dunford**: \"Really great positioning feels so clear, so simple - of course that's what it is.\"\n- Ask: What are competitive alternatives (including status quo)?\n- Remember: 40% of B2B deals are lost to \"no decision\" - you're competing with spreadsheets!\n\n> **Shreyas Doshi**: \"Most execution problems are actually strategy problems.\"\n- If user describes execution problems, dig deeper into strategy clarity\n\n### Phase 2: Why Now?\n> **Brian Chesky**: \"If you build a great product and no one knows about it, did you even build a product?\"\n- Ask: How will you tell the story of this product?\n- Think about every release as a chapter of a story\n\n### Phase 3: Scope Definition\n> **Brian Chesky**: \"Five teams should do one thing rather than one team do five things.\"\n- Ruthlessly cut scope\n- Ask: \"What would you cut to concentrate on fewer things?\"\n\n> **Brian Chesky**: \"The best way to slow a project down is add more people to it.\"\n- Small team, focused scope = faster delivery\n\n### Phase 4: Success Metrics\n> **Marty Cagan**: \"Optimization is easier than innovation; but only innovation wins.\"\n- Don't just optimize metrics - ask what new value is created\n- Everything in the backlog is a bet - make better bets\n\n### Phase 5: Risk Assessment\n> **Shreyas Doshi**: Pre-mortem framework\nAfter PRD is drafted, suggest running a pre-mortem:\n- **Tigers**: Real threats that could kill the project\n- **Paper Tigers**: Seeming threats that aren't real\n- **Elephants**: Things nobody is talking about\n\nAsk: \"What 3 tigers (real threats) could derail this project?\"\n\n### Phase 6: Prioritization\n> **Shreyas Doshi**: LNO Framework\n- **L (Leverage)**: Which features give 10-100x return? Focus here.\n- **N (Neutral)**: Standard features, 1x return\n- **O (Overhead)**: Features with less return than effort\n\n### Reference: Wisdom Source\nAll wisdom sourced from Lenny's Podcast. If you have local transcripts, search them for additional context.\n\n## Quick Mode\n\nIf user says \"quick PRD\" or \"lean PRD\", use abbreviated flow:\n1. Problem (1 question)\n2. Users (1 question)\n3. Success metric (1 question)\n4. Must-have features (1 question)\n5. Generate One-Pager PRD format\n\n---\n\n## Author\n\n**[Canlah AI](https://canlah.ai)** — Run performance marketing without breaking your brand.\n\n- GitHub: [github.com/PHY041](https://github.com/PHY041)\n- All Skills: [clawhub.ai/PHY041](https://clawhub.ai/PHY041)\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn7fdhcxytgt3k2vvnc24c8ke581g5j1\",\n  \"slug\": \"phy-prd-writer\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1774188217298\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:\n\nMulti-turn PRD (Product Requirements Document) creation assistant that asks clarifying questions one at a time to gather requirements, then generates a complete, professional PRD.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[phy041](https://clawhub.ai/user/phy041)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nProduct managers, founders, and development teams use this skill to gather requirements through a guided question flow and produce a structured PRD for a new feature, product, or project.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger phrases may start the PRD workflow when the user's intent is ambiguous.\n\nMitigation: Prefer explicit invocations such as /prd, write a PRD, or create a PRD before using the skill.\n\nRisk: The skill may propose saving files, creating git commits, handing off to other agents, or searching local transcripts after drafting a PRD.\n\nMitigation: Review and approve each proposed path, commit, handoff, and local search scope before allowing the action to proceed.\n\n## Reference(s):\n\n- [Phy Prd Writer ClawHub skill page](https://clawhub.ai/phy041/skills/phy-prd-writer)\n- [Publisher profile: phy041](https://clawhub.ai/user/phy041)\n- [Canlah AI homepage](https://canlah.ai)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance, Shell commands]\n\n**Output Format:** [Markdown PRD document with guided follow-up prompts]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose save locations, git commits, agent handoffs, and local transcript searches after the PRD is generated.]\n\n## Skill Version(s):\n\n1.0.2 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.1: 2 files, 5304 bytes\n\nFiles: SKILL.md (10979b), _meta.json (133b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: prd-writer\ndescription: \"Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete, professional PRD. Use when starting a new feature, product, or project. Triggers on 'write PRD', 'create PRD', 'new feature', 'product requirements', or '/prd'.\"\nhomepage: https://canlah.ai\nmetadata: {\"openclaw\": {\"emoji\": \"📋\", \"os\": [\"darwin\", \"linux\"]}}\n---\n\n# PRD Writer - Multi-Turn Requirements Gathering\n\n## Overview\n\nGuide users through creating a professional PRD by asking focused questions one at a time. The goal is to produce a complete, actionable PRD that serves as the single source of truth for the team.\n\n## The Process\n\n### Phase 1: Problem Discovery (2-3 questions)\n\nStart by understanding the core problem:\n\n1. **Problem Statement**: \"What specific problem are you trying to solve? Describe the user pain point.\"\n2. **Why Now**: \"Why is this important to solve now? What happens if we don't solve it?\"\n3. **Existing Solutions**: \"How are users currently solving this problem (workarounds, competitors)?\"\n\n### Phase 2: User & Market (2-3 questions)\n\n4. **Target Users**: Ask who the primary users are. Offer common persona types:\n   - End consumers (B2C)\n   - Business users (B2B)\n   - Internal team members\n   - Developers/Technical users\n   - Other (specify)\n\n5. **User Context**: \"In what context will users encounter this? (e.g., mobile on-the-go, desktop at work, specific workflow)\"\n\n6. **Market Size/Impact**: \"How many users will this affect? Is this a core feature or nice-to-have?\"\n\n### Phase 3: Success Metrics (1-2 questions)\n\n7. **Definition of Success**: Ask what success looks like. Offer metric types:\n   - User engagement (DAU, retention, time spent)\n   - Business metrics (revenue, conversion, cost reduction)\n   - Technical metrics (performance, reliability, error rates)\n   - User satisfaction (NPS, CSAT, support tickets)\n\n8. **Specific Targets**: \"What specific numbers would indicate success? (e.g., 'reduce load time to <2s', 'increase conversion by 15%')\"\n\n### Phase 4: Scope Definition (2-3 questions)\n\n9. **Core Features**: \"What are the MUST-have features for v1? List the absolute minimum for launch.\"\n\n10. **Out of Scope**: \"What should we explicitly NOT build in this phase? (This prevents scope creep)\"\n\n11. **Future Considerations**: \"What features might come in v2/v3? (Park these for later)\"\n\n### Phase 5: Constraints & Dependencies (1-2 questions)\n\n12. **Technical Constraints**: Ask about limitations:\n    - Existing tech stack requirements\n    - Integration dependencies\n    - Performance requirements\n    - Security/compliance needs\n    - Budget/resource constraints\n\n13. **Timeline**: \"What's the target launch date or deadline? Any external dependencies?\"\n\n### Phase 6: Prioritization (1 question)\n\n14. **MoSCoW Ranking**: Present the collected features and ask user to categorize:\n    - **Must**: Essential for launch\n    - **Should**: Important but can defer if needed\n    - **Could**: Nice-to-have\n    - **Won't**: Explicitly excluded\n\n## Questioning Guidelines\n\n- **One question at a time** - Never overwhelm with multiple questions\n- **Use AskUserQuestion tool** with multiple choice options when categories are clear\n- **Offer \"Other\" option** for open-ended responses\n- **Summarize understanding** after each phase before moving on\n- **Allow backtracking** - If user wants to revise earlier answers, accommodate\n- **Skip if already answered** - If user provided info upfront, don't re-ask\n\n## Example Question Flow\n\n```\nQ1: \"What problem are you solving?\"\n→ User describes pain point\n\nQ2: \"Why is solving this urgent now?\"\n→ User explains timing\n\n[Summary]: \"So we're solving [X] because [Y]. Correct?\"\n→ User confirms or corrects\n\nQ3: \"Who are the primary users?\"\n→ [Multiple choice with AskUserQuestion]\n\n... continue through phases ...\n```\n\n## Output: PRD Document\n\nAfter gathering all information, generate a complete PRD with this structure:\n\n```markdown\n# PRD: [Product/Feature Name]\n\n## Metadata\n| Field | Value |\n|-------|-------|\n| Author | [User name] |\n| Status | Draft |\n| Created | [Date] |\n| Last Updated | [Date] |\n\n## 1. Problem Statement\n[Clear description of the problem and why it matters]\n\n### Why Now?\n[Urgency and timing rationale]\n\n## 2. Goals & Success Metrics\n### Objectives\n- [SMART goal 1]\n- [SMART goal 2]\n\n### Success Metrics (KPIs)\n| Metric | Current | Target | Timeline |\n|--------|---------|--------|----------|\n| [Metric 1] | [Baseline] | [Goal] | [When] |\n\n## 3. User & Market\n### Target Users\n[Primary persona description]\n\n### User Stories\n- As a [user type], I want [action] so that [benefit]\n\n### Competitive Landscape\n[How users solve this today]\n\n## 4. Scope\n### In Scope (v1)\n- [Must-have feature 1]\n- [Must-have feature 2]\n\n### Out of Scope\n- [Explicitly excluded 1]\n- [Explicitly excluded 2]\n\n### Future Considerations (v2+)\n- [Deferred feature 1]\n\n## 5. Feature Requirements\n### Feature: [Name]\n**Priority**: Must/Should/Could\n**Description**: [What it does]\n**Acceptance Criteria**:\n- [ ] [Criterion 1]\n- [ ] [Criterion 2]\n\n## 6. Technical Constraints\n- [Constraint 1]\n- [Constraint 2]\n\n### Dependencies\n- [External dependency 1]\n\n## 7. Timeline & Milestones\n| Milestone | Target Date |\n|-----------|-------------|\n| Design Complete | [Date] |\n| Development Start | [Date] |\n| Beta/Testing | [Date] |\n| Launch | [Date] |\n\n## 8. Open Questions\n- [Unresolved question 1]\n- [Unresolved question 2]\n\n## 9. Appendix\n[Any additional context, wireframes references, research links]\n```\n\n## After PRD Generation\n\n### Step 1: Save & Share\n1. **Save PRD**: Ask where to save (`docs/prd/`, `docs/specs/`, or custom path)\n2. **Commit to git**: Create a commit with the PRD document\n3. **Share for review**: Suggest sending to stakeholders for feedback\n\n### Step 2: Design (if UI/UX involved)\nAsk: \"Does this feature need UI design?\"\n- **Yes** → Suggest using `/brainstorming` skill to explore design approaches\n- **Yes + need mockups** → Suggest `/frontend-design` for wireframes/prototypes\n- **No** → Skip to implementation planning\n\n### Step 3: Technical Architecture\nAsk: \"Is this feature complex enough to need a technical architecture design?\"\n- **Complex feature** → Use `architect` subagent for system design\n  - Output: component breakdown, data flow, tech selection, interface design\n- **Simple feature** → Skip to task breakdown\n\n### Step 4: Break into Tasks\nAsk: \"Do you want to break the PRD into development tasks?\"\n- **Yes** → Use `planner` subagent to create implementation plan\n  - Break down based on architecture design\n  - Generate TaskCreate items with:\n    - Clear acceptance criteria from PRD\n    - Dependencies marked (blockedBy)\n    - Priority from MoSCoW ranking\n\n### Step 5: Implementation\nOnce tasks are created:\n1. `planner` → Detailed implementation plan per task\n2. Write code\n3. `code-reviewer` → Auto-review before commit\n4. `test-creator` → Generate tests\n5. `security-reviewer` → If sensitive code\n\n### Step 6: Validation\nBefore shipping:\n1. `e2e-runner` → Automated testing\n2. Compare against PRD success metrics\n3. Update PRD status to \"Shipped\"\n\n## Workflow Cheatsheet\n\n```\nPhase 0: Requirements\n/prd-writer          → Multi-turn Q&A to gather requirements, generate PRD\n\nPhase 1: Planning\narchitect agent      → Technical architecture design (how to build it)\nplanner agent        → Break into implementation tasks (what to build)\n\nPhase 2: Implementation\n[write code]\n\nPhase 3: Quality Assurance (parallel)\ncode-reviewer + security-reviewer  → simultaneous review\ntest-creator                       → add tests\n\nPhase 4: Validation\ne2e-runner           → end-to-end validation\ndoc-updater          → update documentation\n\nPRD status → Shipped\n```\n\n## Handoff Prompts\n\nAfter PRD is complete, offer these next actions:\n\n```\nPRD generated! What would you like to do next?\n\n1. UI/UX Design Exploration (/brainstorming) - if there's an interface\n2. Technical Architecture Design (architect) - decide how to build it\n3. Break into Development Tasks (planner) - decide what to build\n4. Save for now, continue later\n```\n\nUse AskUserQuestion to let user choose.\n\n## Key Principles\n\n- **Problem before solution** - Never jump to features before understanding the problem\n- **Quantify success** - Vague goals lead to vague outcomes\n- **Explicit exclusions** - What you DON'T build is as important as what you do\n- **Living document** - Remind user to update as requirements evolve\n- **YAGNI** - Ruthlessly cut features that aren't essential for v1\n\n---\n\n## Lenny's Podcast Wisdom Integration\n\nWhen writing PRDs, automatically surface relevant wisdom from top product leaders. Use these to enrich the PRD process:\n\n### Phase 1: Problem Discovery\n> **April Dunford**: \"Really great positioning feels so clear, so simple - of course that's what it is.\"\n- Ask: What are competitive alternatives (including status quo)?\n- Remember: 40% of B2B deals are lost to \"no decision\" - you're competing with spreadsheets!\n\n> **Shreyas Doshi**: \"Most execution problems are actually strategy problems.\"\n- If user describes execution problems, dig deeper into strategy clarity\n\n### Phase 2: Why Now?\n> **Brian Chesky**: \"If you build a great product and no one knows about it, did you even build a product?\"\n- Ask: How will you tell the story of this product?\n- Think about every release as a chapter of a story\n\n### Phase 3: Scope Definition\n> **Brian Chesky**: \"Five teams should do one thing rather than one team do five things.\"\n- Ruthlessly cut scope\n- Ask: \"What would you cut to concentrate on fewer things?\"\n\n> **Brian Chesky**: \"The best way to slow a project down is add more people to it.\"\n- Small team, focused scope = faster delivery\n\n### Phase 4: Success Metrics\n> **Marty Cagan**: \"Optimization is easier than innovation; but only innovation wins.\"\n- Don't just optimize metrics - ask what new value is created\n- Everything in the backlog is a bet - make better bets\n\n### Phase 5: Risk Assessment\n> **Shreyas Doshi**: Pre-mortem framework\nAfter PRD is drafted, suggest running a pre-mortem:\n- **Tigers**: Real threats that could kill the project\n- **Paper Tigers**: Seeming threats that aren't real\n- **Elephants**: Things nobody is talking about\n\nAsk: \"What 3 tigers (real threats) could derail this project?\"\n\n### Phase 6: Prioritization\n> **Shreyas Doshi**: LNO Framework\n- **L (Leverage)**: Which features give 10-100x return? Focus here.\n- **N (Neutral)**: Standard features, 1x return\n- **O (Overhead)**: Features with less return than effort\n\n### Reference: Wisdom Source\nAll wisdom sourced from Lenny's Podcast. If you have local transcripts, search them for additional context.\n\n## Quick Mode\n\nIf user says \"quick PRD\" or \"lean PRD\", use abbreviated flow:\n1. Problem (1 question)\n2. Users (1 question)\n3. Success metric (1 question)\n4. Must-have features (1 question)\n5. Generate One-Pager PRD format\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn7fdhcxytgt3k2vvnc24c8ke581g5j1\",\n  \"slug\": \"phy-prd-writer\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1774181583454\n}\n\nArchive v1.0.0: 2 files, 5282 bytes\n\nFiles: SKILL.md (10951b), _meta.json (133b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: prd-writer\ndescription: \"Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete, professional PRD. Use when starting a new feature, product, or project. Triggers on 'write PRD', 'create PRD', 'new feature', 'product requirements', or '/prd'.\"\nmetadata: {\"openclaw\": {\"emoji\": \"📋\", \"os\": [\"darwin\", \"linux\"]}}\n---\n\n# PRD Writer - Multi-Turn Requirements Gathering\n\n## Overview\n\nGuide users through creating a professional PRD by asking focused questions one at a time. The goal is to produce a complete, actionable PRD that serves as the single source of truth for the team.\n\n## The Process\n\n### Phase 1: Problem Discovery (2-3 questions)\n\nStart by understanding the core problem:\n\n1. **Problem Statement**: \"What specific problem are you trying to solve? Describe the user pain point.\"\n2. **Why Now**: \"Why is this important to solve now? What happens if we don't solve it?\"\n3. **Existing Solutions**: \"How are users currently solving this problem (workarounds, competitors)?\"\n\n### Phase 2: User & Market (2-3 questions)\n\n4. **Target Users**: Ask who the primary users are. Offer common persona types:\n   - End consumers (B2C)\n   - Business users (B2B)\n   - Internal team members\n   - Developers/Technical users\n   - Other (specify)\n\n5. **User Context**: \"In what context will users encounter this? (e.g., mobile on-the-go, desktop at work, specific workflow)\"\n\n6. **Market Size/Impact**: \"How many users will this affect? Is this a core feature or nice-to-have?\"\n\n### Phase 3: Success Metrics (1-2 questions)\n\n7. **Definition of Success**: Ask what success looks like. Offer metric types:\n   - User engagement (DAU, retention, time spent)\n   - Business metrics (revenue, conversion, cost reduction)\n   - Technical metrics (performance, reliability, error rates)\n   - User satisfaction (NPS, CSAT, support tickets)\n\n8. **Specific Targets**: \"What specific numbers would indicate success? (e.g., 'reduce load time to <2s', 'increase conversion by 15%')\"\n\n### Phase 4: Scope Definition (2-3 questions)\n\n9. **Core Features**: \"What are the MUST-have features for v1? List the absolute minimum for launch.\"\n\n10. **Out of Scope**: \"What should we explicitly NOT build in this phase? (This prevents scope creep)\"\n\n11. **Future Considerations**: \"What features might come in v2/v3? (Park these for later)\"\n\n### Phase 5: Constraints & Dependencies (1-2 questions)\n\n12. **Technical Constraints**: Ask about limitations:\n    - Existing tech stack requirements\n    - Integration dependencies\n    - Performance requirements\n    - Security/compliance needs\n    - Budget/resource constraints\n\n13. **Timeline**: \"What's the target launch date or deadline? Any external dependencies?\"\n\n### Phase 6: Prioritization (1 question)\n\n14. **MoSCoW Ranking**: Present the collected features and ask user to categorize:\n    - **Must**: Essential for launch\n    - **Should**: Important but can defer if needed\n    - **Could**: Nice-to-have\n    - **Won't**: Explicitly excluded\n\n## Questioning Guidelines\n\n- **One question at a time** - Never overwhelm with multiple questions\n- **Use AskUserQuestion tool** with multiple choice options when categories are clear\n- **Offer \"Other\" option** for open-ended responses\n- **Summarize understanding** after each phase before moving on\n- **Allow backtracking** - If user wants to revise earlier answers, accommodate\n- **Skip if already answered** - If user provided info upfront, don't re-ask\n\n## Example Question Flow\n\n```\nQ1: \"What problem are you solving?\"\n→ User describes pain point\n\nQ2: \"Why is solving this urgent now?\"\n→ User explains timing\n\n[Summary]: \"So we're solving [X] because [Y]. Correct?\"\n→ User confirms or corrects\n\nQ3: \"Who are the primary users?\"\n→ [Multiple choice with AskUserQuestion]\n\n... continue through phases ...\n```\n\n## Output: PRD Document\n\nAfter gathering all information, generate a complete PRD with this structure:\n\n```markdown\n# PRD: [Product/Feature Name]\n\n## Metadata\n| Field | Value |\n|-------|-------|\n| Author | [User name] |\n| Status | Draft |\n| Created | [Date] |\n| Last Updated | [Date] |\n\n## 1. Problem Statement\n[Clear description of the problem and why it matters]\n\n### Why Now?\n[Urgency and timing rationale]\n\n## 2. Goals & Success Metrics\n### Objectives\n- [SMART goal 1]\n- [SMART goal 2]\n\n### Success Metrics (KPIs)\n| Metric | Current | Target | Timeline |\n|--------|---------|--------|----------|\n| [Metric 1] | [Baseline] | [Goal] | [When] |\n\n## 3. User & Market\n### Target Users\n[Primary persona description]\n\n### User Stories\n- As a [user type], I want [action] so that [benefit]\n\n### Competitive Landscape\n[How users solve this today]\n\n## 4. Scope\n### In Scope (v1)\n- [Must-have feature 1]\n- [Must-have feature 2]\n\n### Out of Scope\n- [Explicitly excluded 1]\n- [Explicitly excluded 2]\n\n### Future Considerations (v2+)\n- [Deferred feature 1]\n\n## 5. Feature Requirements\n### Feature: [Name]\n**Priority**: Must/Should/Could\n**Description**: [What it does]\n**Acceptance Criteria**:\n- [ ] [Criterion 1]\n- [ ] [Criterion 2]\n\n## 6. Technical Constraints\n- [Constraint 1]\n- [Constraint 2]\n\n### Dependencies\n- [External dependency 1]\n\n## 7. Timeline & Milestones\n| Milestone | Target Date |\n|-----------|-------------|\n| Design Complete | [Date] |\n| Development Start | [Date] |\n| Beta/Testing | [Date] |\n| Launch | [Date] |\n\n## 8. Open Questions\n- [Unresolved question 1]\n- [Unresolved question 2]\n\n## 9. Appendix\n[Any additional context, wireframes references, research links]\n```\n\n## After PRD Generation\n\n### Step 1: Save & Share\n1. **Save PRD**: Ask where to save (`docs/prd/`, `docs/specs/`, or custom path)\n2. **Commit to git**: Create a commit with the PRD document\n3. **Share for review**: Suggest sending to stakeholders for feedback\n\n### Step 2: Design (if UI/UX involved)\nAsk: \"Does this feature need UI design?\"\n- **Yes** → Suggest using `/brainstorming` skill to explore design approaches\n- **Yes + need mockups** → Suggest `/frontend-design` for wireframes/prototypes\n- **No** → Skip to implementation planning\n\n### Step 3: Technical Architecture\nAsk: \"Is this feature complex enough to need a technical architecture design?\"\n- **Complex feature** → Use `architect` subagent for system design\n  - Output: component breakdown, data flow, tech selection, interface design\n- **Simple feature** → Skip to task breakdown\n\n### Step 4: Break into Tasks\nAsk: \"Do you want to break the PRD into development tasks?\"\n- **Yes** → Use `planner` subagent to create implementation plan\n  - Break down based on architecture design\n  - Generate TaskCreate items with:\n    - Clear acceptance criteria from PRD\n    - Dependencies marked (blockedBy)\n    - Priority from MoSCoW ranking\n\n### Step 5: Implementation\nOnce tasks are created:\n1. `planner` → Detailed implementation plan per task\n2. Write code\n3. `code-reviewer` → Auto-review before commit\n4. `test-creator` → Generate tests\n5. `security-reviewer` → If sensitive code\n\n### Step 6: Validation\nBefore shipping:\n1. `e2e-runner` → Automated testing\n2. Compare against PRD success metrics\n3. Update PRD status to \"Shipped\"\n\n## Workflow Cheatsheet\n\n```\nPhase 0: Requirements\n/prd-writer          → Multi-turn Q&A to gather requirements, generate PRD\n\nPhase 1: Planning\narchitect agent      → Technical architecture design (how to build it)\nplanner agent        → Break into implementation tasks (what to build)\n\nPhase 2: Implementation\n[write code]\n\nPhase 3: Quality Assurance (parallel)\ncode-reviewer + security-reviewer  → simultaneous review\ntest-creator                       → add tests\n\nPhase 4: Validation\ne2e-runner           → end-to-end validation\ndoc-updater          → update documentation\n\nPRD status → Shipped\n```\n\n## Handoff Prompts\n\nAfter PRD is complete, offer these next actions:\n\n```\nPRD generated! What would you like to do next?\n\n1. UI/UX Design Exploration (/brainstorming) - if there's an interface\n2. Technical Architecture Design (architect) - decide how to build it\n3. Break into Development Tasks (planner) - decide what to build\n4. Save for now, continue later\n```\n\nUse AskUserQuestion to let user choose.\n\n## Key Principles\n\n- **Problem before solution** - Never jump to features before understanding the problem\n- **Quantify success** - Vague goals lead to vague outcomes\n- **Explicit exclusions** - What you DON'T build is as important as what you do\n- **Living document** - Remind user to update as requirements evolve\n- **YAGNI** - Ruthlessly cut features that aren't essential for v1\n\n---\n\n## Lenny's Podcast Wisdom Integration\n\nWhen writing PRDs, automatically surface relevant wisdom from top product leaders. Use these to enrich the PRD process:\n\n### Phase 1: Problem Discovery\n> **April Dunford**: \"Really great positioning feels so clear, so simple - of course that's what it is.\"\n- Ask: What are competitive alternatives (including status quo)?\n- Remember: 40% of B2B deals are lost to \"no decision\" - you're competing with spreadsheets!\n\n> **Shreyas Doshi**: \"Most execution problems are actually strategy problems.\"\n- If user describes execution problems, dig deeper into strategy clarity\n\n### Phase 2: Why Now?\n> **Brian Chesky**: \"If you build a great product and no one knows about it, did you even build a product?\"\n- Ask: How will you tell the story of this product?\n- Think about every release as a chapter of a story\n\n### Phase 3: Scope Definition\n> **Brian Chesky**: \"Five teams should do one thing rather than one team do five things.\"\n- Ruthlessly cut scope\n- Ask: \"What would you cut to concentrate on fewer things?\"\n\n> **Brian Chesky**: \"The best way to slow a project down is add more people to it.\"\n- Small team, focused scope = faster delivery\n\n### Phase 4: Success Metrics\n> **Marty Cagan**: \"Optimization is easier than innovation; but only innovation wins.\"\n- Don't just optimize metrics - ask what new value is created\n- Everything in the backlog is a bet - make better bets\n\n### Phase 5: Risk Assessment\n> **Shreyas Doshi**: Pre-mortem framework\nAfter PRD is drafted, suggest running a pre-mortem:\n- **Tigers**: Real threats that could kill the project\n- **Paper Tigers**: Seeming threats that aren't real\n- **Elephants**: Things nobody is talking about\n\nAsk: \"What 3 tigers (real threats) could derail this project?\"\n\n### Phase 6: Prioritization\n> **Shreyas Doshi**: LNO Framework\n- **L (Leverage)**: Which features give 10-100x return? Focus here.\n- **N (Neutral)**: Standard features, 1x return\n- **O (Overhead)**: Features with less return than effort\n\n### Reference: Wisdom Source\nAll wisdom sourced from Lenny's Podcast. If you have local transcripts, search them for additional context.\n\n## Quick Mode\n\nIf user says \"quick PRD\" or \"lean PRD\", use abbreviated flow:\n1. Problem (1 question)\n2. Users (1 question)\n3. Success metric (1 question)\n4. Must-have features (1 question)\n5. Generate One-Pager PRD format\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn7fdhcxytgt3k2vvnc24c8ke581g5j1\",\n  \"slug\": \"phy-prd-writer\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1772880433594\n}","readmeExcerpt":"Skill: Phy Prd Writer Owner: phy041 Summary: Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete,... Tags: latest:1.0.2, product:1.0.0, requirements:1.0.0 Version history: v1.0.2 | 2026-03-22T14:03:37.298Z | auto - Documentation updated in SKILL.md with clearer formatting. - No changes to code or functionality; co","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"Q1: \"What problem are you solving?\"\n→ User describes pain point\n\nQ2: \"Why is solving this urgent now?\"\n→ User explains timing\n\n[Summary]: \"So we're solving [X] because [Y]. Correct?\"\n→ User confirms or corrects\n\nQ3: \"Who are the primary users?\"\n→ [Multiple choice with AskUserQuestion]\n\n... continue through phases ..."},{"language":"markdown","snippet":"# PRD: [Product/Feature Name]\n\n## Metadata\n| Field | Value |\n|-------|-------|\n| Author | [User name] |\n| Status | Draft |\n| Created | [Date] |\n| Last Updated | [Date] |\n\n## 1. Problem Statement\n[Clear description of the problem and why it matters]\n\n### Why Now?\n[Urgency and timing rationale]\n\n## 2. Goals & Success Metrics\n### Objectives\n- [SMART goal 1]\n- [SMART goal 2]\n\n### Success Metrics (KPIs)\n| Metric | Current | Target | Timeline |\n|--------|---------|--------|----------|\n| [Metric 1] | [Baseline] | [Goal] | [When] |\n\n## 3. User & Market\n### Target Users\n[Primary persona description]\n\n### User Stories\n- As a [user type], I want [action] so that [benefit]\n\n### Competitive Landscape\n[How users solve this today]\n\n## 4. Scope\n### In Scope (v1)\n- [Must-have feature 1]\n- [Must-have feature 2]\n\n### Out of Scope\n- [Explicitly excluded 1]\n- [Explicitly excluded 2]\n\n### Future Considerations (v2+)\n- [Deferred feature 1]\n\n## 5. Feature Requirements\n### Feature: [Name]\n**Priority**: Must/Should/Could\n**Description**: [What it does]\n**Acceptance Criteria**:\n- [ ] [Criterion 1]\n- [ ] [Criterion 2]\n\n## 6. Technical Constraints\n- [Constraint 1]\n- [Constraint 2]\n\n### Dependencies\n- [External dependency 1]\n\n## 7. Timeline & Milestones\n| Milestone | Target Date |\n|-----------|-------------|\n| Design Complete | [Date] |\n| Development Start | [Date] |\n| Beta/Testing | [Date] |\n| Launch | [Date] |\n\n## 8. Open Questions\n- [Unresolved question 1]\n- [Unresolved question 2]\n\n## 9. Appendix\n[Any additional context, wireframes references, research links]"},{"language":"text","snippet":"Phase 0: Requirements\n/prd-writer          → Multi-turn Q&A to gather requirements, generate PRD\n\nPhase 1: Planning\narchitect agent      → Technical architecture design (how to build it)\nplanner agent        → Break into implementation tasks (what to build)\n\nPhase 2: Implementation\n[write code]\n\nPhase 3: Quality Assurance (parallel)\ncode-reviewer + security-reviewer  → simultaneous review\ntest-creator                       → add tests\n\nPhase 4: Validation\ne2e-runner           → end-to-end validation\ndoc-updater          → update documentation\n\nPRD status → Shipped"},{"language":"text","snippet":"PRD generated! What would you like to do next?\n\n1. UI/UX Design Exploration (/brainstorming) - if there's an interface\n2. Technical Architecture Design (architect) - decide how to build it\n3. Break into Development Tasks (planner) - decide what to build\n4. Save for now, continue later"},{"language":"text","snippet":"Q1: \"What problem are you solving?\"\n→ User describes pain point\n\nQ2: \"Why is solving this urgent now?\"\n→ User explains timing\n\n[Summary]: \"So we're solving [X] because [Y]. Correct?\"\n→ User confirms or corrects\n\nQ3: \"Who are the primary users?\"\n→ [Multiple choice with AskUserQuestion]\n\n... continue through phases ..."},{"language":"markdown","snippet":"# PRD: [Product/Feature Name]\n\n## Metadata\n| Field | Value |\n|-------|-------|\n| Author | [User name] |\n| Status | Draft |\n| Created | [Date] |\n| Last Updated | [Date] |\n\n## 1. Problem Statement\n[Clear description of the problem and why it matters]\n\n### Why Now?\n[Urgency and timing rationale]\n\n## 2. Goals & Success Metrics\n### Objectives\n- [SMART goal 1]\n- [SMART goal 2]\n\n### Success Metrics (KPIs)\n| Metric | Current | Target | Timeline |\n|--------|---------|--------|----------|\n| [Metric 1] | [Baseline] | [Goal] | [When] |\n\n## 3. User & Market\n### Target Users\n[Primary persona description]\n\n### User Stories\n- As a [user type], I want [action] so that [benefit]\n\n### Competitive Landscape\n[How users solve this today]\n\n## 4. Scope\n### In Scope (v1)\n- [Must-have feature 1]\n- [Must-have feature 2]\n\n### Out of Scope\n- [Explicitly excluded 1]\n- [Explicitly excluded 2]\n\n### Future Considerations (v2+)\n- [Deferred feature 1]\n\n## 5. Feature Requirements\n### Feature: [Name]\n**Priority**: Must/Should/Could\n**Description**: [What it does]\n**Acceptance Criteria**:\n- [ ] [Criterion 1]\n- [ ] [Criterion 2]\n\n## 6. Technical Constraints\n- [Constraint 1]\n- [Constraint 2]\n\n### Dependencies\n- [External dependency 1]\n\n## 7. Timeline & Milestones\n| Milestone | Target Date |\n|-----------|-------------|\n| Design Complete | [Date] |\n| Development Start | [Date] |\n| Beta/Testing | [Date] |\n| Launch | [Date] |\n\n## 8. Open Questions\n- [Unresolved question 1]\n- [Unresolved question 2]\n\n## 9. Appendix\n[Any additional context, wireframes references, research links]"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: prd-writer\ndescription: \"Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete, professional PRD. Use when starting a new feature, product, or project. Triggers on 'write PRD', 'create PRD', 'new feature', 'product requirements', or '/prd'.\"\nhomepage: https://canlah.ai\nmetadata: {\"openclaw\": {\"emoji\": \"📋\", \"os\": [\"darwin\", \"linux\"]}}\n---\n\n# PRD Writer - Multi-Turn Requirements Gathering\n\n## Overview\n\nGuide users through creating a professional PRD by asking focused questions one at a time. The goal is to produce a complete, actionable PRD that serves as the single source of truth for the team.\n\n## The Process\n\n### Phase 1: Problem Discovery (2-3 questions)\n\nStart by understanding the core problem:\n\n1. **Problem Statement**: \"What specific problem are you trying to solve? Describe the user pain point.\"\n2. **Why Now**: \"Why is this important to solve now? What happens if we don't solve it?\"\n3. **Existing Solutions**: \"How are users currently solving this problem (workarounds, competitors)?\"\n\n### Phase 2: User & Market (2-3 questions)\n\n4. **Target Users**: Ask who the primary users are. Offer common persona types:\n   - End consumers (B2C)\n   - Business users (B2B)\n   - Internal team members\n   - Developers/Technical users\n   - Other (specify)\n\n5. **User Context**: \"In what context will users encounter this? (e.g., mobile on-the-go, desktop at work, specific workflow)\"\n\n6. **Market Size/Impact**: \"How many users will this affect? Is this a core feature or nice-to-have?\"\n\n### Phase 3: Success Metrics (1-2 questions)\n\n7. **Definition of Success**: Ask what success looks like. Offer metric types:\n   - User engagement (DAU, retention, time spent)\n   - Business metrics (revenue, conversion, cost reduction)\n   - Technical metrics (performance, reliability, error rates)\n   - User satisfaction (NPS, CSAT, support tickets)\n\n8. **Specific Targets**: \"What specific numbers would indicate success? (e.g., 'reduce load time to <2s', 'increase conversion by 15%')\"\n\n### Phase 4: Scope Definition (2-3 questions)\n\n9. **Core Features**: \"What are the MUST-have features for v1? List the absolute minimum for launch.\"\n\n10. **Out of Scope**: \"What should we explicitly NOT build in this phase? (This prevents scope creep)\"\n\n11. **Future Considerations**: \"What features might come in v2/v3? (Park these for later)\"\n\n### Phase 5: Constraints & Dependencies (1-2 questions)\n\n12. **Technical Constraints**: Ask about limitations:\n    - Existing tech stack requirements\n    - Integration dependencies\n    - Performance requirements\n    - Security/compliance needs\n    - Budget/resource constraints\n\n13. **Timeline**: \"What's the target launch date or deadline? Any external dependencies?\"\n\n### Phase 6: Prioritization (1 question)\n\n14. **MoSCoW Ranking**: Present the collected features and ask user to categorize:\n    - **Must**: Essential for launch\n    - **Should**: Important"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7fdhcxytgt3k2vvnc24c8ke581g5j1\",\n  \"slug\": \"phy-prd-writer\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1774188217298\n}"},{"path":"skill-card.md","content":"## Description:\n\nMulti-turn PRD (Product Requirements Document) creation assistant that asks clarifying questions one at a time to gather requirements, then generates a complete, professional PRD.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[phy041](https://clawhub.ai/user/phy041)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nProduct managers, founders, and development teams use this skill to gather requirements through a guided question flow and produce a structured PRD for a new feature, product, or project.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger phrases may start the PRD workflow when the user's intent is ambiguous.\n\nMitigation: Prefer explicit invocations such as /prd, write a PRD, or create a PRD before using the skill.\n\nRisk: The skill may propose saving files, creating git commits, handing off to other agents, or searching local transcripts after drafting a PRD.\n\nMitigation: Review and approve each proposed path, commit, handoff, and local search scope before allowing the action to proceed.\n\n## Reference(s):\n\n- [Phy Prd Writer ClawHub skill page](https://clawhub.ai/phy041/skills/phy-prd-writer)\n- [Publisher profile: phy041](https://clawhub.ai/user/phy041)\n- [Canlah AI homepage](https://canlah.ai)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Guidance, Shell commands]\n\n**Output Format:** [Markdown PRD document with guided follow-up prompts]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May propose save locations, git commits, agent handoffs, and local transcript searches after the PRD is generated.]\n\n## Skill Version(s):\n\n1.0.2 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete,... Skill: Phy Prd Writer Owner: phy041 Summary: Multi-turn PRD (Product Requirements Document) creation assistant. Asks clarifying questions one at a time to gather requirements, then generates a complete,... Tags: latest:1.0.2, product:1.0.0, requirements:1.0.0 Version history: v1.0.2 | 2026-03-22T14:03:37.298Z | auto - Documentation updated in SKILL.md with clearer formatting. - No changes to code or functionality; co","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1071,"uniquenessScore":55,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T16:20:13.571Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T16:20:13.571Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T20:57:18.443Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}