@hienlh/ppm 0.9.81 → 0.9.83

package/.opencode/workflows/content-workflow.md

@@ -1,275 +0,0 @@
-# Content Workflow
-
-5-stage content production pipeline from draft to published.
-
-## Overview
-
-| Field | Value |
-|-------|-------|
-| **Purpose** | Manage content lifecycle with quality gates |
-| **Agents** | content-creator, content-reviewer, seo-specialist |
-| **Human Checkpoints** | Final approval before publish |
-
----
-
-## Content States
-
-```
-[DRAFT] → [REVIEW] → [EDIT] → [AUDIT] → [APPROVED] → [PUBLISHED]
-```
-
-Each piece of content moves through these states sequentially.
-
-**IMPORTANT:** Claude MUST automatically run `/write/audit` after any content generation command (`/youtube:*`, `/write:*`) and apply `/write/publish` fixes before presenting final output.
-
----
-
-## Workflow Stages
-
-### Stage 1: Draft
-
-**Agent:** `content-creator`
-
-**Actions:**
-1. Create initial content
-2. Apply SEO foundation
-3. Include target keywords
-4. Structure for readability
-
-**Output:** Draft in `content/drafts/`
-
-**Requirements:**
-- Content brief provided
-- Target keywords identified
-- Audience defined
-
-**Prompt Template:**
-```
-Create [content-type] draft.
-Topic: [topic]
-Keywords: [primary], [secondary]
-Audience: [audience]
-Word count: [target]
-Save to: content/drafts/[slug].md
-```
-
----
-
-### Stage 2: Review
-
-**Agent:** `content-reviewer`
-
-**Actions:**
-1. Brand voice compliance
-2. Factual accuracy check
-3. Grammar and style
-4. SEO validation
-5. Conversion elements
-
-**Output:** Review report with issues
-
-**Prompt Template:**
-```
-Review content at [path].
-Check:
-- Brand voice alignment
-- Factual accuracy
-- Grammar/spelling
-- SEO optimization
-- CTA effectiveness
-Report issues and recommendations.
-```
-
----
-
-### Stage 3: Edit
-
-**Agent:** `content-creator` (with review feedback)
-
-**Actions:**
-1. Address review feedback
-2. Refine messaging
-3. Optimize for SEO
-4. Polish copy
-
-**Output:** Revised draft
-
-**Prompt Template:**
-```
-Edit content at [path].
-Address feedback:
-[feedback-items]
-Maintain: brand voice, SEO keywords
-Save revised version.
-```
-
----
-
-### Stage 4: Audit
-
-**Command:** `/write/audit` → `/write/publish`
-
-**Actions:**
-1. Score content (Copywriting, SEO, Platform, Brand)
-2. Identify issues automatically
-3. Apply fixes (hooks, hashtags, CTAs, readability)
-4. Verify score ≥8.0
-
-**Output:** Polished content ready for approval
-
-**Auto-Triggered By:**
-- `/youtube:social`, `/youtube:blog`, `/youtube:infographic`
-- `/write:blog`, `/write:cro`
-- Any content generation command
-
-**Prompt Template:**
-```
-Run /write/audit on [path].
-If score <8.0, run /write/publish to auto-fix.
-Present final version with before/after scores.
-```
-
----
-
-### Stage 5: Approved
-
-**Agent:** `content-reviewer` (final pass)
-
-**Human Checkpoint:** Final approval required
-
-**Actions:**
-1. Verify audit score ≥8.0
-2. Final quality check
-3. Schedule publication
-4. Prepare assets
-
-**Output:** Approved content ready for publish
-
-**Requires:** `approval-workflow` hook
-
-**Prompt Template:**
-```
-Final review of [path].
-Verify audit score ≥8.0.
-Confirm ready for publication.
-If approved, schedule for [date/time].
-```
-
----
-
-### Stage 6: Published
-
-**Agent:** `social-media-manager`, `email-wizard`
-
-**Actions:**
-1. Publish to platform
-2. Distribute across channels
-3. Enable tracking
-4. Monitor initial performance
-
-**Output:** Live content with tracking
-
-**Prompt Template:**
-```
-Publish approved content at [path].
-Channels: [channels]
-Tracking: [campaign-id]
-Monitor for [duration].
-```
-
----
-
-## Content Types
-
-### Blog Post
-- Length: 1000-2500 words
-- SEO: Primary + 3-5 secondary keywords
-- Structure: Intro, H2 sections, conclusion, CTA
-
-### Landing Page
-- Length: 500-1500 words
-- Focus: Single conversion goal
-- Elements: Headline, benefits, social proof, CTA
-
-### Email
-- Length: 150-400 words
-- Focus: Single message/action
-- Elements: Subject, preview, body, CTA
-
-### Social Post
-- Length: Platform-specific
-- Focus: Engagement or click
-- Elements: Hook, value, CTA
-
-### Ad Copy
-- Length: Platform limits
-- Focus: Click-through
-- Elements: Headline, description, CTA
-
----
-
-## Quality Checklist
-
-### Brand Compliance
-- [ ] Voice and tone match guidelines
-- [ ] Visual style aligned
-- [ ] Messaging on-brand
-
-### SEO Requirements
-- [ ] Primary keyword in title
-- [ ] Keywords in H2s
-- [ ] Meta description optimized
-- [ ] Internal links included
-- [ ] Alt text for images
-
-### Conversion Elements
-- [ ] Clear value proposition
-- [ ] Compelling CTA
-- [ ] Social proof (if applicable)
-- [ ] Urgency elements (if appropriate)
-
-### Technical
-- [ ] Mobile-friendly
-- [ ] Links working
-- [ ] Images optimized
-- [ ] Load time acceptable
-
----
-
-## Integration Points
-
-### Hooks Triggered
-- `brand-guidelines-reminder` → Before Draft
-- `approval-workflow` → Before Approved → Published
-
-### Data Flow
-- Brief → Draft
-- Review → Edit feedback
-- Approval → Distribution
-- Published → Analytics
-
----
-
-## Usage Example
-
-```
-User: "Create social posts from this YouTube video"
-
-# Claude auto-triggers workflow:
-1. /youtube:social → Generate multi-platform posts
-2. /write/audit → Score content (auto-triggered)
-3. /write/publish → Fix issues if score <8.0 (auto-triggered)
-4. Present polished content with score
-5. Human approval → Publish
-```
-
-**User doesn't need to know commands.** Claude picks the right ones based on intent.
-
----
-
-## Success Metrics
-
-- Time to publish (draft → live)
-- Review cycles (iterations needed)
-- Quality score (review pass rate)
-- Performance (engagement, conversions)

package/.opencode/workflows/development-rules.md

@@ -1,42 +0,0 @@
-# Development Rules
-
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT:** You ALWAYS follow these principles: **YAGNI (You Aren't Gonna Need It) - KISS (Keep It Simple, Stupid) - DRY (Don't Repeat Yourself)**
-
-## General
-- **File Naming**: Use kebab-case for file names with a meaningful name that describes the purpose of the file, doesn't matter if the file name is long, just make sure when LLMs read the file names while using Grep or other tools, they can understand the purpose of the file right away without reading the file content.
-- **File Size Management**: Keep individual code files under 200 lines for optimal context management
-  - Split large files into smaller, focused components/modules
-  - Use composition over inheritance for complex widgets
-  - Extract utility functions into separate modules
-  - Create dedicated service classes for business logic
-- Use `docs-seeker` skill for exploring latest docs of plugins/packages if needed
-- Use `gh` bash command to interact with Github features if needed
-- Use `psql` bash command to query Postgres database for debugging if needed
-- Use `ai-multimodal` skill for describing details of images, videos, documents, etc. if needed
-- Use `ai-multimodal` skill and `imagemagick` skill for generating and editing images, videos, documents, etc. if needed
-- Use `sequential-thinking` skill and `debugging` skills for sequential thinking, analyzing code, debugging, etc. if needed
-- **[IMPORTANT]** Follow the codebase structure and code standards in `./docs` during implementation.
-- **[IMPORTANT]** Do not just simulate the implementation or mocking them, always implement the real code.
-
-## Code Quality Guidelines
-- Read and follow codebase structure and code standards in `./docs`
-- Don't be too harsh on code linting, but **make sure there are no syntax errors and code are compilable**
-- Prioritize functionality and readability over strict style enforcement and code formatting
-- Use reasonable code quality standards that enhance developer productivity
-- Use try catch error handling & cover security standards
-- Use `code-reviewer` agent to review code after every implementation
-
-## Pre-commit/Push Rules
-- Run linting before commit
-- Run tests before push (DO NOT ignore failed tests just to pass the build or github actions)
-- Keep commits focused on the actual code changes
-- **DO NOT** commit and push any confidential information (such as dotenv files, API keys, database credentials, etc.) to git repository!
-- Create clean, professional commit messages without AI references. Use conventional commit format.
-
-## Code Implementation
-- Write clean, readable, and maintainable code
-- Follow established architectural patterns
-- Implement features according to specifications
-- Handle edge cases and error scenarios
-- **DO NOT** create new enhanced files, update to the existing files directly.

package/.opencode/workflows/documentation-management.md

@@ -1,121 +0,0 @@
-# Project Documentation Management
-
-### Roadmap & Changelog Maintenance
-- **Project Roadmap** (`./docs/development-roadmap.md`): Living document tracking project phases, milestones, and progress
-- **Project Changelog** (`./docs/project-changelog.md`): Detailed record of all significant changes, features, and fixes
-- **System Architecture** (`./docs/system-architecture.md`): Detailed record of all significant changes, features, and fixes
-- **Code Standards** (`./docs/code-standards.md`): Detailed record of all significant changes, features, and fixes
-
-### Automatic Updates Required
-- **After Feature Implementation**: Update roadmap progress status and changelog entries
-- **After Major Milestones**: Review and adjust roadmap phases, update success metrics
-- **After Bug Fixes**: Document fixes in changelog with severity and impact
-- **After Security Updates**: Record security improvements and version updates
-- **Weekly Reviews**: Update progress percentages and milestone statuses
-
-### Documentation Triggers
-The `project-manager` agent MUST update these documents when:
-- A development phase status changes (e.g., from "In Progress" to "Complete")
-- Major features are implemented or released
-- Significant bugs are resolved or security patches applied
-- Project timeline or scope adjustments are made
-- External dependencies or breaking changes occur
-
-### Update Protocol
-1. **Before Updates**: Always read current roadmap and changelog status
-2. **During Updates**: Maintain version consistency and proper formatting
-3. **After Updates**: Verify links, dates, and cross-references are accurate
-4. **Quality Check**: Ensure updates align with actual implementation progress
-
-### Plans
-
-### Plan Location
-Save plans in `./plans` directory with timestamp and descriptive name.
-
-**Format:** Use naming pattern from `## Naming` section injected by hooks.
-
-**Example:** `plans/251101-1505-authentication-and-profile-implementation/`
-
-#### File Organization
-
-```
-plans/
-├── 20251101-1505-authentication-and-profile-implementation/
-    ├── research/
-    │   ├── researcher-XX-report.md
-    │   └── ...
-│   ├── reports/
-│   │   ├── scout-report.md
-│   │   ├── researcher-report.md
-│   │   └── ...
-│   ├── plan.md                                # Overview access point
-│   ├── phase-01-setup-environment.md          # Setup environment
-│   ├── phase-02-implement-database.md         # Database models
-│   ├── phase-03-implement-api-endpoints.md    # API endpoints
-│   ├── phase-04-implement-ui-components.md    # UI components
-│   ├── phase-05-implement-authentication.md   # Auth & authorization
-│   ├── phase-06-implement-profile.md          # Profile page
-│   └── phase-07-write-tests.md                # Tests
-└── ...
-```
-
-#### File Structure
-
-##### Overview Plan (plan.md)
-- Keep generic and under 80 lines
-- List each phase with status/progress
-- Link to detailed phase files
-- Key dependencies
-
-##### Phase Files (phase-XX-name.md)
-Fully respect the `./docs/development-rules.md` file.
-Each phase file should contain:
-
-**Context Links**
-- Links to related reports, files, documentation
-
-**Overview**
-- Priority
-- Current status
-- Brief description
-
-**Key Insights**
-- Important findings from research
-- Critical considerations
-
-**Requirements**
-- Functional requirements
-- Non-functional requirements
-
-**Architecture**
-- System design
-- Component interactions
-- Data flow
-
-**Related Code Files**
-- List of files to modify
-- List of files to create
-- List of files to delete
-
-**Implementation Steps**
-- Detailed, numbered steps
-- Specific instructions
-
-**Todo List**
-- Checkbox list for tracking
-
-**Success Criteria**
-- Definition of done
-- Validation methods
-
-**Risk Assessment**
-- Potential issues
-- Mitigation strategies
-
-**Security Considerations**
-- Auth/authorization
-- Data protection
-
-**Next Steps**
-- Dependencies
-- Follow-up tasks

package/.opencode/workflows/marketing-workflow.md

@@ -1,198 +0,0 @@
-# Marketing Workflow
-
-End-to-end marketing process orchestration from research to measurement.
-
-## Overview
-
-| Field | Value |
-|-------|-------|
-| **Purpose** | Orchestrate complete marketing cycle |
-| **Agents** | researcher, planner, content-creator, content-reviewer, social-media-manager, analytics-analyst |
-| **Human Checkpoints** | Strategy approval, Content approval |
-
----
-
-## Workflow Stages
-
-### Stage 1: Research & Insights
-
-**Agent:** `researcher`
-
-**Actions:**
-1. Competitive analysis
-2. Audience research
-3. Market trends
-4. Keyword opportunities
-
-**Output:** Research reports in `plans/reports/`
-
-**Prompt Template:**
-```
-Research [topic/market] for marketing campaign.
-Include: competitor analysis, audience insights, trends.
-Save report to plans/reports/[date]-research-[topic].md
-```
-
----
-
-### Stage 2: Strategy & Planning
-
-**Agent:** `planner`
-
-**Actions:**
-1. Define campaign objectives
-2. Select channels
-3. Set KPIs
-4. Create timeline
-
-**Output:** Marketing plan in `plans/`
-
-**Human Checkpoint:** Strategy approval required
-
-**Prompt Template:**
-```
-Create marketing strategy for [objective].
-Based on research: [research-report-path]
-Include: channels, KPIs, timeline.
-Save to plans/[date]-marketing-strategy.md
-```
-
----
-
-### Stage 3: Content Creation
-
-**Agent:** `content-creator`
-
-**Actions:**
-1. Generate content drafts
-2. Create ad copy
-3. Design assets
-4. SEO optimization
-
-**Output:** Content drafts in `content/drafts/`
-
-**Requires:** Brand guidelines hook active
-
-**Prompt Template:**
-```
-Create [content-type] for [campaign].
-Target audience: [audience]
-Tone: [brand-voice]
-Include: headlines, body, CTAs
-```
-
----
-
-### Stage 4: Review & Approval
-
-**Agent:** `content-reviewer`
-
-**Actions:**
-1. Brand compliance check
-2. Fact verification
-3. Grammar/style review
-4. SEO validation
-
-**Human Checkpoint:** Content approval required
-
-**Prompt Template:**
-```
-Review content at [path].
-Check: brand alignment, accuracy, SEO, conversion potential.
-Report issues and recommendations.
-```
-
----
-
-### Stage 5: Distribution
-
-**Agent:** `social-media-manager`, `email-wizard`
-
-**Actions:**
-1. Schedule social posts
-2. Launch email campaigns
-3. Publish blog content
-4. Activate ads
-
-**Requires:** Approval workflow hook
-
-**Prompt Template:**
-```
-Distribute approved content.
-Channels: [channels]
-Schedule: [dates/times]
-Track with campaign ID: [campaign-id]
-```
-
----
-
-### Stage 6: Measurement
-
-**Agent:** `analytics-analyst`
-
-**Actions:**
-1. Track performance metrics
-2. Attribution analysis
-3. Generate reports
-4. Recommend optimizations
-
-**Output:** Analytics reports in `plans/reports/`
-
-**Prompt Template:**
-```
-Analyze campaign [campaign-id] performance.
-Metrics: traffic, conversions, engagement, ROI.
-Compare to KPIs. Recommend next steps.
-```
-
----
-
-## Agent Orchestration
-
-```
-[Research] → [Strategy] → [Content] → [Review] → [Distribution] → [Measurement]
-     │            │            │           │             │              │
-researcher    planner    content-    content-     social-media-   analytics-
-                         creator     reviewer       manager        analyst
-```
-
----
-
-## Integration Points
-
-### Hooks Triggered
-- `brand-guidelines-reminder` → Before content-creator
-- `campaign-tracking` → After each stage
-- `approval-workflow` → Before distribution
-
-### Data Flow
-- Research → feeds Strategy
-- Strategy → guides Content
-- Review → gates Distribution
-- Measurement → informs next cycle
-
----
-
-## Usage Example
-
-```
-/campaign launch "Q1 Product Launch"
-
-# Triggers workflow:
-1. researcher: Market analysis
-2. planner: Campaign strategy (await approval)
-3. content-creator: Landing page, emails, social posts
-4. content-reviewer: Review all assets (await approval)
-5. social-media-manager: Schedule distribution
-6. analytics-analyst: Track and report
-```
-
----
-
-## Success Metrics
-
-- Research depth (sources, insights)
-- Strategy alignment (objectives → tactics)
-- Content quality (brand compliance, engagement)
-- Distribution timing (on-schedule)
-- Performance (vs KPIs)

package/.opencode/workflows/orchestration-protocol.md

@@ -1,16 +0,0 @@
-# Orchestration Protocol
-
-#### Sequential Chaining
-Chain subagents when tasks have dependencies or require outputs from previous steps:
-- **Planning → Implementation → Testing → Review**: Use for feature development
-- **Research → Design → Code → Documentation**: Use for new system components
-- Each agent completes fully before the next begins
-- Pass context and outputs between agents in the chain
-
-#### Parallel Execution
-Spawn multiple subagents simultaneously for independent tasks:
-- **Code + Tests + Docs**: When implementing separate, non-conflicting components
-- **Multiple Feature Branches**: Different agents working on isolated features
-- **Cross-platform Development**: iOS and Android specific implementations
-- **Careful Coordination**: Ensure no file conflicts or shared resource contention
-- **Merge Strategy**: Plan integration points before parallel execution begins

package/.opencode/workflows/primary-workflow.md

@@ -1,45 +0,0 @@
-# Primary Workflow
-
-**IMPORTANT:** Analyze the skills catalog and activate the skills that are needed for the task during the process.
-**IMPORTANT**: Ensure token efficiency while maintaining high quality.
-
-#### 1. Code Implementation
-- Before you start, delegate to `planner` agent to create a implementation plan with TODO tasks in `./plans` directory.
-- When in planning phase, use multiple `researcher` agents in parallel to conduct research on different relevant technical topics and report back to `planner` agent to create implementation plan.
-- Write clean, readable, and maintainable code
-- Follow established architectural patterns
-- Implement features according to specifications
-- Handle edge cases and error scenarios
-- **DO NOT** create new enhanced files, update to the existing files directly.
-- **[IMPORTANT]** After creating or modifying code file, run compile command/script to check for any compile errors.
-
-#### 2. Testing
-- Delegate to `tester` agent to run tests and analyze the summary report.
-  - Write comprehensive unit tests
-  - Ensure high code coverage
-  - Test error scenarios
-  - Validate performance requirements
-- Tests are critical for ensuring code quality and reliability, **DO NOT** ignore failing tests just to pass the build.
-- **IMPORTANT:** make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions.
-- **IMPORTANT:** Always fix failing tests follow the recommendations and delegate to `tester` agent to run tests again, only finish your session when all tests pass.
-
-#### 3. Code Quality
-- After finish implementation, delegate to `code-reviewer` agent to review code.
-- Follow coding standards and conventions
-- Write self-documenting code
-- Add meaningful comments for complex logic
-- Optimize for performance and maintainability
-
-#### 4. Integration
-- Always follow the plan given by `planner` agent
-- Ensure seamless integration with existing code
-- Follow API contracts precisely
-- Maintain backward compatibility
-- Document breaking changes
-- Delegate to `docs-manager` agent to update docs in `./docs` directory if any.
-
-#### 5. Debugging
-- When a user report bugs or issues on the server or a CI/CD pipeline, delegate to `debugger` agent to run tests and analyze the summary report.
-- Read the summary report from `debugger` agent and implement the fix.
-- Delegate to `tester` agent to run tests and analyze the summary report.
-- If the `tester` agent reports failed tests, fix them follow the recommendations and repeat from the **Step 2**.