@hienlh/ppm 0.9.81 → 0.9.82

package/.opencode/commands/ckm-email-sequence.md

@@ -1,170 +0,0 @@
----
-description: "Generate complete email drip sequence with copy - Args: <type> \"[context]\""
----
-
-# Email Sequence Generator
-
-Generate a complete email sequence with full copy, subject lines, and timing.
-
-<sequence_input>$ARGUMENTS</sequence_input>
-
-## Sequence Types
-
-| Type | Emails | Duration | Purpose |
-|------|--------|----------|---------|
-| `welcome` | 5 | 14 days | Build relationship, introduce offer |
-| `onboarding` | 7 | 21 days | Product activation, feature discovery |
-| `nurture` | 6 | 30 days | Educate, build trust, soft sell |
-| `abandon` | 3 | 3 days | Recover cart/signup abandonment |
-| `winback` | 4 | 14 days | Re-engage inactive users |
-| `launch` | 5 | 7 days | Product launch countdown |
-
-## Workflow
-
-### Step 1: Parse Input
-
-Extract sequence type and context:
-- `welcome` → New subscriber welcome series
-- `onboarding "SaaS tool"` → Product-specific onboarding
-- `launch "Black Friday"` → Campaign-specific launch
-
-### Step 2: Inject Brand Context
-
-```bash
-node .opencode/skills/brand-guidelines/scripts/inject-brand-context.cjs --json
-```
-
-Extract: brand voice, tone, prohibited words, CTA style.
-
-### Step 3: Load Email Templates
-
-Activate `email-marketing` skill and read:
-- `.opencode/skills/email-marketing/references/automation-flows.md`
-- `.opencode/skills/email-marketing/references/subject-line-formulas.md`
-- `.opencode/skills/email-marketing/references/email-templates.md`
-
-### Step 4: Generate Sequence Plan
-
-Create sequence architecture:
-
-```
-SEQUENCE: {type}
-TRIGGER: {event}
-DURATION: {days}
-GOAL: {conversion goal}
-
-EMAIL 1 (Day 0)
-├── Purpose: {purpose}
-├── Subject: {subject line}
-├── Hook: {opening line}
-├── Body: {main content}
-├── CTA: {call to action}
-└── Next: Wait {n} days
-
-EMAIL 2 (Day {n})
-...
-```
-
-### Step 5: Write Full Email Copy
-
-For each email, generate:
-1. **Subject line** (3 variants using formulas)
-2. **Preview text** (40-90 chars)
-3. **Opening hook** (pattern interrupt)
-4. **Body copy** (using PAS/AIDA)
-5. **CTA button** (action-oriented)
-6. **P.S. line** (urgency/social proof)
-
-### Step 6: Add Automation Logic
-
-Include branching conditions:
-- Opened? → Engaged path
-- Clicked? → Interest path
-- Purchased? → Exit flow
-- No action? → Reminder path
-
-### Step 7: Save Output
-
-```
-assets/copy/emails/{date}-{type}-sequence/
-├── 00-sequence-plan.md
-├── 01-{purpose}.md
-├── 02-{purpose}.md
-├── 03-{purpose}.md
-├── 04-{purpose}.md
-└── 05-{purpose}.md
-```
-
-## Output Format
-
-### Sequence Plan (00-sequence-plan.md)
-
-```markdown
-# {Type} Email Sequence
-
-## Overview
-- **Trigger:** {trigger event}
-- **Emails:** {count}
-- **Duration:** {days}
-- **Goal:** {conversion goal}
-
-## Flow Diagram
-{ASCII flow diagram}
-
-## Timing
-| Email | Day | Subject | Purpose |
-|-------|-----|---------|---------|
-| 1 | 0 | ... | ... |
-| 2 | 1 | ... | ... |
-
-## Exit Conditions
-- {condition 1}
-- {condition 2}
-```
-
-### Individual Email (01-welcome.md)
-
-```markdown
-# Email 1: {Title}
-
-**Day:** 0 (Immediate)
-**Purpose:** {purpose}
-
-## Subject Lines (Pick One)
-1. {subject 1}
-2. {subject 2}
-3. {subject 3}
-
-## Preview Text
-{40-90 char preview}
-
-## Email Body
-
-{Full email copy with formatting}
-
-## CTA
-**Button:** {CTA text}
-**Link:** {destination}
-
-## P.S.
-{urgency or social proof}
-
----
-*Next email: Day {n} - {next purpose}*
-```
-
-## Examples
-
-```bash
-/email:sequence welcome
-/email:sequence onboarding "project management SaaS"
-/email:sequence launch "New Year sale 40% off"
-/email:sequence abandon "checkout"
-/email:sequence nurture "B2B lead magnet"
-```
-
-## Skills Used
-
-- `email-marketing` - Sequence templates, timing, automation
-- `copywriting` - Email copy formulas, subject lines
-- `brand-guidelines` - Voice, tone, CTA style

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

@@ -1,64 +0,0 @@
----
-description: "💡💡 Generate email content - Args: ['type']"
----
-
-Generate email content for various marketing purposes.
-
-<type>$ARGUMENTS</type>
-
-## Email Types
-- `newsletter` - Newsletter content
-- `cold` - Cold outreach email
-- `followup` - Follow-up sequence
-- `launch` - Product launch email
-- `nurture` - Nurture sequence email
-- `welcome` - Welcome email series
-- `winback` - Re-engagement email
-
-## Workflow
-
-1. **Parse Type** from `$ARGUMENTS`
-
-2. **Gather Context**
-   - Ask via `AskUserQuestion`:
-     - Target audience/persona
-     - Key message/offer
-     - Desired action (CTA)
-
-3. **Email Creation**
-   - Use `email-wizard` agent for email strategy
-   - Use `copywriter` agent for compelling copy
-   - Activate `email-marketing` skill for templates
-   - Generate:
-     - Subject line variants (3-5)
-     - Preview text
-     - Email body
-     - CTA
-
-4. **Optimization**
-   - Deliverability check
-   - Mobile-friendly formatting
-   - A/B test recommendations
-
-5. **Output**
-   - Email file → `assets/copy/emails/{date}-{type}-{slug}.md`
-
-## Agents Used
-- `email-wizard` - Email strategy
-- `copywriter` - Email copywriting
-
-## Skills Used
-- `email-marketing` - Best practices and templates
-- `creativity` - Email visual design, color psychology, style selection
-- `assets-organizing` - Standardized output paths
-
-## Output
-- Email content → `assets/copy/emails/{date}-{type}-{slug}.md`
-
-## Examples
-```
-/email newsletter
-/email cold "SaaS founders"
-/email launch "New Feature"
-/email nurture
-```

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