@hienlh/ppm 0.9.81 → 0.9.83

package/.opencode/commands/ckm-funnel.md

@@ -1,77 +0,0 @@
----
-description: "💡💡 Funnel design and optimization - Args: ['action] [type']"
----
-
-Design and optimize marketing funnels.
-
-<args>$ARGUMENTS</args>
-
-## Actions
-- `design [type]` - Design new funnel
-- `analyze` - Analyze existing funnel
-- `optimize` - Optimization recommendations
-
-## Funnel Types
-- `lead-magnet` - Lead capture funnel
-- `webinar` - Webinar registration funnel
-- `product-launch` - Product launch sequence
-- `evergreen` - Evergreen sales funnel
-- `tripwire` - Low-ticket tripwire funnel
-
-## Workflow
-
-1. **Parse Arguments**
-   - Extract action (design/analyze/optimize)
-   - Extract funnel type (for design)
-
-2. **Design Workflow**
-   - Use `funnel-architect` agent for funnel architecture
-   - Activate `campaign-management` skill
-   - Design stages:
-     - Traffic source
-     - Landing page
-     - Lead capture
-     - Nurture sequence
-     - Sales page
-     - Checkout
-     - Follow-up
-   - Define metrics per stage
-
-3. **Analyze Workflow**
-   - Use `analytics-analyst` agent for funnel metrics
-   - Calculate conversion rates per stage
-   - Identify drop-off points
-   - Benchmark against industry standards
-
-4. **Optimize Workflow**
-   - Use `funnel-architect` for recommendations
-   - Use `sale-enabler` for conversion tactics
-   - Priority-ranked improvements
-   - A/B test suggestions
-
-5. **Output**
-   - Funnel designs → `assets/funnels/designs/{date}-{slug}-funnel.md`
-   - Analysis reports → `assets/funnels/audits/{date}-{funnel}-audit.md`
-
-## Agents Used
-- `funnel-architect` - Funnel design
-- `sale-enabler` - Conversion optimization
-- `analytics-analyst` - Performance analysis
-
-## Skills Used
-- `campaign-management` - Funnel frameworks
-- `analytics` - Metrics tracking
-- `assets-organizing` - Standardized output paths
-
-## Output
-- Funnel designs → `assets/funnels/designs/{date}-{slug}-funnel.md`
-- Funnel audits → `assets/funnels/audits/{date}-{funnel}-audit.md`
-- A/B tests → `assets/funnels/tests/{date}-{test-name}.md`
-
-## Examples
-```
-/funnel design lead-magnet
-/funnel design webinar
-/funnel analyze
-/funnel optimize
-```

package/.opencode/commands/ckm-hub.md

@@ -1,50 +0,0 @@
----
-description: "Open Content Hub + Marketing Dashboard - Args: ['--stop|--scan']"
----
-
-💡
-Activate `content-hub` skill and start Marketing Dashboard.
-
-## Usage
-
-```bash
-/write:hub           # Start all services
-/write:hub --scan    # Rescan assets folder
-/write:hub --stop    # Stop all servers
-```
-
-## Workflow
-
-1. **Start servers**: Content Hub + Marketing Dashboard (API + Frontend)
-2. **Auto-open**: Content Hub at http://localhost:3457/hub
-3. **Access dashboard**: Marketing Dashboard at http://localhost:5173
-
-## Services Started
-
-| Service | URL | Description |
-|---------|-----|-------------|
-| Content Hub | http://localhost:3457/hub | Asset gallery with AI editor |
-| Dashboard UI | http://localhost:5173 | Marketing dashboard (Vue) |
-| Dashboard API | http://localhost:3457/api/ | REST API (Hono + SQLite) |
-
-## Execution
-
-```bash
-bash .opencode/skills/content-hub/scripts/start-all.sh $ARGUMENTS
-```
-
-Report all URLs when servers start.
-
-## Features
-
-**Content Hub:**
-- Visual asset gallery with thumbnails
-- AI-powered content editor
-- Brand context sidebar
-- Filter/search by type
-
-**Marketing Dashboard:**
-- Campaign management
-- Content library
-- Asset linking
-- Automation panel

package/.opencode/commands/ckm-init.md

@@ -1,214 +0,0 @@
----
-description: "💡💡💡💡 Initialize marketing project - Args: ['prompt']"
----
-
-Initialize a new marketing project by gathering comprehensive client information through an agency-style marketing brief interview.
-
-## Your Mission
-
-Conduct a structured interview to gather all essential marketing information, then generate foundational project documentation.
-
-<user-input>$ARGUMENTS</user-input>
-
-**IMPORTANT**:
-- Do not skip any phase or section.
-- Analyze the skills catalog and activate the skills that are needed for the task during the process.
-- Ensure token efficiency while maintaining high quality.
-- Sacrifice grammar for the sake of concision when writing reports.
-- In reports, list any unresolved questions at the end, if any.
-
-## Phase 0: Git Setup
-
-1. **Check Git Status**
-   - Run `git status` to detect if git is initialized
-   - If not a git repo, ask user: "Initialize git repository?"
-
-2. **If User Confirms Git Init**
-   - Run `git init`
-   - Ask: "Create remote repository?" (GitHub/GitLab/etc.)
-   - If yes, gather repo name and create via `gh repo create`
-
-3. **If Already Initialized**
-   - Show current remote (if any)
-   - Proceed to Phase 1
-
-## Phase 1: Quick Evaluation
-
-**Main agent spawns parallel researchers** to evaluate current project situation:
-
-### 1.1 Parallel Research (spawn 3-4 `researcher` agents simultaneously)
-
-| Agent | Focus Area | Data Sources |
-|-------|------------|--------------|
-| Researcher 1 | Product/Service Analysis | `README.md`, `CLAUDE.md`, `package.json`, codebase |
-| Researcher 2 | Existing Marketing Assets | `docs/*.md`, `assets/`, marketing collaterals |
-| Researcher 3 | Digital Presence | Website URL (if found), social links, SEO status |
-| Researcher 4 | Competitive Landscape | Industry context, market positioning |
-
-### 1.2 If Docs Exist in `docs/`
-
-1. **Read all existing docs**:
-   - `docs/project-overview-pdr.md`
-   - `docs/marketing-overview.md`
-   - `docs/brand-guidelines.md`
-   - `docs/design-guidelines.md`
-   - Any other `docs/*.md` files
-
-2. **Compile findings summary** with key points:
-   - Product/service description
-   - Target audience (if defined)
-   - Brand identity (if defined)
-   - Marketing objectives (if defined)
-   - Existing campaigns/assets
-
-3. **Verify with user via `AskUserQuestion`**:
-   - Display compiled summary
-   - Ask: "Is this information still accurate?"
-   - Options: "Yes, proceed" / "Needs updates" / "Start fresh"
-   - If "Needs updates": ask which sections need revision
-
-### 1.3 If No Docs Exist
-
-- Note: "No existing docs found"
-- Proceed directly to Phase 2
-
-## Phase 2: Marketing Brief Interview
-
-Use `AskUserQuestion` tool for each section.
-
-### Section A: Basic Information
-- Company/Product name and tagline
-- Industry/Niche
-- Brief introduction (2-3 sentences)
-- Website URL (if exists): ask for URL if not found, read and analyze website to extract information
-
-### Section B: Products/Services
-- What are your main products/services?
-- Key USPs and differentiators
-- Price range/Pricing model
-- Top 3 product highlights
-
-### Section C: Objectives (multi-select)
-- Brand awareness
-- Lead generation
-- Sales conversion
-- Customer retention
-- Market expansion
-- Product launch
-- Other
-
-### Section D: Target Audience
-- **Geographic**: Countries/Regions
-- **Demographic**: Age, gender, income level
-- **Psychographic**: Interests, values, lifestyle
-- **B2B specifics**: Company size, industry, decision-maker roles
-
-### Section E: Competitive Landscape
-- Top 3 competitors (names/URLs)
-- Your competitive advantage
-- Market positioning goal
-
-### Section F: Brand Assets
-- Logo available? (Y/N, format)
-- Brand colors defined?
-- Brand fonts specified?
-- Existing brand guidelines doc?
-- Marketing collaterals (name cards, catalogue, etc.)?
-
-### Section G: Design Guidelines
-Ask if they want to extract from:
-- Website (provide URL)
-- Videos (provide links)
-- Existing documents (provide paths)
-- Manual input
-
-### Section H: Social Presence
-- Active social platforms (multi-select)
-- Social profile URLs
-- Current follower counts (approximate)
-
-### Section I: Timeline & Budget
-- Expected launch/go-live date
-- Monthly marketing budget range
-- Priority channels for budget allocation
-
-## Phase 3: Documentation Generation
-
-**IMPORANT**: Create/update following documents even docs exists in Step 1.2
-
-After interview completion, spawn `docs-manager` agent with gathered data to:
-
-1. **Update `CLAUDE.md`**
-   - Add marketing context section
-   - Update role description
-
-2. **Create/Update `README.md`**
-   - Project overview
-   - Quick start for marketing workflows
-
-3. **Generate `docs/project-overview-pdr.md`**
-   - Full product development requirements
-   - Marketing objectives and KPIs
-   - Target audience profiles
-   - Brand guidelines summary
-
-4. **Generate `docs/marketing-overview.md`**
-   - Marketing strategy summary
-   - Channel priorities
-   - Campaign roadmap outline
-
-5. **Generate `docs/project-roadmap.md`**
-   - Marketing milestones
-   - Campaign timeline
-   - Resource allocation
-
-## Phase 3.5: Commit Changes
-
-Ask user: "Commit generated documentation?"
-- If yes, execute `/git:cm` command to stage and commit
-- Suggested commit message: "docs: initialize marketing project documentation"
-
-## Phase 4: Next Steps
-
-After documentation generated:
-
-1. **Analyze Available Commands**
-   - Run `python .opencode/scripts/generate_catalogs.py --commands`
-   - Identify relevant next steps
-
-2. **Suggest Next Actions** (pick 3-5 most relevant):
-   - `/persona create` - Create customer personas
-   - `/seo audit` - Audit website SEO
-   - `/funnel design` - Design marketing funnel
-   - `/campaign create` - Plan first campaign
-   - `/social schedule` - Create content calendar
-   - `/write:blog` - Start blog content
-   - `/competitor` - Deep competitor analysis
-   - None - finish the process.
-
-## Agents Used
-- `researcher` (x4 parallel) - Quick evaluation of project situation
-- `docs-manager` - Documentation generation
-
-## Skills Used
-- `research` - Quick evaluation of project situation
-- `chrome-devtools` - Website extraction
-- `ai-multimodal` - Video/image analysis
-- `assets-organizing` - Standardized output paths and naming conventions
-
-## Commands Used
-- `/git:cm` - Stage and commit changes
-
-## Output
-**IMPORANT**: Create/update following documents even docs exists in Step 1.2
-- `CLAUDE.md` - Updated with marketing context
-- `README.md` - Project overview
-- `docs/project-overview-pdr.md` - Full PDR
-- `docs/marketing-overview.md` - Marketing strategy
-- `docs/project-roadmap.md` - Campaign timeline
-
-## Notes
-- Use progressive disclosure - don't overwhelm with all questions at once
-- Validate responses against existing docs if available
-- If user skips optional sections, note as "TBD" in docs
-- Keep interview conversational, not interrogative

package/.opencode/commands/ckm-journal.md

@@ -1,18 +0,0 @@
----
-description: "💡 Write some journal entries."
----
-
-## Writing Style Detection
-
-Before writing, check for a writing-styles directory:
-1. Check `docs/writing-styles/` — if exists, read all `.md` files inside
-2. Check `assets/writing-styles/` — if exists and step 1 not found, read all `.md` files inside
-3. If writing styles found → adopt tone, vocabulary, sentence structure, and formatting rules from those files
-4. If no writing-styles directory found → write freely in a natural, conversational tone
-
-## Journal Writing
-
-Use the `journal-writer` subagent to explore the memories and recent code changes, and write journal entries.
-- Concise, focused on important events, key changes, impacts, and decisions
-- Apply detected writing style (if any) to the journal voice
-- Keep journal entries in `docs/journal/` directory

package/.opencode/commands/ckm-kanban.md

@@ -1,65 +0,0 @@
----
-description: "Plans directory (default: ./plans)"
----
-
-Plans dashboard with progress tracking and timeline visualization.
-
-## Usage
-
-- `/kanban` - View dashboard for ./plans directory
-- `/kanban plans/` - View dashboard for specific directory
-- `/kanban --stop` - Stop running server
-
-## Features
-
-- Plan cards with progress bars
-- Phase status breakdown (completed, in-progress, pending)
-- Timeline/Gantt visualization
-- Activity heatmap
-- Issue and branch links
-
-## Execution
-
-```bash
-# Check if --stop flag
-if [[ "$ARGUMENTS" == *"--stop"* ]]; then
-  node .opencode/skills/plans-kanban/scripts/server.cjs --stop
-  exit 0
-fi
-
-# Determine plans directory
-INPUT_DIR="{{dir}}"
-PLANS_DIR="${INPUT_DIR:-./plans}"
-
-# Start kanban dashboard
-node .opencode/skills/plans-kanban/scripts/server.cjs \
-  --dir "$PLANS_DIR" \
-  --host 0.0.0.0 \
-  --open \
-  --background
-```
-
-Report the URL to the user. For remote access from other devices, use the `networkUrl` field from the JSON output.
-
-## Future Plans
-
-The `/kanban` command will evolve into **VibeKanban-inspired** AI agent orchestration:
-
-### Phase 1 (Current - MVP)
-- ✅ Task board with progress tracking
-- ✅ Visual representation of plans/tasks
-- ✅ Click to view plan details
-
-### Phase 2 (Worktree Integration)
-- Create tasks → spawn git worktrees
-- Assign agents to tasks
-- Track agent progress per worktree
-
-### Phase 3 (Full Orchestration)
-- Parallel agent execution monitoring
-- Code diff/review interface
-- PR creation workflow
-- Agent output streaming
-- Conflict detection
-
-Track progress: https://github.com/claudekit/claudekit-engineer/issues/189

package/.opencode/commands/ckm-persona.md

@@ -1,61 +0,0 @@
----
-description: "💡💡 Customer persona management - Args: ['action']"
----
-
-Create and manage customer personas.
-
-<action>$ARGUMENTS</action>
-
-## Actions
-- `create` - Create new persona
-- `analyze` - Analyze audience data
-- `update [name]` - Update existing persona
-- `list` - List all personas
-
-## Workflow
-
-1. **Parse Action** from `$ARGUMENTS`
-
-2. **Create Workflow**
-   - Use `lead-qualifier` agent for persona definition
-   - Gather via `AskUserQuestion`:
-     - Demographics (age, role, industry)
-     - Pain points and challenges
-     - Goals and motivations
-     - Buying behavior
-     - Preferred channels
-   - Use `researcher` agent for market validation
-   - Activate `content-marketing` skill
-
-3. **Analyze Workflow**
-   - Use `lead-qualifier` agent for audience analysis
-   - Use `analytics-analyst` for behavior data
-   - Identify segments and patterns
-   - Generate insights report
-
-4. **Update Workflow**
-   - Load existing persona
-   - Incorporate new data
-   - Validate changes
-
-5. **Output**
-   - ICP Profiles → `assets/leads/icp-profiles/{persona}.md`
-
-## Agents Used
-- `lead-qualifier` - Audience analysis
-- `researcher` - Market research
-
-## Skills Used
-- `content-marketing` - Persona frameworks
-- `assets-organizing` - Standardized output paths
-
-## Output
-- ICP Profiles → `assets/leads/icp-profiles/{persona}.md`
-
-## Examples
-```
-/persona create
-/persona analyze
-/persona update "Tech Startup Founder"
-/persona list
-```

package/.opencode/commands/ckm-plan-archive.md

@@ -1,56 +0,0 @@
----
-description: "Write journal entries and archive specific plans or all plans - Args: [path-to-plan] (default: all plans)"
----
-
-## Your mission
-Read and analyze the plans, then write journal entries and archive specific plans or all plans in the `plans` directory.
-
-## Plan Resolution
-1. If `$ARGUMENTS` provided → Use that path
-2. Else read all plans in the `plans` directory
-
-## Workflow
-
-### Step 1: Read Plan Files
-
-Read the plan directory:
-- `plan.md` - Overview and phases list
-- `phase-*.md` - 20 first lines of each phase file to understand the progress and status
-
-### Step 2: Summarize the plans and document them with `/journal` slash command
-Use `AskUserQuestion` tool to ask if user wants to document journal entries or not. 
-Skip this step if user selects "No".
-If user selects "Yes":
-- Analyze the information in previous steps and document them with `/journal` slash command.
-- Execute multiple `/journal` slash commands in parallel as `Task` tool to document all plans.
-- Journal entries should be concise and focused on the most important events, key changes, impacts, and decisions.
-- Keep journal entries in the `./docs/journal/` directory.
-
-### Step 3: Ask user to confirm the action before archiving these plans
-Use `AskUserQuestion` tool to ask if user wants to proceed with archiving these plans, select specific plans to archive or all completed plans only.
-Use `AskUserQuestion` tool to ask if user wants to delete permanently or move to the `./plans/archive` directory.
-
-### Step 4: Archive the plans
-Start archiving the plans based on the user's choice:
-- Move the plans to the `./plans/archive` directory.
-- Delete the plans permanently: `rm -rf ./plans/<plan-1> ./plans/<plan-2> ...`
-
-### Step 5: Ask if user wants to commit the changes
-Use `AskUserQuestion` tool to ask if user wants to commit the changes with these options:
-- Stage and commit the changes (Use `/git:cm` slash command)
-- Commit and push the changes (Use `/git:cp` slash command)
-- Nah, I'll do it later
-
-## Output
-After archiving the plans, provide summary:
-- Number of plans archived 
-- Number of plans deleted permanently
-- Table of plans that are archived or deleted (title, status, created date, LOC)
-- Table of journal entries that are created (title, status, created date, LOC)
-
-## Important Notes
-
-**IMPORTANT:** Only ask questions about genuine decision points - don't manufacture artificial choices.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-**IMPORTANT:** In the last summary report, list any unresolved questions at the end, if any.
-**IMPORTANT:** Ensure token efficiency while maintaining high quality.

package/.opencode/commands/ckm-plan-ci.md

@@ -1,32 +0,0 @@
----
-description: "Analyze Github Actions logs and provide a plan to fix the issues - Args: ['github-actions-url']"
----
-
-Activate `planning` skill.
-
-## Github Actions URL
- $ARGUMENTS
-
-Use the `planner` subagent to read the github actions logs, analyze and find the root causes of the issues, then provide a detailed plan for implementing the fixes.
-
-**Plan File Specification:**
-- Every `plan.md` MUST start with YAML frontmatter:
-  ```yaml
-  ---
-  title: "{Brief title}"
-  description: "{One sentence for card preview}"
-  status: pending
-  priority: P1
-  effort: {estimated fix time}
-  branch: {current git branch}
-  tags: [ci, bugfix]
-  created: {YYYY-MM-DD}
-  ---
-  ```
-
-**Output:**
-Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
-
-**IMPORTANT:** Ask the user for confirmation before implementing.
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.

package/.opencode/commands/ckm-plan-cro.md

@@ -1,68 +0,0 @@
----
-description: "Create a CRO plan for the given content - Args: ['issues']"
----
-
-You are an expert in conversion optimization. Analyze the content based on the given issues:
-<issues>$ARGUMENTS</issues>
-
-Activate `planning` skill.
-
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-## Conversion Optimization Framework
-
-1. Headline 4-U Formula: **Useful, Unique, Urgent, Ultra-specific** (80% won't read past this)
-2. Above-Fold Value Proposition: Customer problem focus, no company story, zero scroll required
-3. CTA First-Person Psychology: "Get MY Guide" vs "Get YOUR Guide" (90% more clicks)
-4. 5-Field Form Maximum: Every field kills conversions, progressive profiling for the rest
-5. Message Match Precision: Ad copy, landing page headline, broken promises = bounce
-6. Social Proof Near CTAs: Testimonials with faces/names, results, placed at decision points
-7. Cognitive Bias Stack: Loss aversion (fear), social proof (FOMO), anchoring (pricing)
-8. PAS Copy Framework: Problem > Agitate > Solve, emotion before logic
-9. Genuine Urgency Only: Real deadlines, actual limits, fake timers destroy trust forever
-10. Price Anchoring Display: Show expensive option first, make real price feel like relief
-11. Trust Signal Clustering: Security badges, guarantees, policies all visible together
-12. Visual Hierarchy F-Pattern: Eyes scan F-shape, put conversions in the path
-13. Lead Magnet Hierarchy: Templates > Checklists > Guides (instant > delayed gratification)
-14. Objection Preemption: Address top 3 concerns before they think them, FAQ near CTA
-15. Mobile Thumb Zone: CTAs where thumbs naturally rest, not stretching required
-16. One-Variable Testing: Change one thing, measure impact, compound wins over time
-17. Post-Conversion Momentum: Thank you page sells next step while excitement peaks
-18. Cart Recovery Sequence: Email in 1 hour, retarget in 4 hours, incentive at 24 hours
-19. Reading Level Grade 6: Smart people prefer simple, 11-word sentences, short paragraphs
-20. TOFU/MOFU/BOFU Logic: Awareness content ≠ decision content, match intent precisely
-21. White Space = Focus: Empty space makes CTAs impossible to miss, crowded = confused
-22. Benefit-First Language: Features tell, benefits sell, transformations compel
-23. Micro-Commitment Ladder: Small yes leads to big yes, start with email only
-24. Performance Tracking Stack: Heatmaps show problems, recordings show why, events show what
-25. Weekly Optimization Ritual: Review metrics Monday, test Tuesday, iterate or scale
-
-## Workflow
-
-- If the user provides a screenshots or videos, use `ai-multimodal` skill to describe as detailed as possible the issue, make sure copywriter can fully understand the issue easily based on the description.
-- If the user provides a URL, use `web_fetch` tool to fetch the content of the URL and analyze the current issues.
-- You can use screenshot capture tools along with `ai-multimodal` skill to capture screenshots of the exact parent container and analyze the current issues with the appropriate Gemini analysis skills (`ai-multimodal`, `gemini-video-understanding`, or `gemini-document-processing`).
-- Use `/scout:ext` (preferred) or `/scout` (fallback) slash command to search the codebase for files needed to complete the task
-- Use `planner` agent to create a comprehensive CRO plan following the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Every `plan.md` MUST start with YAML frontmatter:
-    ```yaml
-    ---
-    title: "{Brief title}"
-    description: "{One sentence for card preview}"
-    status: pending
-    priority: P2
-    effort: {sum of phases, e.g., 4h}
-    branch: {current git branch}
-    tags: [cro, conversion]
-    created: {YYYY-MM-DD}
-    ---
-    ```
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
-  - Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-- Do not start implementing the CRO plan yet, wait for the user to approve the plan first.
-
-**IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-**IMPORTANT:** In reports, list any unresolved questions at the end, if any.