myaidev-method 0.2.24-1 → 0.2.24-2

package/src/templates/claude/commands/myai-coordinate-content.md

@@ -10,12 +10,58 @@ You are a Content Production Coordinator specializing in orchestrating content v
 
 Coordinate the content production workflow for the provided directory: $ARGUMENTS
 
+## Content Queue File Format
+
+Each markdown file in your content queue should follow this structure:
+
+```markdown
+---
+title: "Your Article Title"
+content_type: article
+target_platform: wordpress
+status: pending
+priority: normal
+references:
+  - "https://source1.com"
+  - "https://source2.com"
+goals:
+  - "Primary goal for this content"
+  - "Secondary goal"
+---
+
+## Proprietary Content
+
+[Your unique insights, original analysis, and value-add content here.
+This is the section that gets verified for uniqueness.]
+
+## Supporting Content
+
+[Additional context, examples, and supporting material]
+```
+
+### Required Fields
+| Field | Description |
+|-------|-------------|
+| `title` | Article title (used for publishing) |
+| **Proprietary Content section** | Your unique content to be verified |
+
+### Optional Fields
+| Field | Values | Default |
+|-------|--------|---------|
+| `content_type` | article, tutorial, guide, listicle | article |
+| `target_platform` | wordpress, payloadcms, static, docusaurus, mintlify, astro | wordpress |
+| `status` | pending, verified, published, failed | pending |
+| `priority` | high, normal, low | normal |
+| `references` | Array of source URLs | [] |
+| `goals` | Array of publishing goals | [] |
+
 ## Workflow
 
 ### 1. Initialize Work List
-- Read all files from the provided directory path in $ARGUMENTS
-- Parse each file for: Title, Proprietary Content, References, and Goals
-- Display a summary of found items to the user
+- Read all markdown files from the provided directory path in $ARGUMENTS
+- Parse YAML front matter and content sections
+- Validate required fields (title, Proprietary Content section)
+- Display a summary of found items with validation status
 - Ask for confirmation before proceeding with verification
 
 ### 2. Verify Content in Parallel
@@ -45,11 +91,167 @@ Coordinate the content production workflow for the provided directory: $ARGUMENT
 
 ## Parameters Supported
 
-- Directory path (required): Path to content queue directory
-- `--dry-run`: Only verify content, don't publish
-- `--force`: Skip confirmation prompts
-- `--verbose`: Show detailed progress for each item
-- `--output-dir`: Directory for report files (default: current directory)
+### Core Parameters
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| Directory path (required) | Path to content queue directory | - |
+| `--dry-run` | Only verify content, don't publish | false |
+| `--force` | Skip confirmation prompts | false |
+| `--verbose` | Show detailed progress for each item | false |
+| `--output-dir` | Directory for report files | current directory |
+| `--concurrency` | Max parallel operations (1-10) | 3 |
+| `--fresh` | Ignore existing state, start fresh | false |
+| `--resume` | Resume from last checkpoint (auto-detected) | true |
+| `--retry-count` | Number of retry attempts per item | 2 |
+
+### Content Rules Integration
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `--content-rules` | Path to content-rules.md file | auto-detect |
+
+The coordinator automatically searches for `content-rules.md` in these locations:
+1. Explicit path via `--content-rules`
+2. `./content-rules.md` (current directory)
+3. `./.claude/content-rules.md`
+4. `./docs/content-rules.md`
+
+Content rules provide brand voice, writing style, and SEO guidelines that are passed to both the verifier and content writer for consistent output.
+
+### Multi-Platform Publishing
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `--platform` | Default publishing platform | wordpress |
+
+**Supported Platforms:**
+- `wordpress` - WordPress REST API (requires credentials)
+- `payloadcms` - Payload CMS REST API
+- `static` - Generate static markdown files
+- `docusaurus` - Docusaurus documentation site
+- `mintlify` - Mintlify documentation
+- `astro` - Astro content collections
+
+Each content item can override the default platform using the `target_platform` front matter field.
+
+### Webhook Notifications (CI/CD Integration)
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `--webhook-url` | URL to receive workflow notifications | none |
+| `--webhook-events` | Comma-separated events to notify | complete,error |
+
+**Available Events:**
+- `start` - When workflow begins
+- `complete` - When workflow finishes successfully
+- `error` - When errors occur
+- `published` - When each item is published
+
+**Webhook Payload Example:**
+```json
+{
+  "event": "complete",
+  "timestamp": "2026-01-20T10:30:00Z",
+  "workflow": "content-coordination",
+  "data": {
+    "totalItems": 10,
+    "published": 7,
+    "needsReview": 2,
+    "failed": 1,
+    "duration": "5m 23s"
+  }
+}
+```
+
+### Analytics & Monitoring
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `--analytics` | Enable detailed analytics tracking | true |
+| `--analytics-report` | Generate analytics report file | true |
+
+When enabled, generates `analytics-YYYY-MM-DD-HH-MM-SS.md` with:
+- Per-phase timing metrics
+- Success/failure rates
+- Average verification and publishing times
+- Content quality score trends
+- Error categorization
+
+### Queue Management
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `--queue` | Path to persistent queue file | .content-queue.json |
+| `--add-to-queue` | Add items to queue without processing | false |
+| `--clear-completed` | Remove completed items from queue | false |
+| `--queue-stats` | Display queue statistics | false |
+
+**Queue Commands:**
+```bash
+# Add items to queue for later processing
+/myai-coordinate-content ./new-content/ --add-to-queue
+
+# View queue statistics
+/myai-coordinate-content --queue-stats
+
+# Clear completed items from queue
+/myai-coordinate-content --clear-completed
+
+# Process queued items
+/myai-coordinate-content --queue .content-queue.json
+```
+
+### Scheduling (Cron & WordPress)
+
+**Linux Crontab Integration:**
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `--cron` | Enable cron-safe mode (lock files, quiet output) | false |
+| `--min-interval` | Minimum seconds between runs | 0 |
+| `--generate-crontab` | Generate crontab entry and exit | false |
+
+**WordPress Native Scheduling:**
+| Parameter | Description | Default |
+|-----------|-------------|---------|
+| `--schedule-delay` | Hours to delay publication | 0 |
+| `--spread-interval` | Hours between scheduled posts | 0 |
+| `--schedule-date` | Specific publish date (ISO 8601) | immediate |
+
+**Cron Setup:**
+```bash
+# Generate crontab entry
+/myai-coordinate-content --generate-crontab
+
+# Run in cron-safe mode (for crontab)
+/myai-coordinate-content ./content-queue/ --cron --force
+
+# With minimum 6-hour interval between runs
+/myai-coordinate-content ./content-queue/ --cron --min-interval 21600
+```
+
+**WordPress Scheduling (schedule posts for future publication):**
+```bash
+# Delay all posts by 24 hours
+/myai-coordinate-content ./content-queue/ --schedule-delay 24
+
+# Spread posts 6 hours apart
+/myai-coordinate-content ./content-queue/ --spread-interval 6
+
+# Combined: Start in 24 hours, then every 6 hours
+/myai-coordinate-content ./content-queue/ --schedule-delay 24 --spread-interval 6
+```
+
+**Content Front Matter Scheduling:**
+```yaml
+---
+title: "My Article"
+publish_date: "2026-02-15T09:00:00Z"  # Schedule for specific date
+# OR
+scheduled_date: "2026-02-15T09:00:00Z"
+---
+```
+
+### Checkpoint/Resume
+
+The coordinator automatically saves progress to `.content-coordinator-state.json`. If interrupted:
+- Re-run the same command to resume from the last checkpoint
+- Use `--fresh` to start over and ignore saved state
+- Delete the state file manually to reset
 
 ## Output Format
 
@@ -110,20 +312,154 @@ Generated: YYYY-MM-DD HH:MM:SS
 
 ## Example Usage
 
+### Basic Operations
 ```bash
-# Basic usage
+# Basic usage - process all content in queue
 /myai-coordinate-content ./content-queue/
 
-# Dry run to verify content only
+# Dry run - verify content only, no publishing
 /myai-coordinate-content ./content-queue/ --dry-run
 
-# Force publishing without confirmations
+# Force mode - skip all confirmations (useful for CI/CD)
 /myai-coordinate-content ./content-queue/ --force
 
 # Verbose output with custom report directory
 /myai-coordinate-content ./content-queue/ --verbose --output-dir ./reports/
+
+# High concurrency for large batches
+/myai-coordinate-content ./content-queue/ --concurrency 5
+
+# Start fresh, ignoring any saved state
+/myai-coordinate-content ./content-queue/ --fresh
+
+# Resume an interrupted workflow (automatic)
+/myai-coordinate-content ./content-queue/
+```
+
+### Multi-Platform Publishing
+```bash
+# Publish to PayloadCMS instead of WordPress
+/myai-coordinate-content ./content-queue/ --platform payloadcms
+
+# Generate static markdown files
+/myai-coordinate-content ./content-queue/ --platform static --output-dir ./published/
+
+# Publish to Docusaurus documentation site
+/myai-coordinate-content ./docs-queue/ --platform docusaurus
+```
+
+### Content Rules Integration
+```bash
+# Use custom content rules file
+/myai-coordinate-content ./content-queue/ --content-rules ./brand/content-rules.md
+
+# Content rules are auto-detected from standard locations
+/myai-coordinate-content ./content-queue/  # Finds ./content-rules.md automatically
+```
+
+### CI/CD Integration with Webhooks
+```bash
+# Send notifications to CI/CD webhook
+/myai-coordinate-content ./content-queue/ --webhook-url https://ci.example.com/webhook
+
+# Notify on all events including each published item
+/myai-coordinate-content ./content-queue/ --webhook-url https://ci.example.com/webhook --webhook-events start,complete,error,published
+
+# Full CI/CD pipeline integration
+/myai-coordinate-content ./content-queue/ --force --webhook-url $CI_WEBHOOK_URL --analytics
+```
+
+### Queue Management
+```bash
+# Add new content to queue without processing
+/myai-coordinate-content ./new-articles/ --add-to-queue
+
+# View queue statistics
+/myai-coordinate-content --queue-stats
+
+# Process items from queue
+/myai-coordinate-content --queue .content-queue.json
+
+# Clear completed items from queue
+/myai-coordinate-content --clear-completed
+```
+
+### Analytics & Monitoring
+```bash
+# Enable detailed analytics (default)
+/myai-coordinate-content ./content-queue/ --analytics
+
+# Full production run with all options
+/myai-coordinate-content ./content-queue/ \
+  --verbose \
+  --output-dir ./reports/ \
+  --concurrency 3 \
+  --content-rules ./brand/content-rules.md \
+  --webhook-url https://ci.example.com/webhook \
+  --analytics
 ```
 
+### Automated Scheduling
+
+**Setup Linux Crontab:**
+```bash
+# Generate crontab entry with instructions
+/myai-coordinate-content --generate-crontab
+
+# Example crontab entries (add to crontab -e):
+
+# Every 6 hours
+0 */6 * * * cd /path/to/project && npx myaidev-method coordinate-content ./content-queue --cron --force >> /var/log/content-coordinator.log 2>&1
+
+# Daily at 9 AM
+0 9 * * * cd /path/to/project && npx myaidev-method coordinate-content ./content-queue --cron --force >> /var/log/content-coordinator.log 2>&1
+
+# Weekdays at 9 AM and 5 PM
+0 9,17 * * 1-5 cd /path/to/project && npx myaidev-method coordinate-content ./content-queue --cron --force >> /var/log/content-coordinator.log 2>&1
+```
+
+**WordPress Post Scheduling:**
+```bash
+# Schedule posts to publish over the next week (one per day)
+/myai-coordinate-content ./content-queue/ --spread-interval 24
+
+# Delay publishing by 48 hours, then spread every 12 hours
+/myai-coordinate-content ./content-queue/ --schedule-delay 48 --spread-interval 12
+
+# Set specific publish dates in content front matter:
+# publish_date: "2026-02-20T09:00:00Z"
+```
+
+**Combined Automation (Cron + WordPress Scheduling):**
+```bash
+# Run via cron, but schedule posts for optimal times
+/myai-coordinate-content ./content-queue/ \
+  --cron \
+  --force \
+  --schedule-delay 24 \
+  --spread-interval 6 \
+  --webhook-url https://ci.example.com/content-published
+```
+
+### Setting Up a Content Queue
+
+1. Create a directory for your content queue:
+   ```bash
+   mkdir -p ./content-queue
+   ```
+
+2. Add content files following the format above:
+   ```bash
+   # Example: ./content-queue/api-best-practices.md
+   ```
+
+3. Run the coordinator:
+   ```bash
+   /myai-coordinate-content ./content-queue/
+   ```
+
+4. Review the generated reports and confirm publishing
+
 ## User Communication
 
 - Always confirm before starting verification