aico-pm-prd-writing

SKILL.md

Before generating any content, check aico.json in project root for language field to determine the output language. If not set, default to English.

| "Requirements are clear enough" | Implicit requirements cause scope creep | | "We can refine the PRD later" | Late changes cost 10x more to implement | | "User will accept anything" | Users always have hidden expectations | | "It's just a small feature" | Small features grow into big problems |

Create comprehensive Product Requirements Documents (PRD) that define what to build and why, focusing on goals, scope, user stories, and success criteria without implementation details. Use this skill when: - User asks to "write a PRD", "create PRD", "write requirements document" - User mentions "requirements document", "product requirements", "product spec" - Running /pm.plan command to create version planning document - Starting a new product, major feature, or initiative that needs formal requirements - Need to document goals, scope, user stories, functional requirements, and success criteria Output: ALWAYS write PRD files to docs/reference/pm/versions/{version-name}.md Source: yellinzero/aico.

View raw