myaidev-method 0.3.1 → 0.3.3

package/extension.json

@@ -62,7 +62,7 @@
       "id": "sparc-development",
       "name": "SPARC Development",
       "description": "Specification-Pseudocode-Architecture-Refinement-Completion methodology",
-      "skills": ["sparc-architect", "sparc-coder", "sparc-tester", "sparc-reviewer", "sparc-documenter"],
+      "skills": ["myaidev-architect", "myaidev-coder", "myaidev-tester", "myaidev-reviewer", "myaidev-documenter", "myaidev-analyze", "myaidev-debug", "myaidev-refactor", "myaidev-performance", "myaidev-migrate"],
       "platforms": ["claudeCode", "geminiCli", "codexCli"]
     },
     {
@@ -103,7 +103,7 @@
     "development": {
       "name": "Development Pack",
       "description": "SPARC methodology for software development",
-      "skills": ["sparc-architect", "sparc-coder", "sparc-tester", "sparc-reviewer", "sparc-documenter"]
+      "skills": ["myaidev-workflow", "myaidev-architect", "myaidev-coder", "myaidev-tester", "myaidev-reviewer", "myaidev-documenter", "myaidev-analyze", "myaidev-debug", "myaidev-refactor", "myaidev-performance", "myaidev-migrate"]
     },
     "security": {
       "name": "Security Pack",
@@ -120,7 +120,7 @@
       "description": "All skills and capabilities",
       "skills": [
         "content-writer", "content-verifier", "visual-generator", "wordpress-publisher",
-        "sparc-architect", "sparc-coder", "sparc-tester", "sparc-reviewer", "sparc-documenter",
+        "myaidev-workflow", "myaidev-architect", "myaidev-coder", "myaidev-tester", "myaidev-reviewer", "myaidev-documenter", "myaidev-analyze", "myaidev-debug", "myaidev-refactor", "myaidev-performance", "myaidev-migrate",
         "security-tester", "security-auditor",
         "coolify-deployer", "openstack-manager"
       ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "myaidev-method",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "Comprehensive development framework with SPARC methodology for AI-assisted software development, security testing (PTES, OWASP, penetration testing, compliance auditing), AI visual content generation (Gemini, OpenAI GPT Image 1.5, Imagen, FLUX 2, Veo 3), OpenStack VM management, multi-platform publishing (WordPress, PayloadCMS, Astro, Docusaurus, Mintlify), and Coolify deployment",
   "mcpName": "io.github.myaione/myaidev-method",
   "main": "src/index.js",
@@ -37,6 +37,7 @@
     "dev:review": "node src/scripts/dev-review.js",
     "dev:docs": "node src/scripts/dev-docs.js",
     "sparc": "node src/scripts/sparc-workflow.js",
+    "myaidev": "node src/scripts/sparc-workflow.js",
     "wordpress:troubleshoot": "node src/templates/docs/wordpress-troubleshoot.js",
     "wordpress:health-check": "node src/scripts/wordpress-health-check.js",
     "wordpress:security-scan": "node src/scripts/wordpress-security-scan.js",
@@ -123,7 +124,6 @@
     "inquirer": "^13.1.0",
     "jose": "^6.1.3",
     "marked": "^17.0.1",
-    "node-fetch": "^3.3.2",
     "ora": "^9.0.0",
     "pptxgenjs": "^4.0.1",
     "puppeteer": "^24.35.0",
@@ -175,5 +175,12 @@
   ],
   "engines": {
     "node": ">=18.0.0"
+  },
+  "overrides": {
+    "glob": "^13.0.0",
+    "rimraf": "^6.0.0",
+    "gaxios": {
+      "node-fetch": "npm:node-fetch-native@^1.6.0"
+    }
   }
 }

package/skills/content-writer/SKILL.md

@@ -1,40 +1,26 @@
 ---
 name: content-writer
-description: Orchestrates professional content creation through a multi-agent pipeline covering research, planning, writing, SEO optimization, and visual generation. Use when creating articles, blog posts, technical tutorials, or any written content.
-argument-hint: "[topic] [--word-count=1500] [--tone=professional] [--type=blog-post] [--with-images]"
-allowed-tools: [Read, Write, Edit, WebSearch, WebFetch, Task, Bash, Glob, Grep, AskUserQuestion]
+description: Orchestrates professional content creation through a multi-agent pipeline covering research, planning, writing, SEO optimization, and editorial review. Use when creating articles, blog posts, technical tutorials, or any written content.
+argument-hint: "<topic> [--word-count=1500] [--tone=professional] [--type=blog-post]"
+allowed-tools: [Read, Write, WebSearch, WebFetch, Task, Bash, Glob, Grep, AskUserQuestion]
 context: fork
 ---
 
-# Content Writer Skill v2 — Orchestrator Pattern
+# Content Writer — Orchestrator
 
-You are the **Content Production Orchestrator**, a coordinator that decomposes content creation into specialized subagent tasks. Inspired by long-running agent harness patterns, you maintain a lightweight planning context while delegating intensive work to isolated subagents.
+You are the **Content Production Orchestrator**. You parse arguments, dispatch specialized subagents via the Task tool, and assemble their outputs into a final article. All intermediate state flows through `.content-session/` scratchpad files.
 
-## Architecture Overview
+## Subagent Registry
 
-```
-┌─────────────────────────────────────────────────────────┐
-│                  ORCHESTRATOR (this skill)              │
-│  • Parses arguments & loads content-rules               │
-│  • Creates execution plan                               │
-│  • Dispatches subagents                                 │
-│  • Aggregates results into final article                │
-│  • Manages scratchpad state files                       │
-└──────────────┬──────────────────────────────────────────┘
-               │ spawns
-    ┌──────────┼──────────────┬─────────────────┐
-    ▼          ▼              ▼                 ▼
-┌────────┐ ┌────────┐  ┌──────────┐  ┌──────────────┐
-│Research│ │Planner │  │  Writer  │  │Visual Planner│
-│ Agent  │ │ Agent  │  │  Agent   │  │    Agent     │
-└────────┘ └────────┘  └──────────┘  └──────────────┘
-                              │
-                    ┌─────────┼──────────┐
-                    ▼         ▼          ▼
-              ┌─────────┐ ┌──────┐ ┌────────┐
-              │SEO Agent│ │Editor│ │Visuals │
-              └─────────┘ └──────┘ └────────┘
-```
+Each subagent is a real Claude Code subagent defined in `agents/` with its own tools and model:
+
+| Phase | Subagent Name | Model | Tools |
+|-------|--------------|-------|-------|
+| Research | `content-research-agent` | inherit | WebSearch, WebFetch, Read, Write |
+| Planning | `content-planner-agent` | sonnet | Read, Write |
+| Writing | `content-writer-agent` | inherit | Read, Write, WebSearch |
+| SEO | `content-seo-agent` | haiku | Read, Write, WebSearch |
+| Editor | `content-editor-agent` | sonnet | Read, Write |
 
 ## Execution Phases
 
@@ -44,71 +30,80 @@ You are the **Content Production Orchestrator**, a coordinator that decomposes c
 - Determine content type template and constraints
 - Create scratchpad directory: `.content-session/` (ephemeral, gitignored)
 
-### Phase 1: Research (Subagent)
-Spawn a **research subagent** to gather information:
+### Phase 1: Research
 
+Spawn the research subagent:
+
+```
+Task(subagent_type: "content-research-agent", prompt: "
+  Research the topic '{topic}' for a {type} article.
+  Target audience: {audience}. Tone: {tone}.
+  {content_rules_section}
+  Write your findings to .content-session/research.md
+")
 ```
-Task(subagent_type: "general-purpose", prompt: "...")
+
+Skip if `--no-research` flag is set.
+
+### Phase 2: Plan
+
+Read `.content-session/research.md`, then spawn the planner:
+
 ```
+Task(subagent_type: "content-planner-agent", prompt: "
+  Create a detailed article plan for: '{topic}'
+  Content type: {type} | Word count: {word_count} | Tone: {tone}
+  Audience: {audience} | Keywords: {keywords}
+
+  Research summary (from Phase 1):
+  {brief research summary - key findings, angle, gaps}
+
+  {content_rules_section}
+  Write the plan to .content-session/plan.md
+")
+```
+
+### Phase 3: Write (main workload)
+
+Read `.content-session/plan.md` and `.content-session/research.md`, then spawn the writer:
+
+```
+Task(subagent_type: "content-writer-agent", prompt: "
+  Write the full article based on the plan and research.
+  Read the plan from: .content-session/plan.md
+  Read the research from: .content-session/research.md
+  {content_rules_section}
+  Write the complete draft to .content-session/draft.md
+")
+```
+
+### Phase 4: Optimize (Parallel)
 
-The research agent:
-- Uses WebSearch to find 5-8 relevant, current sources
-- Extracts key facts, statistics, expert quotes
-- Identifies content gaps in existing coverage
-- Writes findings to `.content-session/research.md`
-- Returns a concise research summary (not raw data)
-
-### Phase 2: Plan (Subagent)
-Spawn a **planning subagent** with research summary + content rules:
-
-The planner:
-- Creates detailed article outline with section structure
-- Assigns word count targets per section
-- Plans keyword placement strategy
-- Identifies visual content opportunities (if `--with-images`)
-- Writes plan to `.content-session/plan.md`
-- Returns the outline structure
-
-### Phase 3: Write (Subagent — main workload)
-Spawn a **writer subagent** with the plan + research + content rules:
-
-The writer:
-- Produces the full article following the plan
-- Applies brand voice from content-rules
-- Integrates research findings naturally
-- Writes draft to `.content-session/draft.md`
-- Returns completion status
-
-### Phase 4: Optimize (Parallel Subagents)
 Spawn SEO and editorial subagents **in parallel**:
 
-**SEO Agent:**
-- Reviews keyword density and placement
-- Generates meta description, slug, tags
-- Suggests internal/external links
-- Checks heading hierarchy
-- Writes SEO report to `.content-session/seo-report.md`
-
-**Editor Agent:**
-- Reviews for clarity, flow, grammar
-- Checks tone consistency
-- Verifies factual accuracy markers
-- Suggests improvements
-- Writes edit notes to `.content-session/edit-notes.md`
-
-### Phase 5: Visual Strategy (Conditional — if `--with-images`)
-Spawn a **visual planning subagent**:
-- Reviews article for visual opportunities
-- Creates image specifications (prompts, types, placements)
-- Writes visual plan to `.content-session/visual-plan.md`
-- Orchestrator then generates images using the visual-generator skill
-
-### Phase 6: Assemble & Finalize
+```
+Task(subagent_type: "content-seo-agent", prompt: "
+  Analyze the article draft for SEO optimization.
+  Read the draft from: .content-session/draft.md
+  Keywords: {keywords}. Content type: {type}.
+  Write your SEO report to .content-session/seo-report.md
+")
+
+Task(subagent_type: "content-editor-agent", prompt: "
+  Review the article draft for quality and publication readiness.
+  Read the draft from: .content-session/draft.md
+  Target tone: {tone}. Target audience: {audience}.
+  {content_rules_section}
+  Write your editorial report to .content-session/edit-notes.md
+")
+```
+
+### Phase 5: Assemble & Finalize
+
 The orchestrator (this skill):
-- Reads all scratchpad files
+- Reads all scratchpad files (.content-session/draft.md, seo-report.md, edit-notes.md)
 - Applies SEO recommendations to the draft
 - Incorporates editorial improvements
-- Embeds visual references if generated
 - Produces final article with proper frontmatter
 - Saves to `./content-output/{slug}.md`
 - Cleans up `.content-session/` directory
@@ -123,8 +118,6 @@ The orchestrator (this skill):
 | `--type` | Template: blog-post, technical-tutorial, how-to-guide, listicle, comparison-guide, case-study, api-documentation, architecture-guide | blog-post |
 | `--audience` | Target reader demographic | general |
 | `--keywords` | Comma-separated primary,secondary keywords | auto-detected |
-| `--with-images` | Enable AI visual generation | false |
-| `--image-service` | Preferred image service: gemini, dalle, flux, imagen | auto |
 | `--publish` | Publish to platform: wordpress, payloadcms, docusaurus, mintlify, astro | none |
 | `--output-dir` | Output directory for final article | ./content-output |
 | `--no-research` | Skip research phase (use for topics you provide context for) | false |
@@ -132,7 +125,7 @@ The orchestrator (this skill):
 
 ## Content Rules Integration
 
-The orchestrator automatically discovers and loads content rules. Rules are passed to every subagent to ensure consistent brand voice.
+The orchestrator automatically discovers and loads content rules. Rules are passed to every subagent via the Task prompt to ensure consistent brand voice.
 
 **Discovery order:**
 1. `./content-rules.md`
@@ -141,40 +134,12 @@ The orchestrator automatically discovers and loads content rules. Rules are pass
 
 If no rules file exists, suggest running the content-rules-setup skill.
 
-**Rules are injected into subagent prompts as:**
+**Rules are injected into Task prompts as:**
 ```
 ## Brand & Style Guidelines (from content-rules.md)
 {content of rules file}
 ```
 
-## Subagent Prompt Templates
-
-Each subagent has a detailed prompt template in the `agents/` directory. Load the appropriate file when spawning each subagent, injecting the dynamic variables ({topic}, {type}, {tone}, etc.) and {content_rules_section}.
-
-| Phase | Prompt File | Key Variables |
-|-------|-------------|---------------|
-| Research | [agents/research-agent.md](agents/research-agent.md) | topic, type, audience, tone |
-| Planning | [agents/planner-agent.md](agents/planner-agent.md) | topic, type, word_count, tone, audience, keywords, research_summary |
-| Writing | [agents/writer-agent.md](agents/writer-agent.md) | plan_content, research_summary, word_count, tone |
-| SEO | [agents/seo-agent.md](agents/seo-agent.md) | draft_content, keywords, type |
-| Editor | [agents/editor-agent.md](agents/editor-agent.md) | draft_content, tone, audience |
-| Visual | [agents/visual-planner-agent.md](agents/visual-planner-agent.md) | draft_content, type, available_services |
-
-All templates include a `{content_rules_section}` placeholder — inject the loaded content-rules when present.
-
-## Content Type Templates
-
-| Type | Structure | Typical Length | Key Elements |
-|------|-----------|----------------|--------------|
-| `blog-post` | Intro → 3-5 sections → Conclusion | 1500-2500 | Hook, examples, CTA |
-| `technical-tutorial` | Prereqs → Steps → Troubleshooting | 2000-3500 | Code, diagrams, verification |
-| `how-to-guide` | Problem → Solution → Best Practices | 1500-2500 | Step-by-step, tips |
-| `listicle` | Intro → Numbered Items → Summary | 1200-2000 | Consistent format per item |
-| `comparison-guide` | Overview → Deep Dives → Decision | 1500-2500 | Tables, pros/cons |
-| `case-study` | Challenge → Solution → Results | 1200-2000 | Metrics, quotes |
-| `api-documentation` | Overview → Endpoints → Examples | 1000-2000 | Code, tables |
-| `architecture-guide` | Summary → Components → Data Flow | 2500-4000 | Diagrams, tech details |
-
 ## State Management (Scratchpad Pattern)
 
 All intermediate work is written to `.content-session/` directory:
@@ -188,78 +153,82 @@ All intermediate work is written to `.content-session/` directory:
 ├── draft.md             # Writer agent output
 ├── seo-report.md        # SEO optimization suggestions
 ├── edit-notes.md        # Editorial feedback
-├── visual-plan.json     # Visual content specifications
 └── final-meta.json      # Assembled frontmatter data
 ```
 
-This keeps the orchestrator's context lean — it reads only what it needs for each phase.
-
 ## Execution Flow
 
 ```
-1. INIT        → Parse args, load rules, create session dir
-2. RESEARCH    → Spawn research agent (skip if --no-research)
-3. PLAN        → Spawn planner with research summary
-4. WRITE       → Spawn writer with plan + research
-5. OPTIMIZE    → Spawn SEO + Editor agents IN PARALLEL
-6. VISUALS     → Spawn visual planner (if --with-images)
-                  → Generate images using visual-generator skill
-7. ASSEMBLE    → Read all outputs, produce final article
-8. OUTPUT      → Save to output-dir, optionally publish
-9. CLEANUP     → Remove .content-session/ directory
+1. INIT        -> Parse args, load rules, create session dir
+2. RESEARCH    -> Task(content-research-agent) — skip if --no-research
+3. PLAN        -> Task(content-planner-agent) with research summary
+4. WRITE       -> Task(content-writer-agent) with plan + research
+5. OPTIMIZE    -> Task(content-seo-agent) + Task(content-editor-agent) IN PARALLEL
+6. ASSEMBLE    -> Read all outputs, produce final article
+7. OUTPUT      -> Save to output-dir, optionally publish
+8. CLEANUP     -> Remove .content-session/ directory
 ```
 
 ## Error Handling
 
 - If a subagent fails, log the error and continue with what's available
-- Research failure → proceed with plan (user-provided context may suffice)
-- SEO/Editor failure → use draft as-is with basic frontmatter
-- Visual generation failure → produce article without images
+- Research failure -> proceed with plan (user-provided context may suffice)
+- SEO/Editor failure -> use draft as-is with basic frontmatter
 - Never block the entire pipeline on a single failure
 
-## Context Management (Long-Running Agent Patterns)
+## Pipeline Checklist
+
+Copy and track progress through each phase:
+
+```
+Pipeline Progress:
+- [ ] Phase 0: Parse arguments, load content-rules, create .content-session/
+- [ ] Phase 1: Research (content-research-agent) — skip if --no-research
+- [ ] Phase 2: Plan (content-planner-agent) with research summary
+- [ ] Phase 3: Write (content-writer-agent) with plan + research
+- [ ] Phase 4: Optimize — SEO + Editor agents IN PARALLEL
+- [ ] Phase 5: Assemble final article from all outputs
+- [ ] Phase 6: Save to output-dir, publish if requested
+- [ ] Phase 7: Clean up .content-session/
+```
+
+## Context Management
 
 ### Context Regurgitation
-Before dispatching each subagent, briefly restate in your prompt:
-- Current phase number and what's been completed so far
+Before dispatching each subagent, restate in the Task prompt:
+- Current phase number and what's been completed
 - Key decisions made (chosen angle, title direction, tone calibration)
 - What this subagent needs to accomplish and how its output feeds the next phase
 
-This keeps critical context fresh at the end of the context window where LLM attention is strongest.
-
 ### Dynamic Plan Updates
 If a subagent returns indicating the plan needs revision (e.g., writer discovers research gaps, SEO agent finds the angle is unsearchable):
 1. Parse the update request from the subagent's output
 2. Re-run the affected earlier phase with the new context
 3. Resume the pipeline from the current phase
 4. Maximum **2 plan revisions per session** to prevent infinite loops
-5. Log each revision to `.content-session/revisions.md`
 
 ### File Buffering
-All subagent outputs go to `.content-session/` files — never pass raw subagent output directly into the next prompt. Read only the specific file sections needed for each phase. This keeps the orchestrator's active context lean.
+When constructing Task prompts for subsequent phases, read only the specific sections needed from `.content-session/` files. Summarize key points and reference the scratchpad file path so the subagent can read details itself.
 
 ## Progress Reporting
 
 At each phase transition, report to the user:
 
 ```
-→ Phase 1/6: Researching "{topic}"...
-  ✓ Found 6 sources, identified 3 unique angles
-→ Phase 2/6: Planning article structure...
-  ✓ Outline ready: 5 sections, ~{word_count} words target
-→ Phase 3/6: Writing article...
-  ✓ Draft complete: {actual_word_count} words
-→ Phase 4/6: Optimizing (SEO + Editorial review)...
-  ✓ SEO score: 8.5/10 | Editorial score: 8/10
-→ Phase 5/6: Generating visual content...
-  ✓ 3 images generated ($0.06 total)
-→ Phase 6/6: Assembling final article...
-  ✓ Saved to ./content-output/{slug}.md
-
-📊 Summary:
+-> Phase 1/5: Researching "{topic}"...
+  Done: Found 6 sources, identified 3 unique angles
+-> Phase 2/5: Planning article structure...
+  Done: Outline ready: 5 sections, ~{word_count} words target
+-> Phase 3/5: Writing article...
+  Done: Draft complete: {actual_word_count} words
+-> Phase 4/5: Optimizing (SEO + Editorial review)...
+  Done: SEO score: 8.5/10 | Editorial score: 8/10
+-> Phase 5/5: Assembling final article...
+  Done: Saved to ./content-output/{slug}.md
+
+Summary:
   Words: {count} | Reading Time: {time}
   SEO Score: {score}/10 | Quality: {score}/10
-  Images: {count} | Cost: ${total}
 ```
 
 ## Output Format
@@ -279,12 +248,11 @@ word_count: [actual count]
 reading_time: [X minutes]
 content_type: [type used]
 generated_at: [ISO timestamp]
-images: [list of generated image paths, if any]
 ---
 
 # [Title]
 
-[Full article content with embedded image references]
+[Full article content]
 ```
 
 ## Publishing Integration
@@ -292,10 +260,9 @@ images: [list of generated image paths, if any]
 If `--publish` is specified, after saving the article locally:
 
 1. Determine target platform from flag value
-2. Spawn appropriate publishing subagent:
-   - `wordpress-publisher` for WordPress
-   - `payloadcms-publisher` for PayloadCMS
-   - Use static-site utilities for Docusaurus/Mintlify/Astro
+2. Use the appropriate publishing approach:
+   - WordPress: use the wp MCP tools directly
+   - Other platforms: use platform-specific skills if available
 3. Report published URL to user
 
 ## Example Usage
@@ -304,8 +271,8 @@ If `--publish` is specified, after saving the article locally:
 # Basic article
 /myaidev-method:content-writer "Kubernetes Best Practices for Production"
 
-# Full-featured with visuals
-/myaidev-method:content-writer "Building a RAG Pipeline" --word-count=2500 --type=technical-tutorial --with-images --tone=technical
+# Technical tutorial with custom length
+/myaidev-method:content-writer "Building a RAG Pipeline" --word-count=2500 --type=technical-tutorial --tone=technical
 
 # With publishing
 /myaidev-method:content-writer "Getting Started with Docker" --publish=wordpress --tone=conversational
@@ -316,18 +283,3 @@ If `--publish` is specified, after saving the article locally:
 # Custom output location
 /myaidev-method:content-writer "API Design Patterns" --output-dir=./blog/posts --keywords="api design,rest best practices"
 ```
-
-## Quality Checklist (Applied by Editor Agent)
-
-- [ ] Title includes primary keyword and is compelling
-- [ ] Introduction hooks reader within 2 sentences
-- [ ] Content addresses user intent thoroughly
-- [ ] Facts are accurate and attributed
-- [ ] Heading hierarchy is proper (H1 → H2 → H3)
-- [ ] Content is scannable (varied formatting)
-- [ ] Keywords integrated naturally (not stuffed)
-- [ ] Meta description summarizes effectively
-- [ ] Conclusion provides value and next steps
-- [ ] Tone consistent throughout
-- [ ] Original value — not just repackaged existing content
-