@specforge/mcp 3.3.5 → 3.3.7

package/dist/cli/templates/agents/content/task-type/sfag-test-writer.js

@@ -1,169 +0,0 @@
-/**
- * SFAG-Test-Writer Agent Template
- *
- * Specialized agent for writing comprehensive tests.
- */
-export const SFAG_TEST_WRITER = {
-    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
-`,
-};
-//# sourceMappingURL=sfag-test-writer.js.map

package/dist/cli/templates/agents/content/task-type/sfag-test-writer.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"sfag-test-writer.js","sourceRoot":"","sources":["../../../../../../src/cli/templates/agents/content/task-type/sfag-test-writer.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAIH,MAAM,CAAC,MAAM,gBAAgB,GAAkB;IAC7C,IAAI,EAAE,kBAAkB;IACxB,WAAW,EAAE,8BAA8B;IAC3C,kBAAkB,EAAE;;;;;;;;;;;;WAYX;IACT,KAAK,EAAE,OAAO;IACd,KAAK,EAAE,QAAQ;IACf,QAAQ,EAAE,UAAU;IACpB,OAAO,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8IV;CACA,CAAC"}

package/dist/cli/templates/content/sf-autonomous.d.ts

@@ -1,7 +0,0 @@
-/**
- * SF-Run-Autonomous Command Template
- *
- * Template for running autonomous implementation for multiple tickets.
- */
-export declare const SF_RUN_AUTONOMOUS_CONTENT = "# Run Autonomous Implementation (SpecForge)\n\nExecute autonomous batch implementation of ready tickets.\n\n## Arguments\n- `$ARGUMENTS` - Optional: Maximum number of tickets to implement (default: 5)\n\n## Task\n\n### 1. Get Ready Tickets\n\n**MCP Calls:**\n```typescript\nget_working_context()\nlist_tickets({\n  specificationId,\n  status: 'ready',\n  sortBy: 'priority'\n})\n```\n\n### 2. For Each Ticket (up to max)\n\n**MCP Calls:**\n```typescript\n// Set context\nset_working_context({ ticketId: ticket.id })\n\n// Update status\nupdate_ticket({\n  ticketId: ticket.id,\n  status: 'in_progress'\n})\n\n// Get full details\nget_ticket(ticket.id)\n\n// Implement ticket\n// ... implementation logic ...\n\n// Mark complete\nupdate_ticket({\n  ticketId: ticket.id,\n  status: 'done'\n})\n```\n\n### 3. Display Summary\n\n**Output:**\n```\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nAUTONOMOUS IMPLEMENTATION COMPLETE\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nCompleted: {completedCount}/{attemptedCount}\nDuration:  {duration}\n\nCOMPLETED TICKETS\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n\u2713 E{n}-T{m} \u2502 {title}\n\nFAILED TICKETS\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\n\u2717 E{n}-T{m} \u2502 {title} \u2502 {reason}\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\n```\n\n## Notes\n- Implements tickets in priority order\n- Stops on errors or when max reached\n- Use /sf-review to see detailed results\n";
-//# sourceMappingURL=sf-autonomous.d.ts.map

package/dist/cli/templates/content/sf-autonomous.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sf-autonomous.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-autonomous.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,yBAAyB,s1FAuErC,CAAC"}

package/dist/cli/templates/content/sf-autonomous.js

@@ -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
-`;
-//# sourceMappingURL=sf-autonomous.js.map

package/dist/cli/templates/content/sf-autonomous.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"sf-autonomous.js","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-autonomous.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuExC,CAAC"}

package/dist/cli/templates/content/sf-create-epics.d.ts

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

package/dist/cli/templates/content/sf-create-epics.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sf-create-epics.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-create-epics.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,uBAAuB,upJA0HnC,CAAC"}

package/dist/cli/templates/content/sf-create-epics.js

@@ -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
-`;
-//# sourceMappingURL=sf-create-epics.js.map

package/dist/cli/templates/content/sf-create-epics.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"sf-create-epics.js","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-create-epics.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,MAAM,CAAC,MAAM,uBAAuB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA0HtC,CAAC"}

package/dist/cli/templates/content/sf-create-spec.d.ts

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

package/dist/cli/templates/content/sf-create-spec.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sf-create-spec.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-create-spec.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,sBAAsB,wsKAiIlC,CAAC"}

package/dist/cli/templates/content/sf-create-spec.js

@@ -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
-`;
-//# sourceMappingURL=sf-create-spec.js.map

package/dist/cli/templates/content/sf-create-spec.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"sf-create-spec.js","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-create-spec.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,MAAM,CAAC,MAAM,sBAAsB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiIrC,CAAC"}

package/dist/cli/templates/content/sf-create-tickets.d.ts

@@ -1,7 +0,0 @@
-/**
- * SF-Create-Tickets Command Template
- *
- * Template for creating detailed tickets individually with full implementation context.
- */
-export declare const SF_CREATE_TICKETS_CONTENT = "# Create Tickets (SpecForge)\n\nCreate detailed tickets for an epic with full implementation context.\n\n## Arguments\n- `$ARGUMENTS` - Required: Epic ID\n\n## Task\n\n### 1. Get Epic Context\n\n**MCP Calls:**\n```typescript\nepic({\n  operation: 'get',\n  epicId: $ARGUMENTS,\n  include: ['tickets', 'specification']  // Get existing tickets and parent spec\n})\n```\n\n### 2. Extract Ticket Definitions\n\n**Logic:**\n- Read epic description and objective\n- Parse task breakdown from epic content\n- Determine complexity and dependencies\n- Extract acceptance criteria for each ticket\n\n### 3. Create Tickets\n\n**MCP Calls:**\n```typescript\n// For each task in epic\nfor (const task of tasks) {\n  await ticket({\n    operation: 'create',\n\n    // === REQUIRED ===\n    epicId: $ARGUMENTS,\n    title: task.title,\n\n    // === CORE (recommended) ===\n    description: task.description,\n    priority: 'high',               // high | medium | low\n    complexity: 'medium',           // small | medium | large | xlarge\n    estimatedHours: 4,\n    tags: ['feature', 'api'],\n    notes: 'Watch out for edge case X',  // Warnings, considerations\n\n    // === ACCEPTANCE CRITERIA ===\n    acceptanceCriteria: [\n      'Function returns correct result for valid input',\n      'Function throws error for invalid input',\n      'Unit tests cover all branches'\n    ],\n\n    // === IMPLEMENTATION GUIDANCE ===\n    implementation: {\n      filesToCreate: ['src/services/user.service.ts'],\n      filesToModify: ['src/index.ts'],\n      steps: [\n        'Create UserService class',\n        'Implement createUser method',\n        'Add validation with zod',\n        'Write unit tests'\n      ],\n      testing: 'Use vitest with mocked database'\n    },\n    technicalDetails: {\n      approach: 'Repository pattern with dependency injection',\n      stack: ['typescript', 'prisma', 'zod'],\n      endpoints: ['/api/users POST'],\n      databaseChanges: ['Add users table']\n    },\n\n    // === CODE REFERENCES ===\n    codeReferences: [{\n      name: 'createUser',\n      language: 'typescript',\n      code: `async function createUser(data: CreateUserInput): Promise<User> {\n  const validated = createUserSchema.parse(data);\n  return await db.user.create({ data: validated });\n}`\n    }],\n    typeReferences: [{\n      name: 'CreateUserInput',\n      definition: `interface CreateUserInput {\n  email: string;\n  name: string;\n  role?: 'admin' | 'user';\n}`\n    }],\n\n    // === DEPENDENCIES ===\n    dependsOn: ['ticket-id-1', 'ticket-id-2']  // Must complete these first\n  })\n}\n```\n\n### 4. Display Creation Results\n\n**Output:**\n```\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nTICKETS CREATED\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\nEpic: E{n} - {epicTitle}\n\nCREATED TICKETS\n\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\nE{n}-T1  \u2502 {title} \u2502 {complexity} \u2502 ready\nE{n}-T2  \u2502 {title} \u2502 {complexity} \u2502 pending (depends on T1)\nE{n}-T3  \u2502 {title} \u2502 {complexity} \u2502 ready\n\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\n\nTotal: {ticketCount} tickets created\n\nNext: Run /sf-status to see overall progress\n```\n\n## Field Reference\n\n| Field | Required | Description |\n|-------|----------|-------------|\n| epicId | \u2705 | Parent epic |\n| title | \u2705 | Ticket title |\n| description | | What to implement |\n| complexity | | small \\| medium \\| large \\| xlarge |\n| acceptanceCriteria | | Success criteria (array of strings) |\n| implementation | | Steps, files to create/modify |\n| technicalDetails | | Approach, stack, endpoints |\n| codeReferences | | Code snippets to guide implementation |\n| typeReferences | | Type definitions to implement |\n| dependsOn | | Ticket IDs that must complete first |\n| notes | | Warnings, edge cases, considerations |\n\n## Notes\n- Only epicId and title are required\n- Tickets with dependsOn start as 'pending', others as 'ready'\n- codeReferences and typeReferences provide implementation guidance\n- Use /sf-next to start working on ready tickets\n";
-//# sourceMappingURL=sf-create-tickets.d.ts.map

package/dist/cli/templates/content/sf-create-tickets.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sf-create-tickets.d.ts","sourceRoot":"","sources":["../../../../src/cli/templates/content/sf-create-tickets.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,eAAO,MAAM,yBAAyB,4kKA6IrC,CAAC"}