code-ai-installer 3.0.0 → 4.0.0

package/domains/development/locales/en/.agents/skills/pm-prd/SKILL.md

@@ -1,8 +1,34 @@
 ---
 name: pm-prd
 description: Generate a PRD — Vision, MVP, out-of-scope, user stories, acceptance criteria, NFR, risks, and open questions. The result must be verifiable.
+type: discretionary
+domain: development
+owners:
+  - product_manager
+gates:
+  - PM
+tech: []
+topic:
+  - pm
+triggers:
+  - write PRD
+  - Vision and MVP
+  - user stories
+  - acceptance criteria
+  - NFR requirements
+  - out-of-scope
+  - product risks
+related:
+  - pm-interview
+  - a11y-baseline
+  - pm-backlog
+  - ux-discovery
+  - ux-spec
+budget_lines: 250
+schema_version: 1
 ---
 
+
 # Skill: PRD (Product Requirements Document)
 
 A PRD that UX/ARCH/DEV/TEST can work from without "guessing".
@@ -22,13 +48,11 @@ A PRD that UX/ARCH/DEV/TEST can work from without "guessing".
 
 ```
 1. Input: Interview Summary (from $pm-interview)
-2. Draft PRD structure (section 2)
-3. Write user stories + acceptance criteria (section 3)
-4. Define NFR
-5. List risks + open questions
-6. Run quality checklist (section 4)
-7. Submit for User review
-8. After approval → handoff (section 5)
+2. Draft PRD structure (§2)
+3. Write user stories + acceptance criteria (§3)
+4. Define NFR + risks + open questions
+5. Run quality checklist (§4)
+6. Submit for User review → after approval, handoff (§5)
 ```
 
 ---
@@ -40,47 +64,59 @@ A PRD that UX/ARCH/DEV/TEST can work from without "guessing".
 | Field | Content |
 |-------|---------|
 | Problem | What pain point are we solving? |
-| Target audience | Who are the users? |
+| Target audience | Who are the users? (see Persona card §2.2) |
 | Value proposition | Why would they use this over alternatives? |
 | Success metrics | How do we measure success? (KPI / OKR) |
 
-### 2) Scope
+### 2) Persona Card (≥1 per primary user type; multi-sided product — one per side)
+
+```markdown
+**Persona:** <Name — archetype, not a real person>
+**Role / Context:** <profession + where they use the product>
+**Goals:** <what they want to achieve>
+**Pain points:** <current frustrations>
+**Constraints:** <device, skills, time, environment>
+```
+
+### 3) User Journey
+
+Stories ≠ flow. List key journeys by name + indicate which US-XX cover each step. Diagram/screen details — in `$ux-discovery`.
+
+### 4) Scope
 
 | In scope (MVP) | Out of scope | Rationale |
 |----------------|-------------|-----------|
 | Feature A | Feature X | Not MVP priority |
 | Feature B | Feature Y | Technical complexity, defer to v2 |
 
-### 3) Roles & Permissions
+### 5) Roles & Permissions
 
 | Role | Can do | Cannot do |
 |------|--------|-----------|
-| Site Owner | CRUD settings, coupons | Access other sites |
-| End User | View popup, copy coupon | Modify settings |
-
-### 4) User Stories → section 3
+| Workspace Admin | Manage members, configure workspace, view all data | Delete organization |
+| Member | Create/edit own resources, view shared resources | Manage other members |
+| Guest | View shared resources (read-only) | Create or edit anything |
 
-### 5) Acceptance Criteria → section 3
+### 6) User Stories & Acceptance Criteria → §3
 
-### 6) Non-Functional Requirements
+### 7) Non-Functional Requirements
 
 | Category | Requirement | Priority |
 |----------|-----------|:--------:|
-| **Security** | Input validation (Zod), no secrets in logs | P0 |
-| **Security** | Server-side auth on all protected endpoints | P0 |
-| **Performance** | API response < 500ms (p95) | P1 |
-| **Performance** | Widget load < 1s (LCP) | P1 |
+| **Security** | Input validation (Zod) + server-side auth on protected endpoints + no secrets in logs | P0 |
+| **Performance** | API response < 500ms (p95); public page load < 1s (LCP) | P1 |
 | **Reliability** | Graceful error handling, no 500 to user | P0 |
 | **Observability** | Structured logging (pino), request_id correlation | P1 |
-| **Accessibility** | WCAG 2.1 AA baseline (see $a11y-baseline) | P1 |
-| **Localization** | English only (MVP) | — |
+| **Accessibility** | WCAG 2.1 AA baseline (see `$a11y-baseline`) | P1 |
+| **Localization** | List of locales for MVP (e.g. `en` + `ru`) | per project |
 
-### 7) Risks & Open Questions
+### 8) Risks & Open Questions
 
 | # | Type | Description | Impact | Mitigation | Status |
 |---|------|------------|--------|-----------|:------:|
-| R-01 | Technical | Wix API rate limits | High | Caching, retry logic | Open |
-| R-02 | Product | User confusion with templates | Medium | Clear preview | Mitigated |
+| R-01 | Technical | External API rate limits | High | Caching, retry/backoff, queue | Open |
+| R-02 | Product | Users may misinterpret destructive actions | Medium | Confirm dialogs + undo window | Mitigated |
+| R-03 | Compliance | GDPR/PII handling unclear at MVP scope | High | Legal review pre-launch | Open |
 
 ---
 
@@ -95,26 +131,26 @@ A PRD that UX/ARCH/DEV/TEST can work from without "guessing".
 **I want to** <action>
 **So that** <benefit>
 
-**Priority:** P0 / P1 / P2
+**Priority:** P0 / P1 / P2  <!-- category and example — §3 Story categories below; single P0/P1/P2 definition for all PM skills is here -->
 
 #### Acceptance Criteria
 
 | # | Given | When | Then |
 |---|-------|------|------|
-| AC-01 | I am on Settings page | I change title and click Save | Title updates in widget preview |
-| AC-02 | I am on Settings page | I leave title empty and click Save | Validation error "Title required" shown |
-| AC-03 | Server is unavailable | I click Save | Error toast "Failed to save" shown |
+| AC-01 | <positive scenario> | <user action> | <expected result> |
+| AC-02 | <negative/invalid input> | <user action> | <validation error or guard> |
+| AC-03 | <edge case: server down, race, etc> | <user action> | <fallback behavior, no data loss> |
 ```
 
-### Story categories
+### Story categories (single source of truth for P0/P1/P2)
 
-| Category | Examples | Priority |
+| Category | Examples (mixed contexts) | Priority |
 |----------|---------|:--------:|
-| **Core CRUD** | Create coupon, update settings, delete coupon | P0 |
-| **Integration** | Install webhook, Wix auth, embed widget | P0 |
+| **Core CRUD** | Create invoice, update profile, delete record | P0 |
+| **Integration** | Auth (OAuth/SSO), webhook setup, embed component | P0 |
 | **UX Polish** | Loading states, empty states, toasts | P1 |
 | **Error Handling** | Network errors, validation, edge cases | P1 |
-| **Admin** | Analytics, export, bulk ops | P2 |
+| **Admin / Analytics** | Reporting, export, bulk ops, audit log | P2 |
 
 ---
 
@@ -132,42 +168,39 @@ A PRD that UX/ARCH/DEV/TEST can work from without "guessing".
 | PRD-08 | PRD is understandable without verbal explanation | ☐ |
 | PRD-09 | No vague language ("should be fast" → "< 500ms p95") | ☐ |
 | PRD-10 | Dependencies between stories identified | ☐ |
+| PRD-11 | At least 1 Persona card per primary user type | ☐ |
+| PRD-12 | User journeys listed (names + covering US-XX) | ☐ |
 
 ---
 
 ## 5. Handoff Checklist
 
-What PM passes to downstream gates:
-
 | # | Deliverable | For whom | Status |
 |---|------------|:--------:|--------|
-| 1 | PRD document | UX + ARCH + DEV + TEST | ☐ |
-| 2 | User stories with AC | UX (for flows) + TEST (for test plan) | ☐ |
-| 3 | NFR table | ARCH (for system design) | ☐ |
-| 4 | Risks & open questions | All | ☐ |
-| 5 | Backlog (`$pm-backlog`) | DEV + Conductor | ☐ |
+| 1 | PRD + user stories + AC | UX + ARCH + DEV + TEST | ☐ |
+| 2 | NFR table | ARCH | ☐ |
+| 3 | Risks & open questions | All | ☐ |
+| 4 | Backlog (`$pm-backlog`) | DEV + Conductor | ☐ |
 
 ---
 
 ## 6. Example: User Story
 
 ```markdown
-### US-03: Configure Popup Design
+### US-03: Customize Notification Appearance
 
-**As a** Site Owner
-**I want to** customize popup colors, fonts, and template
-**So that** the popup matches my store's branding
+**As a** Workspace Admin
+**I want to** customize notification colors, icon, and label
+**So that** notifications match my team's visual identity
 
 **Priority:** P0
 
 #### Acceptance Criteria
 | # | Given | When | Then |
 |---|-------|------|------|
-| AC-01 | On Design tab | Change background color | Preview updates in real-time |
-| AC-02 | On Design tab | Select new template | Preview switches to selected template |
-| AC-03 | On Design tab | Click Save | Settings persist, toast "Settings saved" |
-| AC-04 | On Design tab | Enter invalid color | Validation error shown inline |
-| AC-05 | Server down | Click Save | Error toast, settings not lost |
+| AC-01 | On Appearance tab | Change accent color | Preview updates in real-time |
+| AC-02 | On Appearance tab | Enter invalid color hex | Validation error shown inline |
+| AC-03 | Server down | Click Save | Error toast, draft preserved locally |
 ```
 
 ---
@@ -177,34 +210,19 @@ What PM passes to downstream gates:
 ```markdown
 # PRD: <Product/Feature Name>
 
-**Version:** 1.0
-**Date:** YYYY-MM-DD
-**Author:** Product Manager Agent
+**Version:** 1.0  **Date:** YYYY-MM-DD  **Author:** Product Manager Agent
 **Status:** Draft / Review / Approved
 
-## 1. Vision & Goals
-<section 2, table 1>
-
-## 2. Scope
-<section 2, table 2>
-
-## 3. Roles & Permissions
-<section 2, table 3>
-
-## 4. User Stories
-<section 3 format × N stories>
-
-## 5. Non-Functional Requirements
-<section 2, table 6>
-
-## 6. Risks & Open Questions
-<section 2, table 7>
-
-## Quality Checklist
-<section 4 — all checked>
-
-## Handoff
-<section 5 — all checked>
+## 1. Vision & Goals       — §2.1 table
+## 2. Personas             — §2.2 card × N
+## 3. User Journeys        — names + covering US-XX
+## 4. Scope                — §2.4 table
+## 5. Roles & Permissions  — §2.5 table
+## 6. User Stories         — §3 format × N
+## 7. NFR                  — §2.7 table
+## 8. Risks & Open Questions — §2.8 table
+## Quality Checklist       — §4 all checked
+## Handoff                 — §5 all checked
 ```
 
 ---
@@ -212,4 +230,5 @@ What PM passes to downstream gates:
 ## See also
 - `$pm-interview` — interview/discovery (input)
 - `$pm-backlog` — decompose PRD into backlog
-- `$ux-discovery` → `$ux-spec` — UX design (uses PRD)
+- `$ux-discovery` → `$ux-spec` — UX design (uses PRD + journey)
+- `$a11y-baseline` — accessibility baseline for NFR

package/domains/development/locales/en/.agents/skills/pm-prd/agents/kimi.yaml

@@ -1,14 +1,14 @@
-name: "pm-prd"
-display_name: "PRD (Product Requirements Document)"
-description: "Generate a PRD — Vision, MVP, out-of-scope, user stories, acceptance criteria, NFR, risks, and open questions. The result must be verifiable."
-default_prompt: "Use $pm-prd when the task matches the \"PRD (Product Requirements Document)\" skill."
-triggers:
-  - "pm-prd"
-  - "pm prd"
-  - "PRD (Product Requirements Document)"
-  - "Generate a PRD — Vision, MVP, out-of-scope, user stories, acceptance criteria, NFR, risks, and open questions"
-capabilities:
-  - "pm"
-  - "prd"
-tools: []
-implicit_invocation: true
+name: "pm-prd"
+display_name: "PRD (Product Requirements Document)"
+description: "Generate a PRD — Vision, MVP, out-of-scope, user stories, acceptance criteria, NFR, risks, and open questions. The result must be verifiable."
+default_prompt: "Use $pm-prd when the task matches the \"PRD (Product Requirements Document)\" skill."
+triggers:
+  - "pm-prd"
+  - "pm prd"
+  - "PRD (Product Requirements Document)"
+  - "Generate a PRD — Vision, MVP, out-of-scope, user stories, acceptance criteria, NFR, risks, and open questions"
+capabilities:
+  - "pm"
+  - "prd"
+tools: []
+implicit_invocation: true