code-ai-installer 1.2.0 → 1.3.0

package/locales/en/.agents/performance_review_baseline/agents/gemini.json

@@ -1,12 +1,13 @@
 {
   "name": "performance_review_baseline",
-  "display_name": "Basic perf review",
-  "description": "Basic perf review: N+1, pagination, batches, extra requests, architectural cache, heavy operations in the request-path.",
-  "default_prompt": "Use $performance_review_baseline when the task matches the \"Basic perf review\" skill.",
+  "display_name": "N+1 indicators",
+  "description": "Baseline perf-review — N+1, pagination, batches, extra requests, cache by architecture, heavy operations in the request path.",
+  "default_prompt": "Use $performance_review_baseline when the task matches the \"N+1 indicators\" skill.",
   "triggers": [
     "performance_review_baseline",
     "performance review baseline",
-    "Basic perf review"
+    "N+1 indicators",
+    "Baseline perf-review — N+1, pagination, batches, extra requests, cache by architecture, heavy operations in the request path"
   ],
   "capabilities": [
     "performance",

package/locales/en/.agents/performance_review_baseline/agents/openai.yaml

@@ -1,7 +1,7 @@
 interface:
-  display_name: "Basic perf review"
-  short_description: "Basic perf review: N+1, pagination, batches, extra requests, architectural cache, heavy operati…"
-  default_prompt: "Use $performance_review_baseline when the task matches the \"Basic perf review\" skill."
+  display_name: "N+1 indicators"
+  short_description: "Baseline perf-review — N+1, pagination, batches, extra requests, cache by architecture, heavy o…"
+  default_prompt: "Use $performance_review_baseline when the task matches the \"N+1 indicators\" skill."
 dependencies:
   tools: []
 policy:

package/locales/en/.agents/performance_review_baseline/agents/qwen.json

@@ -1,12 +1,13 @@
 {
   "name": "performance_review_baseline",
-  "display_name": "Basic perf review",
-  "description": "Basic perf review: N+1, pagination, batches, extra requests, architectural cache, heavy operations in the request-path.",
-  "default_prompt": "Use $performance_review_baseline when the task matches the \"Basic perf review\" skill.",
+  "display_name": "N+1 indicators",
+  "description": "Baseline perf-review — N+1, pagination, batches, extra requests, cache by architecture, heavy operations in the request path.",
+  "default_prompt": "Use $performance_review_baseline when the task matches the \"N+1 indicators\" skill.",
   "triggers": [
     "performance_review_baseline",
     "performance review baseline",
-    "Basic perf review"
+    "N+1 indicators",
+    "Baseline perf-review — N+1, pagination, batches, extra requests, cache by architecture, heavy operations in the request path"
   ],
   "capabilities": [
     "performance",

package/locales/en/.agents/performance_review_baseline/agents/skill.yaml

@@ -1,12 +1,13 @@
 version: 1
 name: "performance_review_baseline"
-display_name: "Basic perf review"
-description: "Basic perf review: N+1, pagination, batches, extra requests, architectural cache, heavy operations in the request-path."
-default_prompt: "Use $performance_review_baseline when the task matches the \"Basic perf review\" skill."
+display_name: "N+1 indicators"
+description: "Baseline perf-review — N+1, pagination, batches, extra requests, cache by architecture, heavy operations in the request path."
+default_prompt: "Use $performance_review_baseline when the task matches the \"N+1 indicators\" skill."
 triggers:
   - "performance_review_baseline"
   - "performance review baseline"
-  - "Basic perf review"
+  - "N+1 indicators"
+  - "Baseline perf-review — N+1, pagination, batches, extra requests, cache by architecture, heavy operations in the request path"
 capabilities:
   - "performance"
   - "review"

package/locales/en/.agents/pm_backlog/SKILL.md

@@ -1,32 +1,250 @@
 ---
 name: pm_backlog
-description: Decomposition of PRD into the primary backlog: epics, features and tasks with priorities, dependencies and iteration proposal (MVP → v1).
+description: Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1).
 ---
 
 # Skill: Backlog (epics/features/tasks)
 
-## Goal
-Turn PRD into planned work: what to do and in what order.
+Turn the PRD into plannable work.
 
-## Exit
-Backlog format:
+**Sections:**
+1. [Workflow](#1-workflow)
+2. [Hierarchy](#2-hierarchy)
+3. [Task Card Template](#3-task-card)
+4. [Decomposition Rules](#4-rules)
+5. [Iteration Planning](#5-iterations)
+6. [Example: Smart Cart Rescue](#6-example)
+7. [Output Template](#7-output)
 
-### Epics (E-xx)
-- E-01: ...
-  - Feature (F-xx): ...
-    - Task (T-xx): ... (short, verifiable)
+---
+
+## 1. Workflow
+
+```
+1. Input: PRD (from $pm_prd) — user stories + AC
+2. Group stories into Epics (business domain areas)
+3. Break each story into Features (deliverable chunks)
+4. Break each feature into Tasks (implementable units)
+5. Assign priorities (P0/P1/P2)
+6. Map dependencies
+7. Propose iterations (section 5)
+8. Submit for review → $board
+```
+
+---
+
+## 2. Hierarchy
+
+```
+Epic (E-xx) — business domain area
+├── Feature (F-xx) — deliverable user-facing chunk
+│   ├── Task (T-xx) — implementable unit (1-4h of work)
+│   ├── Task (T-xx)
+│   └── Task (T-xx)
+├── Feature (F-xx)
+│   └── ...
+└── Spike (SP-xx) — research / time-boxed exploration
+```
+
+### Level definitions
+
+| Level | What | Size | Example |
+|-------|------|------|---------|
+| **Epic** | Business domain area | 1-3 weeks | E-01: Settings Management |
+| **Feature** | User-facing deliverable | 2-5 days | F-01: Settings CRUD API |
+| **Task** | Implementable unit | 1-4 hours | T-01: Create settings schema |
+| **Spike** | Research / exploration | Time-boxed (2-8h) | SP-01: Evaluate Wix Webhooks |
+
+---
+
+## 3. Task Card Template
+
+```markdown
+### T-XX: <Title>
+
+**Feature:** F-XX
+**Owner:** DEV / UX / ARCH / TEST
+**Priority:** P0 / P1 / P2
+**Estimate:** XS (1h) / S (2h) / M (4h) / L (8h) / XL (16h)
+
+**Description:**
+<What needs to be done, concretely>
+
+**Acceptance Criteria:**
+- [ ] <Measurable, checkable criterion>
+- [ ] <Measurable, checkable criterion>
+
+**Dependencies:**
+- Requires: T-XX (schema), F-XX (API)
+- Blocks: T-XX (UI integration)
+
+**DoD (Definition of Done):**
+- [ ] Code complete
+- [ ] Unit tests pass
+- [ ] Code review passed
+- [ ] No P0 bugs
+```
+
+### Estimation guide
+
+| Size | Hours | Complexity | Example |
+|------|:-----:|-----------|---------|
+| **XS** | ~1h | Trivial change | Add field to schema |
+| **S** | ~2h | Simple, well-understood | CRUD endpoint |
+| **M** | ~4h | Moderate, some decisions | Form with validation |
+| **L** | ~8h | Complex, multiple parts | Full settings page |
+| **XL** | ~16h | Large, risky → split if possible | Template system |
+
+---
+
+## 4. Decomposition Rules
+
+| Rule | Explanation |
+|------|------------|
+| **Vertical slices** | End-to-end features (API + UI + tests), not layer-by-layer |
+| **MVP first** | P0 = product doesn't work without it |
+| **One task = one result** | Each task produces a checkable artifact |
+| **Max 4h per task** | If larger → split into subtasks |
+| **Spike for unknowns** | Uncertainty → create time-boxed Spike task |
+| **Dependencies explicit** | State what's required before and what this blocks |
+| **Cross-cutting last** | Polish, a11y, perf → P1/P2 after core works |
+
+### Priority rules
+
+| Priority | Criteria | % of MVP |
+|----------|---------|:--------:|
+| 🔴 **P0** | Core functionality, must ship | 60-70% |
+| 🟠 **P1** | Important UX, error handling, polish | 20-30% |
+| 🟡 **P2** | Nice-to-have, future iteration | 5-10% |
+
+---
+
+## 5. Iteration Planning
 
-For each Feature:
-- Priority (P0/P1/P2)
-- Dependencies (for example: UX Spec, architecture, integrations)
-- Risk/ambiguity (if any)
+### Iteration format
 
-## Decomposition rules
-- Make “vertical” features (end-to-end), and not layer by layer.
-- MVP first: P0 is only something without which the product does not work.
-- If there is uncertainty, create a Spike task (time-box) as a separate item.
+```markdown
+### Iteration N: <Name> (<duration>)
+
+**Goal:** <One-sentence goal>
+**Scope:** <Features/tasks included>
+**Entry criteria:** <What must be ready>
+**Exit criteria:** <What must be done>
+
+| Task | Priority | Estimate | Owner | Status |
+|------|:--------:|:--------:|:-----:|:------:|
+| T-01 | P0 | S | DEV | ☐ |
+| T-02 | P0 | M | DEV | ☐ |
+```
+
+### Typical MVP breakdown
+
+| Iteration | Focus | Content |
+|-----------|-------|---------|
+| **Iter 1** | Foundation | Schema, API, basic CRUD, install flow |
+| **Iter 2** | Core UI | Dashboard, settings, config panel |
+| **Iter 3** | Integration | Widget, live preview, templates |
+| **Iter 4** | Hardening | Error handling, edge cases, testing |
+
+---
+
+## 6. Example: Smart Cart Rescue
+
+```markdown
+## E-01: Settings Management
+### F-01: Settings CRUD API (P0)
+- T-01: Create Settings Mongoose schema — S — DEV
+- T-02: POST /settings endpoint (create on install) — S — DEV
+- T-03: PUT /settings/:id endpoint (update) — S — DEV
+- T-04: GET /settings/:id endpoint (read) — XS — DEV
+- T-05: Settings validation (Zod schema) — S — DEV
+
+### F-02: Settings Dashboard UI (P0)
+- T-06: Settings page layout (2-column: config + preview) — M — DEV
+- T-07: General tab (title, subtitle, CTA fields) — M — DEV
+- T-08: Design tab (color pickers, font select) — L — DEV
+- T-09: Timer tab (enable switch, min/sec inputs) — S — DEV
+- T-10: Save flow (button → API → toast) — S — DEV
+
+## E-02: Coupon Management
+### F-03: Coupon CRUD API (P0)
+- T-11: Coupon Mongoose schema — S — DEV
+- T-12: POST /coupons endpoint — S — DEV
+- T-13: GET /coupons (list) endpoint — S — DEV
+- T-14: DELETE /coupons/:id endpoint — XS — DEV
+
+### F-04: Coupon Dashboard UI (P0)
+- T-15: Coupons list (table + empty state) — M — DEV
+- T-16: Create coupon form (modal) — M — DEV
+- T-17: Delete coupon (confirm → delete → toast) — S — DEV
+
+## E-03: Widget (Public Popup)
+### F-05: Widget Rendering (P0)
+- T-18: Public widget endpoint (GET /widget/:id) — S — DEV
+- T-19: Glassmorphism template renderer — L — DEV
+- T-20: Token replacement engine (title, subtitle, colors) — M — DEV
+- T-21: Timer countdown logic — M — DEV
+
+### SP-01: Evaluate Wix Webhooks (P0, time-box: 4h)
+- Research: How to handle install/uninstall webhooks
+- Output: ADR with chosen approach
+```
+
+---
+
+## 7. Output Template
+
+```markdown
+# Product Backlog: <Project Name>
+
+**PRD:** <reference>
+**Date:** YYYY-MM-DD
+**Author:** Product Manager Agent
+
+## Summary
+| Metric | Count |
+|--------|:-----:|
+| Epics | X |
+| Features | Y |
+| Tasks | Z |
+| Spikes | W |
+| P0 tasks | A |
+| P1 tasks | B |
+| P2 tasks | C |
+
+## Backlog
+
+### E-01: <Epic Name>
+#### F-01: <Feature Name> (P0)
+| Task | Priority | Estimate | Owner | Deps | Status |
+|------|:--------:|:--------:|:-----:|------|:------:|
+| T-01: ... | P0 | S | DEV | — | ☐ |
+| T-02: ... | P0 | M | DEV | T-01 | ☐ |
+
+#### F-02: <Feature Name> (P0)
+...
+
+### E-02: <Epic Name>
+...
+
+## Iterations
+<section 5 format>
+
+## Dependencies Graph
+<list critical path dependencies>
+
+## Spikes
+| ID | Question | Time box | Output | Status |
+|----|---------|:--------:|--------|:------:|
+| SP-01 | ... | 4h | ADR | ☐ |
+
+## Next Step
+→ Transfer to $board for tracking
+```
+
+---
 
-## Suggesting iterations
-- Iteration 1 (MVP slice 1): ...
-- Iteration 2 (MVP slice 2): ...
-- Iteration 3 (hardening / v1): ...
+## See also
+- `$pm_prd` — PRD (input)
+- `$board` — project board (tracks execution)
+- `$handoff` — gate transitions

package/locales/en/.agents/pm_backlog/agents/claude.json

@@ -1,13 +1,13 @@
 {
   "name": "pm_backlog",
   "display_name": "Backlog (epics/features/tasks)",
-  "description": "Decomposition of PRD into the primary backlog: epics, features and tasks with priorities, dependencies and iteration proposal (MVP → v1).",
+  "description": "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1).",
   "default_prompt": "Use $pm_backlog when the task matches the \"Backlog (epics/features/tasks)\" skill.",
   "triggers": [
     "pm_backlog",
     "pm backlog",
     "Backlog (epics/features/tasks)",
-    "Decomposition of PRD into the primary backlog"
+    "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1)"
   ],
   "capabilities": [
     "pm",

package/locales/en/.agents/pm_backlog/agents/copilot.json

@@ -1,13 +1,13 @@
 {
   "name": "pm_backlog",
   "display_name": "Backlog (epics/features/tasks)",
-  "description": "Decomposition of PRD into the primary backlog: epics, features and tasks with priorities, dependencies and iteration proposal (MVP → v1).",
+  "description": "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1).",
   "default_prompt": "Use $pm_backlog when the task matches the \"Backlog (epics/features/tasks)\" skill.",
   "triggers": [
     "pm_backlog",
     "pm backlog",
     "Backlog (epics/features/tasks)",
-    "Decomposition of PRD into the primary backlog"
+    "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1)"
   ],
   "capabilities": [
     "pm",

package/locales/en/.agents/pm_backlog/agents/gemini.json

@@ -1,13 +1,13 @@
 {
   "name": "pm_backlog",
   "display_name": "Backlog (epics/features/tasks)",
-  "description": "Decomposition of PRD into the primary backlog: epics, features and tasks with priorities, dependencies and iteration proposal (MVP → v1).",
+  "description": "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1).",
   "default_prompt": "Use $pm_backlog when the task matches the \"Backlog (epics/features/tasks)\" skill.",
   "triggers": [
     "pm_backlog",
     "pm backlog",
     "Backlog (epics/features/tasks)",
-    "Decomposition of PRD into the primary backlog"
+    "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1)"
   ],
   "capabilities": [
     "pm",

package/locales/en/.agents/pm_backlog/agents/openai.yaml

@@ -1,6 +1,6 @@
 interface:
   display_name: "Backlog (epics/features/tasks)"
-  short_description: "Decomposition of PRD into the primary backlog: epics, features and tasks with priorities, depen…"
+  short_description: "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities,…"
   default_prompt: "Use $pm_backlog when the task matches the \"Backlog (epics/features/tasks)\" skill."
 dependencies:
   tools: []

package/locales/en/.agents/pm_backlog/agents/qwen.json

@@ -1,13 +1,13 @@
 {
   "name": "pm_backlog",
   "display_name": "Backlog (epics/features/tasks)",
-  "description": "Decomposition of PRD into the primary backlog: epics, features and tasks with priorities, dependencies and iteration proposal (MVP → v1).",
+  "description": "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1).",
   "default_prompt": "Use $pm_backlog when the task matches the \"Backlog (epics/features/tasks)\" skill.",
   "triggers": [
     "pm_backlog",
     "pm backlog",
     "Backlog (epics/features/tasks)",
-    "Decomposition of PRD into the primary backlog"
+    "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1)"
   ],
   "capabilities": [
     "pm",

package/locales/en/.agents/pm_backlog/agents/skill.yaml

@@ -1,13 +1,13 @@
 version: 1
 name: "pm_backlog"
 display_name: "Backlog (epics/features/tasks)"
-description: "Decomposition of PRD into the primary backlog: epics, features and tasks with priorities, dependencies and iteration proposal (MVP → v1)."
+description: "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1)."
 default_prompt: "Use $pm_backlog when the task matches the \"Backlog (epics/features/tasks)\" skill."
 triggers:
   - "pm_backlog"
   - "pm backlog"
   - "Backlog (epics/features/tasks)"
-  - "Decomposition of PRD into the primary backlog"
+  - "Decomposition of the PRD into an initial backlog ? epics, features, and tasks with priorities, dependencies, and proposed iterations (MVP -> v1)"
 capabilities:
   - "pm"
   - "backlog"

package/locales/en/.agents/pm_interview/SKILL.md

@@ -1,56 +1,197 @@
 ---
 name: pm_interview
-description: Structured interview/documentation analysis: collect goals, audience, MVP, limitations, integrations and success criteria so that you can write a PRD.
+description: Structured interview/documentation review — collect goals, audience, MVP, constraints, integrations, and success criteria, so that can was write PRD.
 ---
 
 #Skill: PM Interview/Discovery
 
-## Goal
-Quickly find out the minimum sufficient information for PRD and subsequent development.
+Collect the minimally sufficient information for a PRD.
 
-## When to use
-- At the beginning of the project
-- When the user gives scattered input
-- When direction/priorities change
+**Sections:**
+1. [Workflow](#1-workflow)
+2. [Question Bank](#2-questions)
+3. [Priority & Assumptions](#3-priority)
+4. [Example: Smart Cart Rescue](#4-example)
+5. [Output Template](#5-output)
 
-## Exit
-- Summary of introductory points (bullet points)
-- List of questions (3–12), sorted by importance
-- Explicit assumptions (if made)
+---
+
+## 1. Workflow
+
+```
+1. Read that, what already is:
+   ├── User brief / idea description
+   ├── Existing code / README
+   └── Previous documents (if is)
+
+2. Extract facts (what already known)
+
+3. Determine gaps (what needed clarify)
+   └── Use Question Bank (section 2)
+
+4. Prioritize questions:
+   ├── 🔴 Blocking — without the answer you cannot write the PRD
+   ├── 🟠 Important — affects on PRD, but can assume
+   └── 🟡 Nice-to-know — can postpone
+
+5. Ask questions (only blocking + important)
+   └── The rest → assumptions with marker ASSUMPTION
+
+6. Form Interview Summary (section 5)
+   └── Pass in → $pm_prd
+```
+
+### When Not needed interview
+
+| Situation | Action |
+|----------|---------|
+| The user provided a detailed brief with answers to everything | Skip → immediately $pm_prd |
+| Iteration over existing PRD | Minimum interview (only new questions) |
+| Bugfix / patch | Not needed |
+
+---
+
+## 2. Question Bank
 
-## Skeleton interview (ask only relevant ones)
 ### A) Product and users
-- Who are the target users?
-- What is the main pain/task?
-- How does the user solve this now?
-- What are the user roles and differences in rights?
+
+| # | Question | Why | Priority |
+|---|--------|-------|:--------:|
+| Q-01 | Who goal users? | Defines user stories and UX | 🔴 |
+| Q-02 | What is the main pain point/task? | Core value proposition | 🔴 |
+| Q-03 | How does the user solve this now? | Competitive context | 🟠 |
+| Q-04 | Which roles and permission differences are there? | Auth/ACL scope | 🔴 |
 
 ### B) MVP and boundaries
-- What is required in an MVP (3–7 points)?
-- What exactly is NOT included (out-of-scope)?
-- What are the most common/critical scenarios?
+
+| # | Question | Why | Priority |
+|---|--------|-------|:--------:|
+| Q-05 | What is mandatory in the MVP (3-7 items)? | Scope control | 🔴 |
+| Q-06 | What definitely does not belong here (out of scope)? | Prevent scope creep | 🔴 |
+| Q-07 | Which scenarios most common/critical? | Priority of user flows | 🟠 |
 
 ### C) Success and metrics
-- How will we understand that the product is successful? (metrics/OKR)
-- Are there KPIs for speed, conversion, retention?
+
+| # | Question | Why | Priority |
+|---|--------|-------|:--------:|
+| Q-08 | How will we know that the product is successful? | Success criteria | 🟠 |
+| Q-09 | Are there KPIs (speed, conversion, retention)? | Measurable goals | 🟡 |
 
 ### D) Data and integrations
-- What data do we store? (profile, content, transactions)
-- Do you need integrations (payments, email/SMS, CRM, SSO, analytics)?
-- Are there external APIs and restrictions?
 
-### E) Non-functional requirements (NFR)
-- Security/compliance (PII, GDPR, SOC2, etc.)?
-- Performance (expected load)?
-- Availability (SLA)?
-- Localization/languages?
+| # | Question | Why | Priority |
+|---|--------|-------|:--------:|
+| Q-10 | Which data store? | Data model scope | 🔴 |
+| Q-11 | Needed whether external integrations? | Architecture dependencies | 🔴 |
+| Q-12 | There is whether external API and constraints? | API constraints | 🟠 |
+
+### E) NFR (non-functional)
+
+| # | Question | Why | Priority |
+|---|--------|-------|:--------:|
+| Q-13 | There is whether requirements by security/compliance? | Security scope | 🟠 |
+| Q-14 | Expected load? | Scaling strategy | 🟡 |
+| Q-15 | Localization / languages? | i18n scope | 🟡 |
 
 ### F) Technologies and deployment
-- Preferred stack? If not, offer options.
-- Where will we deploy? (Vercel/Docker/AWS/…)
-- Do you need an admin panel?
-
-## Question minimization rule
-- If you can move forward with a safe assumption, make an assumption and mark it.
-- If the answer is critical for architecture/UX, ask a question.
-- If the question can be postponed until PRD, add it to the open questions section.
+
+| # | Question | Why | Priority |
+|---|--------|-------|:--------:|
+| Q-16 | Preferred stack? | Tech decisions | 🟠 |
+| Q-17 | Where are we deploying? | Infrastructure | 🟠 |
+| Q-18 | Needed whether admin panel? | Additional scope | 🟡 |
+
+---
+
+## 3. Priority & Assumptions
+
+### Question minimization rule
+
+| Situation | Action |
+|----------|---------|
+| The response is critical for architecture/UX | 🔴 Mandatory ask |
+| You can move forward with a safe assumption | 🟠 Assume + mark ASSUMPTION |
+| Can postpone to PRD review | 🟡 Add in Open Questions |
+
+### Assumption format
+
+```markdown
+**ASSUMPTION-XX:** <Statement>
+- Basis: <Why this is safe to assume>
+- Risk: Low / Medium / High
+- Confirm to: <milestone>
+```
+
+---
+
+## 4. Example: Smart Cart Rescue
+
+```markdown
+# Interview Summary: Smart Cart Rescue
+
+## Facts (from user brief)
+- Wix App — andbandoned cart recovery via popup
+- Dashboard for configuring popup widgets
+- Multiple design templates (Glassmorphism, Neo-Brutalism, Minimal)
+- Coupon management (CRUD)
+- Timer countdown for urgency
+
+## Questions Asked
+| # | Question | Answer | Status |
+|---|----------|--------|:------:|
+| Q-01 | Target users? | Wix store owners | ✅ |
+| Q-04 | Roles? | Single role: Site Owner | ✅ |
+| Q-05 | MVP features? | Settings, Coupons, Widget, Install | ✅ |
+| Q-06 | Out of scope? | Analytics, A/B testing, multi-language | ✅ |
+| Q-11 | Integrations? | Wix Platform (OAuth, Webhooks) | ✅ |
+
+## Assumptions
+- ASSUMPTION-01: Desktop-only (Wix Editor = desktop) → Low risk
+- ASSUMPTION-02: English only for MVP → Low risk
+- ASSUMPTION-03: No payment integration (free app) → Low risk
+```
+
+---
+
+## 5. Output Template
+
+```markdown
+# PM Interview Summary
+
+**Date:** YYYY-MM-DD
+**Interviewer:** Product Manager Agent
+**Source:** <user brief / existing docs / conversation>
+
+## Facts (confirmed)
+| # | Fact | Source |
+|---|------|--------|
+| F-01 | ... | User brief |
+| F-02 | ... | README.md |
+
+## Questions & Answers
+| # | Question | Priority | Answer | Status |
+|---|----------|:--------:|--------|:------:|
+| Q-01 | ... | 🔴 | ... | ✅ Answered |
+| Q-05 | ... | 🔴 | ... | ✅ Answered |
+| Q-09 | ... | 🟡 | — | ASSUMED |
+
+## Assumptions
+| ID | Assumption | Risk | Confirm by |
+|----|-----------|:----:|-----------|
+| ASSUMPTION-01 | ... | Low | MVP review |
+
+## Open Questions (deferred)
+| # | Question | Why deferred | Address at |
+|---|----------|-------------|-----------|
+| Q-14 | Expected load? | Not critical for MVP | Pre-launch |
+
+## Next Step
+→ Proceed to $pm_prd
+```
+
+---
+
+## See also
+- `$pm_prd` — PRD (output of interview)
+- `$pm_backlog` — Backlog decomposition
+- `$ux_discovery` — UX-specific discovery