create-hq 5.1.0 → 5.2.0

package/template/workers/dev-team/infra-dev/skills/create-dockerfile.md

@@ -1,62 +0,0 @@
-# create-dockerfile
-
-Create optimized Dockerfile for project.
-
-## Arguments
-
-`$ARGUMENTS` = `--repo <path>` (required)
-
-Optional:
-- `--type <nodejs|python|go|rust>` - Project type
-- `--multi-stage` - Use multi-stage build
-- `--target <dev|prod>` - Build target
-
-## Process
-
-1. Detect project type and dependencies
-2. Choose base image (prefer slim/alpine)
-3. Design build stages:
-   - Dependencies stage
-   - Build stage
-   - Production stage
-4. Optimize layer caching
-5. Add security best practices:
-   - Non-root user
-   - Minimal final image
-   - No secrets in image
-6. Generate Dockerfile
-7. Generate .dockerignore
-8. Present for human approval
-
-## Output
-
-- `Dockerfile`
-- `.dockerignore`
-- `docker-compose.yml` (if needed)
-
-## Node.js Template
-
-```dockerfile
-# Build stage
-FROM node:20-alpine AS builder
-WORKDIR /app
-COPY package*.json ./
-RUN npm ci --only=production
-
-# Production stage
-FROM node:20-alpine
-WORKDIR /app
-RUN addgroup -g 1001 -S nodejs && adduser -S nodejs -u 1001
-COPY --from=builder /app/node_modules ./node_modules
-COPY --chown=nodejs:nodejs . .
-USER nodejs
-EXPOSE 3000
-CMD ["node", "dist/index.js"]
-```
-
-## Best Practices
-
-- Use specific version tags, not latest
-- Order commands for cache efficiency
-- COPY specific files, not entire context
-- Use .dockerignore for node_modules, .git, etc.

package/template/workers/dev-team/infra-dev/skills/setup-cicd.md

@@ -1,63 +0,0 @@
-# setup-cicd
-
-Set up CI/CD pipeline for repository.
-
-## Arguments
-
-`$ARGUMENTS` = `--repo <path>` (required)
-
-Optional:
-- `--platform <github|gitlab|bitbucket>` - CI platform (default: github)
-- `--type <nodejs|python|go|rust>` - Project type
-- `--include-deploy` - Include deployment stage
-
-## Process
-
-1. Detect project type from package.json/requirements.txt/go.mod/Cargo.toml
-2. Analyze existing workflow files (if any)
-3. Design pipeline stages:
-   - Build
-   - Lint
-   - Test
-   - Security scan
-   - Deploy (if --include-deploy)
-4. Generate workflow file(s)
-5. Add branch protection rules (suggest)
-6. Present for human approval
-
-## Output
-
-- `.github/workflows/ci.yml` (or equivalent)
-- Branch protection recommendations
-- Required secrets list
-
-## GitHub Actions Template
-
-```yaml
-name: CI
-on:
-  push:
-    branches: [main, develop]
-  pull_request:
-    branches: [main]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-          cache: 'npm'
-      - run: npm ci
-      - run: npm run build
-      - run: npm run lint
-      - run: npm test
-```
-
-## Human Checkpoints
-
-- Approve workflow before commit
-- Approve any deployment configurations
-- Review secrets requirements

package/template/workers/dev-team/infra-dev/src/index.ts

@@ -1,55 +0,0 @@
-#!/usr/bin/env node
-import { Command } from 'commander';
-
-const program = new Command();
-
-program
-  .name('infra-dev')
-  .description('CI/CD pipelines, deployment configurations, and monitoring')
-  .version('1.0.0');
-
-program
-  .command('setup-cicd')
-  .description('Set up CI/CD pipeline')
-  .requiredOption('--repo <path>', 'Target repository')
-  .option('--platform <platform>', 'CI platform: github|gitlab|bitbucket', 'github')
-  .option('--type <type>', 'Project type: nodejs|python|go|rust')
-  .option('--include-deploy', 'Include deployment stage')
-  .action(async (options) => {
-    console.log('setup-cicd:', options);
-  });
-
-program
-  .command('create-dockerfile')
-  .description('Create optimized Dockerfile')
-  .requiredOption('--repo <path>', 'Target repository')
-  .option('--type <type>', 'Project type: nodejs|python|go|rust')
-  .option('--multi-stage', 'Use multi-stage build')
-  .option('--target <target>', 'Build target: dev|prod', 'prod')
-  .action(async (options) => {
-    console.log('create-dockerfile:', options);
-  });
-
-program
-  .command('add-monitoring')
-  .description('Add monitoring and observability')
-  .requiredOption('--repo <path>', 'Target repository')
-  .option('--type <type>', 'Type: metrics|logs|traces|all', 'all')
-  .option('--provider <provider>', 'Provider: datadog|newrelic|prometheus|otel')
-  .option('--alerts', 'Include alerting rules')
-  .action(async (options) => {
-    console.log('add-monitoring:', options);
-  });
-
-program
-  .command('configure-deployment')
-  .description('Configure deployment')
-  .requiredOption('--repo <path>', 'Target repository')
-  .option('--platform <platform>', 'Platform: vercel|railway|fly|aws|gcp')
-  .option('--env <env>', 'Environment: staging|production')
-  .option('--preview', 'Enable preview deployments')
-  .action(async (options) => {
-    console.log('configure-deployment:', options);
-  });
-
-program.parse();

package/template/workers/dev-team/infra-dev/src/mcp-server.ts

@@ -1,82 +0,0 @@
-#!/usr/bin/env node
-import { Server } from '@modelcontextprotocol/sdk/server/index.js';
-import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
-import { CallToolRequestSchema, ListToolsRequestSchema } from '@modelcontextprotocol/sdk/types.js';
-
-const server = new Server(
-  { name: 'infra-dev', version: '1.0.0' },
-  { capabilities: { tools: {} } }
-);
-
-server.setRequestHandler(ListToolsRequestSchema, async () => ({
-  tools: [
-    {
-      name: 'setup_cicd',
-      description: 'Set up CI/CD pipeline for repository',
-      inputSchema: {
-        type: 'object',
-        properties: {
-          repo: { type: 'string', description: 'Target repository path' },
-          platform: { type: 'string', enum: ['github', 'gitlab', 'bitbucket'], description: 'CI platform' },
-          type: { type: 'string', enum: ['nodejs', 'python', 'go', 'rust'], description: 'Project type' },
-          include_deploy: { type: 'boolean', description: 'Include deployment stage' },
-        },
-        required: ['repo'],
-      },
-    },
-    {
-      name: 'create_dockerfile',
-      description: 'Create optimized Dockerfile for project',
-      inputSchema: {
-        type: 'object',
-        properties: {
-          repo: { type: 'string', description: 'Target repository path' },
-          type: { type: 'string', enum: ['nodejs', 'python', 'go', 'rust'], description: 'Project type' },
-          multi_stage: { type: 'boolean', description: 'Use multi-stage build' },
-          target: { type: 'string', enum: ['dev', 'prod'], description: 'Build target' },
-        },
-        required: ['repo'],
-      },
-    },
-    {
-      name: 'add_monitoring',
-      description: 'Add monitoring and observability to application',
-      inputSchema: {
-        type: 'object',
-        properties: {
-          repo: { type: 'string', description: 'Target repository path' },
-          type: { type: 'string', enum: ['metrics', 'logs', 'traces', 'all'], description: 'Monitoring type' },
-          provider: { type: 'string', enum: ['datadog', 'newrelic', 'prometheus', 'otel'], description: 'Monitoring provider' },
-          alerts: { type: 'boolean', description: 'Include alerting rules' },
-        },
-        required: ['repo'],
-      },
-    },
-    {
-      name: 'configure_deployment',
-      description: 'Configure deployment for application',
-      inputSchema: {
-        type: 'object',
-        properties: {
-          repo: { type: 'string', description: 'Target repository path' },
-          platform: { type: 'string', enum: ['vercel', 'railway', 'fly', 'aws', 'gcp'], description: 'Deployment platform' },
-          env: { type: 'string', enum: ['staging', 'production'], description: 'Target environment' },
-          preview: { type: 'boolean', description: 'Enable preview deployments' },
-        },
-        required: ['repo'],
-      },
-    },
-  ],
-}));
-
-server.setRequestHandler(CallToolRequestSchema, async (request) => {
-  const { name, arguments: args } = request.params;
-  return { content: [{ type: 'text', text: `Tool ${name} called with: ${JSON.stringify(args)}` }] };
-});
-
-async function main() {
-  const transport = new StdioServerTransport();
-  await server.connect(transport);
-}
-
-main().catch(console.error);

package/template/workers/dev-team/infra-dev/tsconfig.json

@@ -1,19 +0,0 @@
-{
-  "compilerOptions": {
-    "target": "ES2022",
-    "module": "NodeNext",
-    "moduleResolution": "NodeNext",
-    "lib": ["ES2022"],
-    "outDir": "./dist",
-    "rootDir": "./src",
-    "strict": true,
-    "esModuleInterop": true,
-    "skipLibCheck": true,
-    "forceConsistentCasingInFileNames": true,
-    "resolveJsonModule": true,
-    "declaration": true,
-    "sourceMap": true
-  },
-  "include": ["src/**/*"],
-  "exclude": ["node_modules", "dist"]
-}

package/template/workers/dev-team/infra-dev/worker.yaml

@@ -1,92 +0,0 @@
-worker:
-  id: infra-dev
-  name: "Infrastructure Developer"
-  description: "CI/CD pipelines, deployment configurations, and monitoring setup"
-  type: CodeWorker
-  version: "1.0"
-  team: dev-team
-
-execution:
-  mode: on_demand
-  max_runtime: 20m
-  retry_attempts: 2
-  spawn_method: task_tool
-
-context:
-  base:
-    - workers/public/dev-team/infra-dev/skills/
-    - knowledge/public/dev-team/patterns/infra/
-    - knowledge/public/dev-team/workflows/deployment.md
-  dynamic:
-    - pattern: "{target_repo}/.github/"
-      when: always
-    - pattern: "{target_repo}/docker*"
-      when: "task.involves_docker"
-    - pattern: "{target_repo}/terraform/"
-      when: "task.involves_terraform"
-    - pattern: "{target_repo}/k8s/"
-      when: "task.involves_kubernetes"
-    - pattern: "{target_repo}/package.json"
-      when: always
-  exclude:
-    - node_modules/
-    - dist/
-    - "*.log"
-    - src/
-    - tests/
-
-skills:
-  - id: setup-cicd
-    file: skills/setup-cicd.md
-  - id: create-dockerfile
-    file: skills/create-dockerfile.md
-  - id: add-monitoring
-    file: skills/add-monitoring.md
-  - id: configure-deployment
-    file: skills/configure-deployment.md
-
-verification:
-  post_execute:
-    - check: yaml_lint
-      command: npx yaml-lint .github/workflows/*.yml
-    - check: dockerfile_lint
-      command: docker run --rm -i hadolint/hadolint < Dockerfile
-  approval_required: true
-  human_checkpoints:
-    - before_deploy
-    - on_production_change
-
-external_skills:
-  - vercel/github-actions-templates
-  - vercel/terraform-module-library
-  - vercel/monitoring
-
-mcp:
-  server:
-    command: node
-    args: [dist/mcp-server.js]
-  tools:
-    - setup_cicd
-    - create_dockerfile
-    - add_monitoring
-    - configure_deployment
-
-# State Machine (Loom pattern)
-state_machine:
-  enabled: true
-  max_retries: 1
-  hooks:
-    post_execute:
-      - auto_checkpoint
-      - log_metrics
-    on_error:
-      - log_error
-      - checkpoint_error_state
-
-reporting:
-  on_complete:
-    - log_changes
-    - extract_learnings
-  metrics:
-    - pipeline_execution_time
-    - deployment_success_rate

package/template/workers/dev-team/knowledge-curator/package.json

@@ -1,24 +0,0 @@
-{
-  "name": "@hq/knowledge-curator",
-  "version": "1.0.0",
-  "description": "Knowledge curator worker - process learnings, maintain documentation",
-  "type": "module",
-  "main": "dist/index.js",
-  "bin": {
-    "knowledge-curator": "dist/index.js"
-  },
-  "scripts": {
-    "build": "tsc",
-    "typecheck": "tsc --noEmit",
-    "start": "node dist/index.js",
-    "mcp": "node dist/mcp-server.js"
-  },
-  "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.0.0",
-    "commander": "^12.0.0"
-  },
-  "devDependencies": {
-    "@types/node": "^20.0.0",
-    "typescript": "^5.0.0"
-  }
-}

package/template/workers/dev-team/knowledge-curator/skills/curate-troubleshooting.md

@@ -1,63 +0,0 @@
-# curate-troubleshooting
-
-Add or update troubleshooting entries for common issues.
-
-## Arguments
-
-`$ARGUMENTS` = `--issue <description>` (required)
-
-Optional:
-- `--solution <description>` - Solution that worked
-- `--category <category>` - Issue category
-- `--tags <tags>` - Comma-separated tags
-
-## Process
-
-1. Search existing troubleshooting for similar issues
-2. If exists: update with new information
-3. If new: create entry with:
-   - Symptoms
-   - Root cause
-   - Solution
-   - Prevention
-4. Add relevant tags for searchability
-5. Present to human for approval
-6. Write to `knowledge/public/dev-team/troubleshooting/`
-
-## Entry Format
-
-```markdown
-## Issue: Brief Description
-
-### Symptoms
-- What you observe
-
-### Root Cause
-Why this happens
-
-### Solution
-\`\`\`bash
-# Commands or code to fix
-\`\`\`
-
-### Prevention
-How to avoid this in future
-
-### Tags
-`error`, `database`, `timeout`
-```
-
-## Categories
-
-- `build` - Build/compile errors
-- `runtime` - Runtime errors
-- `database` - Database issues
-- `network` - Network/API issues
-- `auth` - Authentication/authorization
-- `deploy` - Deployment issues
-- `performance` - Performance problems
-
-## Output
-
-- Troubleshooting entry created/updated
-- Summary of changes

package/template/workers/dev-team/knowledge-curator/skills/process-learnings.md

@@ -1,61 +0,0 @@
-# process-learnings
-
-Process learnings from completed tasks and route to appropriate locations.
-
-## Arguments
-
-`$ARGUMENTS` = `--learnings <json>` (required)
-
-Optional:
-- `--project <name>` - Source project
-- `--worker <id>` - Source worker
-- `--task <id>` - Source task ID
-
-## Learnings Format
-
-```json
-{
-  "what_worked": ["Description of successful approach"],
-  "what_failed": ["Description of failed approach", "Why it failed"],
-  "patterns_discovered": ["Reusable pattern description"],
-  "context_notes": ["Important context for future reference"],
-  "worker_specific": ["Learnings specific to worker type"]
-}
-```
-
-## Process
-
-1. Parse incoming learnings
-2. Categorize each learning:
-   - **Project-specific**: Store in `projects/{name}/learnings/`
-   - **Worker-specific**: Store in `workers/{worker}/knowledge/`
-   - **General pattern**: Store in `knowledge/public/dev-team/patterns/`
-   - **Troubleshooting**: Store in `knowledge/public/dev-team/troubleshooting/`
-3. Check for duplicates/conflicts with existing knowledge
-4. Format as markdown
-5. Present to human for approval
-6. Write to appropriate location
-7. Update related CLAUDE.md files if needed
-
-## Routing Rules
-
-| Category | Destination |
-|----------|-------------|
-| Project conventions | `projects/{name}/learnings/conventions.md` |
-| Bug fixes | `projects/{name}/learnings/bugs-fixed.md` |
-| Backend patterns | `knowledge/public/dev-team/patterns/backend/` |
-| Frontend patterns | `knowledge/public/dev-team/patterns/frontend/` |
-| Database patterns | `knowledge/public/dev-team/patterns/database/` |
-| Worker tips | `workers/public/dev-team/{worker}/knowledge/` |
-| Error solutions | `knowledge/public/dev-team/troubleshooting/` |
-
-## Output
-
-- Files created/updated
-- Summary of knowledge added
-
-## Human Checkpoints
-
-- Approve categorization
-- Approve content before writing
-- Confirm duplicate handling

package/template/workers/dev-team/knowledge-curator/skills/sync-documentation.md

@@ -1,76 +0,0 @@
-# sync-documentation
-
-Sync and update documentation across the HQ system.
-
-## Arguments
-
-`$ARGUMENTS` = `--scope <scope>` (required)
-
-Optional:
-- `--target <path>` - Specific file to update
-- `--dry-run` - Preview changes without writing
-
-## Scopes
-
-- `worker` - Update worker CLAUDE.md files
-- `project` - Update project documentation
-- `knowledge` - Sync knowledge base indices
-- `all` - Full documentation sync
-
-## Process
-
-1. Scan scope for documentation files
-2. Identify outdated or missing content:
-   - Worker capabilities not documented
-   - Skills not listed
-   - Stale references
-3. Generate updates
-4. Present changes to human
-5. Apply updates
-
-## Documentation Standards
-
-### Worker CLAUDE.md
-```markdown
-# Worker Name
-
-One-line description.
-
-## Capabilities
-- Capability 1
-- Capability 2
-
-## Skills
-| Skill | Description |
-|-------|-------------|
-| skill-1 | What it does |
-
-## Context
-What the worker needs access to.
-
-## Usage
-How to invoke the worker.
-```
-
-### Project Documentation
-```markdown
-# Project Name
-
-## Overview
-Brief description.
-
-## Structure
-Key directories and files.
-
-## Conventions
-Project-specific patterns.
-
-## Learnings
-Link to learnings directory.
-```
-
-## Output
-
-- List of files updated
-- Summary of changes
-- Warnings for missing documentation

package/template/workers/dev-team/knowledge-curator/skills/update-patterns.md

@@ -1,63 +0,0 @@
-# update-patterns
-
-Update or create reusable patterns in the knowledge base.
-
-## Arguments
-
-`$ARGUMENTS` = `--category <category>` (required)
-
-Optional:
-- `--pattern <name>` - Specific pattern to update
-- `--content <markdown>` - Pattern content
-
-## Categories
-
-- `backend` - Backend development patterns
-- `frontend` - Frontend development patterns
-- `database` - Database patterns
-- `infra` - Infrastructure patterns
-- `testing` - Testing patterns
-- `security` - Security patterns
-
-## Process
-
-1. Read existing patterns in category
-2. Identify where new pattern fits:
-   - New file
-   - Addition to existing file
-   - Replacement of outdated pattern
-3. Format pattern with:
-   - Title
-   - When to use
-   - Implementation example
-   - Caveats/gotchas
-4. Present to human for approval
-5. Write pattern
-
-## Pattern Format
-
-```markdown
-## Pattern Name
-
-### When to Use
-- Situation A
-- Situation B
-
-### Implementation
-
-\`\`\`typescript
-// Example code
-\`\`\`
-
-### Caveats
-- Important consideration 1
-- Important consideration 2
-
-### Related Patterns
-- [Other Pattern](link)
-```
-
-## Output
-
-- Pattern file created/updated
-- Summary of changes