create-hq 6.0.0 → 10.0.0

package/template/starter-projects/code-worker/README.md

@@ -1,97 +0,0 @@
-# Code Worker Setup
-
-Set up a Ralph loop for autonomous code implementation on your projects.
-
-## What You'll Build
-
-- **Code Worker**: Implements features from PRDs autonomously
-- **Back Pressure System**: Verification (tests, types, build) before commits
-- **Ralph Loop**: Orchestrated implementation with fresh context per task
-
-## How It Works
-
-The Ralph methodology uses a simple loop:
-1. Pick a task from PRD (where `passes: false`)
-2. Implement it in a fresh context
-3. Run back pressure (typecheck, build, tests)
-4. If passing, commit and mark complete
-5. Repeat until all tasks pass
-
-## Quick Start
-
-1. Run `/setup` and select "Code Worker"
-2. Follow the PRD tasks in order:
-   - Configure repository connection
-   - Create first PRD with features
-   - Run first Ralph loop
-
-## Files Created
-
-```
-workers/code/{project}/
-├── worker.yaml      # Worker configuration
-
-projects/{project}/
-├── prd.json         # Feature tracking
-└── README.md        # Project documentation
-
-workspace/checkpoints/
-└── {feature-id}.json # Task completion records
-```
-
-## Writing Good PRDs
-
-Each feature should be:
-- **Atomic**: One thing, not multiple
-- **Verifiable**: Clear acceptance criteria
-- **Scoped**: Files to modify listed upfront
-
-Example feature:
-```json
-{
-  "id": "F1",
-  "title": "Add user authentication",
-  "description": "Implement JWT-based auth with login/logout endpoints",
-  "acceptance_criteria": [
-    "POST /login returns JWT token",
-    "POST /logout invalidates token",
-    "Protected routes return 401 without valid token"
-  ],
-  "files": ["src/auth.ts", "src/routes/auth.ts"],
-  "passes": false
-}
-```
-
-## Back Pressure Commands
-
-Customize in worker.yaml based on your stack:
-
-**TypeScript/Node:**
-```yaml
-verification:
-  post_execute:
-    - check: typecheck
-      command: npm run typecheck
-      must_pass: true
-    - check: build
-      command: npm run build
-      must_pass: true
-```
-
-**Python:**
-```yaml
-verification:
-  post_execute:
-    - check: typecheck
-      command: mypy .
-      must_pass: true
-    - check: test
-      command: pytest
-      must_pass: true
-```
-
-## Next Steps After Setup
-
-- Run `/ralph-loop` to implement features automatically
-- Use `/checkpoint` to save progress mid-task
-- Add more features to prd.json as you go

package/template/starter-projects/code-worker/prd.json

@@ -1,45 +0,0 @@
-{
-  "project": "code-worker-setup",
-  "goal": "Set up Ralph loop for autonomous code implementation on a project",
-  "success_criteria": "Code worker running Ralph loops, back pressure passing, features being committed automatically",
-  "features": [
-    {
-      "id": "repo-setup",
-      "title": "Configure repository connection",
-      "description": "Link code worker to your project repository with proper verification commands",
-      "acceptance_criteria": [
-        "worker.yaml has correct repo/project path",
-        "Back pressure commands defined (typecheck, build, test)",
-        "Verification passes when run locally"
-      ],
-      "files": ["workers/code/{project}/worker.yaml"],
-      "passes": false
-    },
-    {
-      "id": "first-prd",
-      "title": "Create first PRD",
-      "description": "Define features for Ralph loop to implement",
-      "acceptance_criteria": [
-        "prd.json has project name and goal",
-        "At least 3 features defined",
-        "Each feature has acceptance_criteria array",
-        "All features start with passes: false"
-      ],
-      "files": ["projects/{project}/prd.json"],
-      "passes": false
-    },
-    {
-      "id": "first-loop",
-      "title": "Run first Ralph loop",
-      "description": "Execute /ralph-loop and complete one feature",
-      "acceptance_criteria": [
-        "Sub-agent spawned successfully",
-        "Back pressure checks pass",
-        "Checkpoint written to workspace/checkpoints/",
-        "Feature marked passes: true in PRD"
-      ],
-      "files": [],
-      "passes": false
-    }
-  ]
-}

package/template/starter-projects/personal-assistant/README.md

@@ -1,42 +0,0 @@
-# Personal Assistant Setup
-
-Set up an email digest worker that creates a "Presidential Daily Brief" from your unread emails.
-
-## What You'll Build
-
-- **Email Worker**: Fetches and classifies your emails
-- **Daily Digest**: HTML summary with urgent/actionable/fyi sections
-- **Automated Schedule**: Runs daily at your preferred time
-
-## Prerequisites
-
-- Email account(s) you want to digest
-- (Optional) API credentials for your email provider
-
-## Quick Start
-
-1. Run `/setup` and select "Personal Assistant"
-2. Follow the PRD tasks in order:
-   - Configure email accounts
-   - Customize worker schedule
-   - Run first digest
-
-## Files Created
-
-```
-workers/assistant/email/
-├── worker.yaml      # Worker configuration
-└── prd.json         # Task tracking
-
-settings/email/
-└── accounts.json    # Your email accounts (gitignored)
-
-workspace/digests/
-└── {date}-pdb.html  # Generated digests
-```
-
-## Next Steps After Setup
-
-- Run `/digest` to generate a digest on-demand
-- Adjust classification rules in worker.yaml
-- Add more email accounts as needed

package/template/starter-projects/personal-assistant/prd.json

@@ -1,43 +0,0 @@
-{
-  "project": "personal-assistant-setup",
-  "goal": "Set up email digest and task management workers",
-  "success_criteria": "Daily email digest running automatically, classifying emails correctly",
-  "features": [
-    {
-      "id": "email-config",
-      "title": "Configure email accounts",
-      "description": "Add email accounts to settings/email/accounts.json for the digest worker to access",
-      "acceptance_criteria": [
-        "accounts.json exists with at least one account",
-        "Account has name, email, and provider fields",
-        "Provider is one of: gmail, outlook, imap"
-      ],
-      "files": ["settings/email/accounts.json"],
-      "passes": false
-    },
-    {
-      "id": "email-worker",
-      "title": "Customize email worker",
-      "description": "Update email worker settings to match your schedule and preferences",
-      "acceptance_criteria": [
-        "worker.yaml has correct schedule (morning or evening)",
-        "Digest format matches preferences",
-        "Output destination is set correctly"
-      ],
-      "files": ["workers/assistant/email/worker.yaml"],
-      "passes": false
-    },
-    {
-      "id": "first-digest",
-      "title": "Run first email digest",
-      "description": "Execute email worker manually and generate first digest to verify setup",
-      "acceptance_criteria": [
-        "Digest generated in workspace/digests/",
-        "Classification working (urgent/actionable/fyi/archive)",
-        "HTML opens correctly in browser"
-      ],
-      "files": [],
-      "passes": false
-    }
-  ]
-}

package/template/starter-projects/social-media/README.md

@@ -1,60 +0,0 @@
-# Social Media Worker Setup
-
-Set up a content worker that helps you maintain a consistent social media presence.
-
-## What You'll Build
-
-- **Voice Style Guide**: Document your authentic writing voice
-- **Content Worker**: Generates drafts matching your style
-- **Content Queue**: Organized pipeline of ideas → drafts → posts
-
-## Supported Platforms
-
-- X (Twitter)
-- LinkedIn
-- (Add more as needed)
-
-## Quick Start
-
-1. Run `/setup` and select "Social Media Worker"
-2. Follow the PRD tasks in order:
-   - Create voice style guide
-   - Seed content queue with ideas
-   - Generate first draft
-
-## Files Created
-
-```
-knowledge/{your-name}/
-├── profile.md       # Your identity and positioning
-└── voice-style.md   # Writing voice documentation
-
-workers/social/{platform}/
-├── worker.yaml      # Worker configuration
-└── queue.json       # Content queue
-
-social-content/drafts/
-├── INDEX.md         # Draft inventory
-├── x/               # X/Twitter drafts
-└── linkedin/        # LinkedIn drafts
-```
-
-## Content Commands
-
-- `/contentidea {idea}` - Transform idea into full content suite
-- `/suggestposts` - Get strategic posting suggestions
-- `/scheduleposts` - Pick what to post based on context
-
-## Voice Style Tips
-
-Your voice-style.md should include:
-- **Tone**: Professional? Casual? Direct?
-- **Patterns**: Phrases you use, sentence structures you prefer
-- **Avoid**: Things that don't sound like you
-- **Examples**: Real posts that capture your voice
-
-## Next Steps After Setup
-
-- Run `/suggestposts` to get content ideas
-- Run `/contentidea {topic}` to build out an idea
-- Run `/scheduleposts` when ready to post

package/template/starter-projects/social-media/prd.json

@@ -1,43 +0,0 @@
-{
-  "project": "social-presence-setup",
-  "goal": "Set up social media content worker for consistent posting with your authentic voice",
-  "success_criteria": "Content queue established, voice guide documented, first draft generated matching your style",
-  "features": [
-    {
-      "id": "voice-guide",
-      "title": "Create voice style guide",
-      "description": "Document your writing voice so content stays consistent and authentic",
-      "acceptance_criteria": [
-        "voice-style.md has tone section",
-        "Includes 3+ example phrases that sound like you",
-        "Lists things to avoid in your writing"
-      ],
-      "files": ["knowledge/{your-name}/voice-style.md"],
-      "passes": false
-    },
-    {
-      "id": "content-queue",
-      "title": "Seed content queue",
-      "description": "Add initial content ideas to the queue to get started",
-      "acceptance_criteria": [
-        "queue.json has at least 3 content ideas",
-        "Each idea has topic, type (post/thread/article), and notes",
-        "Ideas span different themes/topics"
-      ],
-      "files": ["workers/social/{platform}/queue.json"],
-      "passes": false
-    },
-    {
-      "id": "first-draft",
-      "title": "Generate first content draft",
-      "description": "Run social worker or /contentidea to create first draft",
-      "acceptance_criteria": [
-        "Draft saved to workspace/drafts/social/",
-        "Matches voice style guide",
-        "Within platform character limits"
-      ],
-      "files": [],
-      "passes": false
-    }
-  ]
-}

package/template/workers/content-brand/README.md

@@ -1,59 +0,0 @@
-# Content Worker: Brand Voice
-
-Brand voice analysis worker for ExampleCo content.
-
-## Purpose
-
-Analyzes website content for brand voice consistency, tone alignment, and messaging effectiveness. Ensures all content reflects ExampleCo's professional-yet-approachable brand identity.
-
-## Skills
-
-| Skill | Description |
-|-------|-------------|
-| voice-analysis | Evaluate overall brand voice consistency |
-| tone-check | Check tone matches context (page type, audience) |
-| messaging-alignment | Verify key messages are represented |
-
-## Knowledge Sources
-
-- `companies/example-company/knowledge/brand-guidelines.md` - Core brand voice guide
-- `companies/example-company/knowledge/messaging/` - Messaging by audience/vertical
-
-## Scoring Categories
-
-| Category | Weight | Description |
-|----------|--------|-------------|
-| Tone Alignment | 30% | Matches professional-approachable balance |
-| Messaging Consistency | 30% | Key messages present and accurate |
-| Jargon Appropriateness | 20% | Technical language at right level |
-| Trust Elements | 20% | Proof points, credentials, social proof |
-
-## Brand Voice Characteristics
-
-1. **Professional but Approachable** - Enterprise credibility without coldness
-2. **Confident without Arrogance** - Authority without dismissiveness
-3. **Technical with Clarity** - Accuracy without confusion
-4. **Trust-Building** - Proof-driven claims, no hype
-
-## Usage
-
-```bash
-# Run via HQ
-/run content-brand --page homepage
-
-# Or directly
-cd workers/content-brand
-npx ts-node src/analyze.ts --input content/homepage.json
-```
-
-## Output
-
-Reports go to `workspace/reports/content/` with format:
-- `{date}-content-brand-{page}.md`
-
-## Integration
-
-Part of the Content Team worker group. Works alongside:
-- content-sales (conversion analysis)
-- content-product (accuracy verification)
-- content-legal (compliance checking)

package/template/workers/content-brand/skills/messaging-alignment.md

@@ -1,91 +0,0 @@
-# Skill: Messaging Alignment
-
-Verify content aligns with approved brand messaging and key messages.
-
-## Input
-
-- Page content JSON
-- Brand messaging guidelines
-- Key message library
-
-## Process
-
-1. **Load key messages**
-   - Core value proposition
-   - Product positioning statements
-   - Audience-specific messages
-   - Proof points and stats
-
-2. **Scan content for alignment**
-   - Key message presence
-   - Accurate representation
-   - Consistent terminology
-   - No conflicting claims
-
-3. **Identify gaps**
-   - Missing key messages
-   - Diluted messaging
-   - Off-brand statements
-
-4. **Score alignment**
-   - Message coverage
-   - Accuracy
-   - Consistency
-
-## Key Message Categories
-
-### Core Value Proposition
-- What ExampleCo does
-- Who it's for
-- Why it matters
-- How it's different
-
-### Product Messaging
-- Feature descriptions
-- Benefit statements
-- Use case framing
-- Technical capabilities
-
-### Audience-Specific
-- Banking/Credit Union focus
-- Healthcare positioning
-- Enterprise requirements
-- Security/Compliance emphasis
-
-### Proof Points
-- Customer metrics
-- Industry recognition
-- Security certifications
-- Case study references
-
-## Scoring Criteria
-
-| Criterion | Weight | Description |
-|-----------|--------|-------------|
-| Coverage | 30% | Key messages present |
-| Accuracy | 30% | Messages stated correctly |
-| Consistency | 20% | Same terms throughout |
-| Prominence | 20% | Messages visible, not buried |
-
-## Output
-
-```yaml
-alignment_score: 85
-key_messages:
-  present:
-    - "Enterprise AI platform"
-    - "Banking-focused"
-    - "SOC2 certified"
-  missing:
-    - "Implementation support"
-  inaccurate:
-    - message: "Industry leader"
-      issue: "Claim not substantiated on page"
-terminology:
-  consistent:
-    - "ExampleCo OS" (used 4x)
-  inconsistent:
-    - term: "AI assistant"
-      variants: ["AI helper", "virtual assistant", "bot"]
-      recommendation: "Standardize on 'AI assistant'"
-```

package/template/workers/content-brand/skills/tone-check.md

@@ -1,76 +0,0 @@
-# Skill: Tone Check
-
-Verify tone matches page context and target audience.
-
-## Input
-
-- Page content JSON
-- Page type (homepage, product, solutions, etc.)
-- Target audience (if specified)
-
-## Process
-
-1. **Identify page context**
-   - Page type from URL/metadata
-   - Target audience from content signals
-   - Conversion goal
-
-2. **Define expected tone**
-   - Homepage: Confident, welcoming, high-level
-   - Product pages: Detailed, technical, benefit-focused
-   - Solutions pages: Empathetic, problem-aware, specific
-   - About pages: Authentic, credible, human
-
-3. **Analyze actual tone**
-   - Sentence structure (formal vs casual)
-   - Word choice complexity
-   - Emotional register
-   - Call-to-action intensity
-
-4. **Compare and score**
-   - Match percentage
-   - Deviation severity
-   - Context appropriateness
-
-## Tone Expectations by Page Type
-
-### Homepage
-- Confident but not boastful
-- Welcoming, inclusive
-- Clear value proposition
-- Light on details, heavy on benefits
-
-### Product Pages
-- Technical accuracy
-- Feature-benefit connections
-- Use case clarity
-- Appropriate depth
-
-### Solutions Pages
-- Problem acknowledgment
-- Empathy for pain points
-- Specific to vertical/audience
-- Proof points relevant to context
-
-### Legal/Compliance Pages
-- Formal, precise
-- No marketing language
-- Clear and unambiguous
-- Properly structured
-
-## Output
-
-```yaml
-tone_score: 76
-page_type: "product"
-expected_tone: "technical, benefit-focused"
-actual_tone: "promotional, feature-heavy"
-mismatches:
-  - element: "Product description"
-    expected: "Specific technical capabilities"
-    actual: "Generic marketing language"
-    impact: "medium"
-recommendations:
-  - "Add specific metrics and use cases"
-  - "Reduce promotional adjectives"
-```

package/template/workers/content-brand/skills/voice-analysis.md

@@ -1,68 +0,0 @@
-# Skill: Voice Analysis
-
-Evaluate overall brand voice consistency across page content.
-
-## Input
-
-Page content JSON with extracted text sections.
-
-## Process
-
-1. **Extract all text elements**
-   - Headings (H1-H6)
-   - Paragraphs
-   - CTAs and buttons
-   - List items
-
-2. **Analyze voice characteristics**
-   - Professional tone markers
-   - Approachability indicators
-   - Confidence level (without arrogance)
-   - Technical clarity
-
-3. **Score each characteristic**
-   - 0-25: Poor alignment
-   - 26-50: Needs improvement
-   - 51-75: Acceptable
-   - 76-100: Strong alignment
-
-4. **Identify deviations**
-   - Flag overly casual language
-   - Flag aggressive sales language
-   - Flag inconsistent tone shifts
-
-## Scoring Rubric
-
-### Professional Markers (positive)
-- Industry-appropriate terminology
-- Clear, direct statements
-- Data-backed claims
-- Formal structure
-
-### Approachability Markers (positive)
-- Second person ("you", "your")
-- Benefit-focused language
-- Conversational clarity
-- Empathetic acknowledgment
-
-### Red Flags (negative)
-- Hyperbole ("revolutionary", "game-changing")
-- Urgency pressure ("act now", "don't miss")
-- Unexplained acronyms
-- Jargon overload
-
-## Output
-
-```yaml
-voice_score: 82
-characteristics:
-  professional: 85
-  approachable: 78
-  confident: 80
-  clear: 84
-deviations:
-  - location: "Hero section"
-    issue: "Overly promotional language"
-    evidence: "Revolutionary AI that transforms everything"
-    suggestion: "Focus on specific, provable benefits"
-```