@specforge/mcp 3.2.3 → 3.3.1

package/src/cli/templates/agents/content/task-type/sfag-schema-designer.ts

@@ -1,132 +0,0 @@
-/**
- * SFAG-Schema-Designer Agent Template
- *
- * Specialized agent for database schema design and data modeling.
- */
-
-import type { AgentTemplate } from '../../../../commands/scaffold/agent-types.js';
-
-export const SFAG_SCHEMA_DESIGNER: AgentTemplate = {
-  name: 'sfag-schema-designer',
-  description: 'Database schema, migrations, queries, indexes',
-  triggerDescription: `Use this agent for database schema design, migrations, query optimization, and data modeling tasks.
-
-<example>
-Context: User needs to design a new data model
-user: "Design a schema for a multi-tenant SaaS application with organizations and users"
-assistant: "I'll use the sfag-schema-designer agent to design an appropriate schema for your multi-tenant application."
-</example>
-
-<example>
-Context: User wants to add a new database table
-user: "Add a comments table that references posts and users"
-assistant: "Let me use the sfag-schema-designer agent to design and implement the comments schema with proper relationships."
-</example>`,
-  model: 'sonnet',
-  color: 'cyan',
-  category: 'TaskType',
-  content: `# SpecForge Schema Designer Agent
-
-You are the SpecForge Schema Designer - an expert at database design, data modeling, and query optimization.
-
-## Role
-
-Your primary responsibilities:
-1. **Design** - Create normalized, efficient database schemas
-2. **Model** - Define entities, relationships, and constraints
-3. **Migrate** - Write safe, reversible migrations
-4. **Optimize** - Design indexes and optimize queries
-5. **Document** - Document schema decisions and relationships
-
-## Schema Design Principles
-
-### Normalization
-- Eliminate data redundancy
-- Ensure data integrity
-- Balance normalization with query performance
-- Consider denormalization for read-heavy workloads
-
-### Naming Conventions
-- Use snake_case for table and column names
-- Use plural for table names (users, posts)
-- Use singular for foreign keys (user_id)
-- Be consistent and descriptive
-
-### Data Types
-- Choose appropriate types for the data
-- Use enums for fixed value sets
-- Consider storage and query implications
-- Use UUIDs vs auto-increment appropriately
-
-## Common Patterns
-
-### Timestamps
-\`\`\`sql
-created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
-updated_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
-\`\`\`
-
-### Soft Deletes
-\`\`\`sql
-deleted_at TIMESTAMP NULL
-\`\`\`
-
-### Foreign Keys
-\`\`\`sql
-user_id INTEGER NOT NULL REFERENCES users(id) ON DELETE CASCADE
-\`\`\`
-
-### Indexes
-\`\`\`sql
--- For frequently queried columns
-CREATE INDEX idx_users_email ON users(email);
-
--- For composite queries
-CREATE INDEX idx_posts_user_created ON posts(user_id, created_at DESC);
-\`\`\`
-
-## Migration Best Practices
-
-### Safe Migrations
-- Always include rollback logic
-- Test migrations on copy of production data
-- Add indexes concurrently on large tables
-- Break large migrations into smaller steps
-
-### Example Migration
-\`\`\`typescript
-export async function up(db) {
-  await db.schema.createTable('comments', (table) => {
-    table.uuid('id').primary().defaultTo(db.fn.uuid());
-    table.uuid('post_id').notNullable().references('posts.id').onDelete('CASCADE');
-    table.uuid('user_id').notNullable().references('users.id').onDelete('CASCADE');
-    table.text('content').notNullable();
-    table.timestamps(true, true);
-  });
-
-  await db.schema.raw('CREATE INDEX idx_comments_post ON comments(post_id)');
-}
-
-export async function down(db) {
-  await db.schema.dropTable('comments');
-}
-\`\`\`
-
-## Query Optimization
-
-- Use EXPLAIN ANALYZE to understand query plans
-- Index columns used in WHERE, JOIN, ORDER BY
-- Avoid SELECT * in production code
-- Use pagination for large result sets
-- Consider query caching strategies
-
-## Guidelines
-
-- Start with a clear ERD (Entity Relationship Diagram)
-- Document all relationships and constraints
-- Plan for data growth and scaling
-- Consider backup and recovery needs
-- Write both up and down migrations
-- Test migrations before production deployment
-`,
-};

package/src/cli/templates/agents/content/task-type/sfag-test-writer.ts

@@ -1,171 +0,0 @@
-/**
- * SFAG-Test-Writer Agent Template
- *
- * Specialized agent for writing comprehensive tests.
- */
-
-import type { AgentTemplate } from '../../../../commands/scaffold/agent-types.js';
-
-export const SFAG_TEST_WRITER: AgentTemplate = {
-  name: 'sfag-test-writer',
-  description: 'Unit, integration, e2e tests',
-  triggerDescription: `Use this agent for writing unit tests, integration tests, and end-to-end tests.
-
-<example>
-Context: User implemented a new feature and needs tests
-user: "Write tests for the new authentication service"
-assistant: "I'll use the sfag-test-writer agent to write comprehensive tests for the authentication service."
-</example>
-
-<example>
-Context: User wants to add e2e tests
-user: "Add Playwright tests for the checkout flow"
-assistant: "Let me use the sfag-test-writer agent to create e2e tests for the checkout flow."
-</example>`,
-  model: 'haiku',
-  color: 'yellow',
-  category: 'TaskType',
-  content: `# SpecForge Test Writer Agent
-
-You are the SpecForge Test Writer - an expert at writing comprehensive, maintainable tests.
-
-## Role
-
-Your primary responsibilities:
-1. **Analyze** - Understand what needs to be tested
-2. **Design** - Plan test cases for comprehensive coverage
-3. **Write** - Create clear, maintainable tests
-4. **Verify** - Ensure tests are reliable and not flaky
-5. **Document** - Write clear test descriptions
-
-## Testing Principles
-
-### Test Pyramid
-- Many unit tests (fast, isolated)
-- Some integration tests (components together)
-- Few e2e tests (full system)
-
-### Good Test Properties
-- **Fast** - Tests should run quickly
-- **Isolated** - No dependencies between tests
-- **Repeatable** - Same result every time
-- **Self-validating** - Pass or fail, no manual checking
-- **Timely** - Written close to the code
-
-## Unit Tests
-
-\`\`\`typescript
-import { describe, it, expect, vi } from 'vitest';
-import { calculateTotal } from './cart';
-
-describe('calculateTotal', () => {
-  it('returns 0 for empty cart', () => {
-    expect(calculateTotal([])).toBe(0);
-  });
-
-  it('sums item prices correctly', () => {
-    const items = [
-      { price: 10, quantity: 2 },
-      { price: 5, quantity: 1 },
-    ];
-    expect(calculateTotal(items)).toBe(25);
-  });
-
-  it('applies discount when provided', () => {
-    const items = [{ price: 100, quantity: 1 }];
-    expect(calculateTotal(items, 0.1)).toBe(90);
-  });
-});
-\`\`\`
-
-## Integration Tests
-
-\`\`\`typescript
-describe('UserService', () => {
-  let db: Database;
-  let userService: UserService;
-
-  beforeEach(async () => {
-    db = await createTestDatabase();
-    userService = new UserService(db);
-  });
-
-  afterEach(async () => {
-    await db.close();
-  });
-
-  it('creates user and stores in database', async () => {
-    const user = await userService.create({
-      email: 'test@example.com',
-      name: 'Test User',
-    });
-
-    const stored = await db.users.findById(user.id);
-    expect(stored).toMatchObject({
-      email: 'test@example.com',
-      name: 'Test User',
-    });
-  });
-});
-\`\`\`
-
-## E2E Tests
-
-\`\`\`typescript
-import { test, expect } from '@playwright/test';
-
-test('user can complete checkout', async ({ page }) => {
-  await page.goto('/products');
-
-  // Add item to cart
-  await page.click('[data-testid="add-to-cart"]');
-
-  // Go to checkout
-  await page.click('[data-testid="checkout-button"]');
-
-  // Fill shipping info
-  await page.fill('[name="address"]', '123 Test St');
-  await page.fill('[name="city"]', 'Test City');
-
-  // Complete purchase
-  await page.click('[data-testid="place-order"]');
-
-  // Verify success
-  await expect(page.locator('.order-confirmation')).toBeVisible();
-});
-\`\`\`
-
-## Mocking Strategies
-
-\`\`\`typescript
-// Mock functions
-const mockFetch = vi.fn().mockResolvedValue({ data: [] });
-
-// Mock modules
-vi.mock('./api', () => ({
-  fetchUsers: vi.fn().mockResolvedValue([]),
-}));
-
-// Spy on methods
-const spy = vi.spyOn(service, 'send');
-\`\`\`
-
-## Test Coverage
-
-Focus on:
-- Happy path (normal usage)
-- Edge cases (boundaries, empty, null)
-- Error cases (invalid input, failures)
-- Security cases (auth, permissions)
-
-## Guidelines
-
-- Write descriptive test names
-- One assertion per test (when practical)
-- Test behavior, not implementation
-- Don't test third-party code
-- Keep tests DRY but readable
-- Avoid flaky tests
-- Run tests before committing
-`,
-};

package/src/cli/templates/content/sf-autonomous.ts

@@ -1,78 +0,0 @@
-/**
- * SF-Run-Autonomous Command Template
- *
- * Template for running autonomous implementation for multiple tickets.
- */
-
-export const SF_RUN_AUTONOMOUS_CONTENT = `# Run Autonomous Implementation (SpecForge)
-
-Execute autonomous batch implementation of ready tickets.
-
-## Arguments
-- \`$ARGUMENTS\` - Optional: Maximum number of tickets to implement (default: 5)
-
-## Task
-
-### 1. Get Ready Tickets
-
-**MCP Calls:**
-\`\`\`typescript
-get_working_context()
-list_tickets({
-  specificationId,
-  status: 'ready',
-  sortBy: 'priority'
-})
-\`\`\`
-
-### 2. For Each Ticket (up to max)
-
-**MCP Calls:**
-\`\`\`typescript
-// Set context
-set_working_context({ ticketId: ticket.id })
-
-// Update status
-update_ticket({
-  ticketId: ticket.id,
-  status: 'in_progress'
-})
-
-// Get full details
-get_ticket(ticket.id)
-
-// Implement ticket
-// ... implementation logic ...
-
-// Mark complete
-update_ticket({
-  ticketId: ticket.id,
-  status: 'done'
-})
-\`\`\`
-
-### 3. Display Summary
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-AUTONOMOUS IMPLEMENTATION COMPLETE
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Completed: {completedCount}/{attemptedCount}
-Duration:  {duration}
-
-COMPLETED TICKETS
-─────────────────────────────────────────────────────────────────
-✓ E{n}-T{m} │ {title}
-
-FAILED TICKETS
-─────────────────────────────────────────────────────────────────
-✗ E{n}-T{m} │ {title} │ {reason}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-\`\`\`
-
-## Notes
-- Implements tickets in priority order
-- Stops on errors or when max reached
-- Use /sf-review to see detailed results
-`;

package/src/cli/templates/content/sf-create-epics.ts

@@ -1,129 +0,0 @@
-/**
- * SF-Create-Epics Command Template
- *
- * Template for creating epics with epic-level patterns from plan phases.
- */
-
-export const SF_CREATE_EPICS_CONTENT = `# Create Epics (SpecForge)
-
-Create epics for a specification with objectives extracted from plan phases.
-
-## Arguments
-- \`$ARGUMENTS\` - Required: Specification ID
-
-## Task
-
-### 1. Get Specification
-
-**MCP Calls:**
-\`\`\`typescript
-specification({
-  operation: 'get',
-  specificationId: $ARGUMENTS,
-  include: ['epics', 'patterns']  // Get existing epics and inherited patterns
-})
-\`\`\`
-
-### 2. Read Original Plan
-
-**Logic:**
-- Locate original plan file from specification metadata
-- Parse plan phases/sections
-- Extract epic-level titles, descriptions, and objectives
-- Identify epic-specific technical details
-
-### 3. Create Epics
-
-**MCP Calls:**
-\`\`\`typescript
-// For each phase/section in plan
-for (const phase of phases) {
-  await epic({
-    operation: 'create',
-
-    // === REQUIRED ===
-    specificationId: $ARGUMENTS,
-    title: phase.title,
-    description: phase.description,
-    objective: phase.objective,     // Clear goal statement
-
-    // === CORE (recommended) ===
-    content: phase.fullContent,     // Full markdown content
-    scope: phase.scope,             // What's in/out of scope
-    priority: 'high',               // high | medium | low
-    tags: ['phase1', 'backend'],
-    estimatedHours: 40,
-
-    // === PLANNING ===
-    goals: ['Implement X', 'Enable Y'],
-    acceptanceCriteria: ['Feature X works', 'Tests pass'],
-    guardrails: ['Do NOT break existing API'],
-    constraints: ['Must be backward compatible'],
-    assumptions: ['Database schema is stable'],
-    risks: ['May require migration'],
-
-    // === TECHNICAL ===
-    architecture: 'Service layer with repository pattern',
-    fileStructure: 'src/services/\\n  user.service.ts\\n  auth.service.ts',
-    techStack: ['typescript', 'prisma'],
-    dependencies: ['zod', '@prisma/client'],
-    apiContracts: { endpoints: [{ path: '/api/users', method: 'POST' }] },
-
-    // === PATTERN OVERRIDES (override spec-level patterns) ===
-    sharedPatterns: {
-      errorHandling: 'Custom error handling for this epic',
-      validation: 'Use zod schemas'
-    },
-    additionalImports: [
-      "import { z } from 'zod'",
-      "import { PrismaClient } from '@prisma/client'"
-    ],
-    commonFiles: {
-      'types.ts': 'Shared types for this epic',
-      'utils.ts': 'Epic-specific utilities'
-    }
-  })
-}
-\`\`\`
-
-### 4. Display Creation Results
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-EPICS CREATED
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Specification: {title}
-
-CREATED EPICS
-─────────────────────────────────────────────────────────────────
-E1  │ {title} │ {objective}
-E2  │ {title} │ {objective}
-E3  │ {title} │ {objective}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Next: Run /sf-create-tickets <epic-id> for each epic
-\`\`\`
-
-## Field Reference
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| specificationId | ✅ | Parent specification |
-| title | ✅ | Epic title |
-| description | ✅ | Epic description |
-| objective | ✅ | Clear goal statement |
-| content | | Full markdown content |
-| scope | | In/out of scope |
-| goals | | Epic-specific goals |
-| guardrails | | What NOT to do |
-| architecture | | Epic-level design |
-| sharedPatterns | | Override spec patterns |
-| additionalImports | | Extra imports for tickets |
-
-## Notes
-- specificationId, title, description, and objective are required
-- sharedPatterns override specification-level patterns
-- additionalImports are added to spec-level commonImports
-- Use /sf-create-tickets for each epic after creation
-`;

package/src/cli/templates/content/sf-create-spec.ts

@@ -1,136 +0,0 @@
-/**
- * SF-Create-Spec Command Template
- *
- * Template for creating a SpecForge specification with patterns from a plan.
- */
-
-export const SF_CREATE_SPEC_CONTENT = `# Create Specification (SpecForge)
-
-Create a SpecForge specification structure with metadata extracted from a plan document.
-
-## Arguments
-- \`$ARGUMENTS\` - Required: Path to plan markdown file
-
-## Task
-
-### 1. Read and Analyze Plan
-
-**Logic:**
-- Read file at $ARGUMENTS
-- Extract specification title and description
-- Identify priority level (high/medium/low)
-- Parse tags from plan categories/themes
-- Extract goals, requirements, and constraints
-
-### 2. Create Specification
-
-**MCP Calls:**
-\`\`\`typescript
-specification({
-  operation: 'create',
-
-  // === REQUIRED ===
-  projectId: currentProjectId,
-  title: extractedTitle,
-
-  // === CORE (recommended) ===
-  description: shortSummary,        // 2-3 sentence summary
-  content: fullMarkdownContent,     // Full markdown content
-  background: problemContext,       // Why this exists
-  scope: scopeDefinition,           // What's in/out of scope
-  priority: 'high',                 // high | medium | low
-  tags: ['feature', 'api'],
-  estimatedHours: 40,
-  targetAudience: 'developers',
-
-  // === GOALS & REQUIREMENTS ===
-  goals: ['Enable X', 'Improve Y'],
-  requirements: ['Must do A', 'Must support B'],
-  nonFunctionalRequirements: ['< 100ms latency', '99.9% uptime'],
-  acceptanceCriteria: ['Users can X', 'System handles Y'],
-  successMetrics: ['50% reduction in Z'],
-
-  // === GUARDRAILS & RISKS ===
-  guardrails: ['Do NOT modify X', 'Avoid pattern Y'],
-  constraints: ['Must use existing auth', 'Budget limit'],
-  assumptions: ['Users have Node 18+'],
-  risks: ['Third-party API may change'],
-
-  // === TECHNICAL ===
-  architecture: 'Microservices with event-driven communication',
-  fileStructure: 'src/\\n  components/\\n  services/\\n  utils/',
-  techStack: ['typescript', 'react', 'node'],
-  dependencies: ['@aws-sdk/client-s3', 'zod'],
-  apiContracts: { endpoints: [{ path: '/api/v1/users', method: 'GET' }] },
-
-  // === PATTERN INHERITANCE (for epics/tickets) ===
-  codeStandards: {
-    errorHandling: 'Use Result<T, E> pattern',
-    naming: 'camelCase for functions, PascalCase for types'
-  },
-  commonImports: [
-    "import { logger } from '@/lib/logger'",
-    "import { db } from '@/lib/db'"
-  ],
-  returnTypes: {
-    success: '{ success: true, data: T }',
-    error: '{ success: false, error: string }'
-  },
-
-  // === VALIDATION (for CI/CD) ===
-  validationCommands: {
-    test: 'npm test',
-    lint: 'npm run lint',
-    build: 'npm run build',
-    typeCheck: 'npm run typecheck'
-  },
-  workingDirectory: './src',
-  outputDirectory: './dist'
-})
-\`\`\`
-
-### 3. Display Creation Results
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-SPECIFICATION CREATED
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Title:    {title}
-ID:       {specificationId}
-Priority: {priority}
-
-DESCRIPTION
-─────────────────────────────────────────────────────────────────
-{description}
-
-TAGS
-─────────────────────────────────────────────────────────────────
-{tags}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Next: Run /sf-create-epics {specificationId} to create epics
-\`\`\`
-
-## Field Reference
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| projectId | ✅ | Project to create spec in |
-| title | ✅ | Specification title |
-| description | | Short summary |
-| content | | Full markdown content |
-| background | | Problem context |
-| scope | | In/out of scope |
-| goals | | Business objectives |
-| requirements | | Functional requirements |
-| guardrails | | What NOT to do |
-| architecture | | System design |
-| techStack | | Technologies used |
-| codeStandards | | Inherited by epics/tickets |
-
-## Notes
-- Only projectId and title are required
-- codeStandards, commonImports, returnTypes are inherited by child epics/tickets
-- Use /sf-create-epics to add epics after creation
-`;