@specforge/mcp 3.3.4 → 3.3.7

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"}

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

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

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

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

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

@@ -1,7 +0,0 @@
-/**
- * SF-Epic Command Template
- *
- * Template for viewing epic details and progress.
- */
-export declare const SF_EPIC_CONTENT = "# View Epic (SpecForge)\n\nView detailed information about a specific epic and its progress.\n\n## Arguments\n- `$ARGUMENTS` - Required: Epic ID (e.g., E1)\n\n## Task\n\n### 1. Get Epic Details\n\n**MCP Calls:**\n```typescript\nget_epic($ARGUMENTS)\nget_specification(epic.specificationId)\nlist_tickets({ epicId: $ARGUMENTS })\n```\n\n### 2. Calculate Progress\n\n**Logic:**\n- Count tickets by status\n- Calculate completion percentage\n- Identify blockers\n- Track velocity\n\n### 3. Display Epic Overview\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\nEPIC: E{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\n{title}\n\nSpecification: {specTitle}\nProgress:      {done}/{total} ({percentage}%)\nStatus:        {status}\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\nTICKETS\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} \u2502 done\n\u2192 E{n}-T{m} \u2502 {title} \u2502 in_progress\n\u25CB E{n}-T{m} \u2502 {title} \u2502 ready\n\u2297 E{n}-T{m} \u2502 {title} \u2502 blocked\n\nPATTERNS\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{epicPatterns}\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-next to continue implementation\n```\n\n## Notes\n- Shows all tickets in epic\n- Displays epic-level patterns\n- Use /sf-ticket-implementation <id> to work on specific ticket\n";
-//# sourceMappingURL=sf-epic.d.ts.map

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

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

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

@@ -1,69 +0,0 @@
-/**
- * SF-Epic Command Template
- *
- * Template for viewing epic details and progress.
- */
-export const SF_EPIC_CONTENT = `# View Epic (SpecForge)
-
-View detailed information about a specific epic and its progress.
-
-## Arguments
-- \`$ARGUMENTS\` - Required: Epic ID (e.g., E1)
-
-## Task
-
-### 1. Get Epic Details
-
-**MCP Calls:**
-\`\`\`typescript
-get_epic($ARGUMENTS)
-get_specification(epic.specificationId)
-list_tickets({ epicId: $ARGUMENTS })
-\`\`\`
-
-### 2. Calculate Progress
-
-**Logic:**
-- Count tickets by status
-- Calculate completion percentage
-- Identify blockers
-- Track velocity
-
-### 3. Display Epic Overview
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-EPIC: E{n}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-{title}
-
-Specification: {specTitle}
-Progress:      {done}/{total} ({percentage}%)
-Status:        {status}
-
-DESCRIPTION
-─────────────────────────────────────────────────────────────────
-{description}
-
-TICKETS
-─────────────────────────────────────────────────────────────────
-✓ E{n}-T{m} │ {title} │ done
-→ E{n}-T{m} │ {title} │ in_progress
-○ E{n}-T{m} │ {title} │ ready
-⊗ E{n}-T{m} │ {title} │ blocked
-
-PATTERNS
-─────────────────────────────────────────────────────────────────
-{epicPatterns}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Next: Run /sf-next to continue implementation
-\`\`\`
-
-## Notes
-- Shows all tickets in epic
-- Displays epic-level patterns
-- Use /sf-ticket-implementation <id> to work on specific ticket
-`;
-//# sourceMappingURL=sf-epic.js.map

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

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

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

@@ -1,7 +0,0 @@
-/**
- * SF-Import-Plan Command Template
- *
- * Template for transforming a plan into a complete SpecForge specification.
- */
-export declare const SF_IMPORT_PLAN_CONTENT = "# Import Plan (SpecForge)\n\nTransform a plan document into a complete SpecForge specification with epics and tickets.\n\n## Arguments\n- `$ARGUMENTS` - Required: Path to plan markdown file\n\n## Task\n\n### 1. Read and Parse Plan\n\n**Logic:**\n- Read file at $ARGUMENTS\n- Extract specification metadata\n- Parse epic sections\n- Extract ticket information\n- Identify patterns and guardrails\n\n### 2. Create Specification\n\n**MCP Calls:**\n```typescript\ncreate_specification({\n  title: extractedTitle,\n  description: extractedDescription,\n  metadata: extractedMetadata\n})\n```\n\n### 3. Create Epics and Tickets\n\n**MCP Calls:**\n```typescript\n// For each epic in plan\nfor (const epic of epics) {\n  const epicId = await create_epic({\n    specificationId,\n    title: epic.title,\n    description: epic.description\n  })\n\n  // For each ticket in epic\n  for (const ticket of epic.tickets) {\n    await create_ticket({\n      epicId,\n      title: ticket.title,\n      description: ticket.description,\n      dependencies: ticket.dependencies\n    })\n  }\n}\n```\n\n### 4. Display Import 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\nPLAN IMPORT 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\nSpecification: {title}\nID:            {specificationId}\n\nCREATED\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\nEpics:   {epicCount}\nTickets: {ticketCount}\n\nSTRUCTURE\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 {ticketCount} tickets\nE2  \u2502 {title} \u2502 {ticketCount} tickets\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-init {specificationId} to start work\n```\n\n## Notes\n- Automatically creates full ticket system from plan\n- Preserves epic and ticket structure\n- Use /sf-init to begin implementation\n";
-//# sourceMappingURL=sf-import.d.ts.map

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

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

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

@@ -1,88 +0,0 @@
-/**
- * SF-Import-Plan Command Template
- *
- * Template for transforming a plan into a complete SpecForge specification.
- */
-export const SF_IMPORT_PLAN_CONTENT = `# Import Plan (SpecForge)
-
-Transform a plan document into a complete SpecForge specification with epics and tickets.
-
-## Arguments
-- \`$ARGUMENTS\` - Required: Path to plan markdown file
-
-## Task
-
-### 1. Read and Parse Plan
-
-**Logic:**
-- Read file at $ARGUMENTS
-- Extract specification metadata
-- Parse epic sections
-- Extract ticket information
-- Identify patterns and guardrails
-
-### 2. Create Specification
-
-**MCP Calls:**
-\`\`\`typescript
-create_specification({
-  title: extractedTitle,
-  description: extractedDescription,
-  metadata: extractedMetadata
-})
-\`\`\`
-
-### 3. Create Epics and Tickets
-
-**MCP Calls:**
-\`\`\`typescript
-// For each epic in plan
-for (const epic of epics) {
-  const epicId = await create_epic({
-    specificationId,
-    title: epic.title,
-    description: epic.description
-  })
-
-  // For each ticket in epic
-  for (const ticket of epic.tickets) {
-    await create_ticket({
-      epicId,
-      title: ticket.title,
-      description: ticket.description,
-      dependencies: ticket.dependencies
-    })
-  }
-}
-\`\`\`
-
-### 4. Display Import Results
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-PLAN IMPORT COMPLETE
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Specification: {title}
-ID:            {specificationId}
-
-CREATED
-─────────────────────────────────────────────────────────────────
-Epics:   {epicCount}
-Tickets: {ticketCount}
-
-STRUCTURE
-─────────────────────────────────────────────────────────────────
-E1  │ {title} │ {ticketCount} tickets
-E2  │ {title} │ {ticketCount} tickets
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Next: Run /sf-init {specificationId} to start work
-\`\`\`
-
-## Notes
-- Automatically creates full ticket system from plan
-- Preserves epic and ticket structure
-- Use /sf-init to begin implementation
-`;
-//# sourceMappingURL=sf-import.js.map

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

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

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

@@ -1,7 +0,0 @@
-/**
- * SF-Next Command Template
- *
- * Template for quick starting the next ready ticket.
- */
-export declare const SF_NEXT_CONTENT = "# Quick Start Next Ticket (SpecForge)\n\nAutomatically find and start the next ready ticket for implementation.\n\n## Task\n\n### 1. Find Next Ready Ticket\n\n**MCP Calls:**\n```typescript\nget_working_context()\nlist_tickets({\n  specificationId,\n  status: 'ready',\n  sortBy: 'priority'\n})\n```\n\n### 2. Set Ticket Context\n\n**MCP Calls:**\n```typescript\nset_working_context({\n  ticketId: nextTicket.id\n})\nupdate_ticket({\n  ticketId: nextTicket.id,\n  status: 'in_progress'\n})\n```\n\n### 3. Display Ticket Details\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\nSTARTING: E{n}-T{m}\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}\nPriority:     {priority}\nEpic:         E{n} - {epicTitle}\nDependencies: {depCount} completed\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\nACCEPTANCE CRITERIA\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\u25A1 {criterion1}\n\u25A1 {criterion2}\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\nReady to implement!\n```\n\n## Notes\n- Automatically selects highest priority ready ticket\n- Updates ticket status to in_progress\n- Sets working context to selected ticket\n";
-//# sourceMappingURL=sf-next.d.ts.map

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

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

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

@@ -1,67 +0,0 @@
-/**
- * SF-Next Command Template
- *
- * Template for quick starting the next ready ticket.
- */
-export const SF_NEXT_CONTENT = `# Quick Start Next Ticket (SpecForge)
-
-Automatically find and start the next ready ticket for implementation.
-
-## Task
-
-### 1. Find Next Ready Ticket
-
-**MCP Calls:**
-\`\`\`typescript
-get_working_context()
-list_tickets({
-  specificationId,
-  status: 'ready',
-  sortBy: 'priority'
-})
-\`\`\`
-
-### 2. Set Ticket Context
-
-**MCP Calls:**
-\`\`\`typescript
-set_working_context({
-  ticketId: nextTicket.id
-})
-update_ticket({
-  ticketId: nextTicket.id,
-  status: 'in_progress'
-})
-\`\`\`
-
-### 3. Display Ticket Details
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-STARTING: E{n}-T{m}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Title:        {title}
-Priority:     {priority}
-Epic:         E{n} - {epicTitle}
-Dependencies: {depCount} completed
-
-DESCRIPTION
-─────────────────────────────────────────────────────────────────
-{description}
-
-ACCEPTANCE CRITERIA
-─────────────────────────────────────────────────────────────────
-□ {criterion1}
-□ {criterion2}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Ready to implement!
-\`\`\`
-
-## Notes
-- Automatically selects highest priority ready ticket
-- Updates ticket status to in_progress
-- Sets working context to selected ticket
-`;
-//# sourceMappingURL=sf-next.js.map

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

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

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

@@ -1,7 +0,0 @@
-/**
- * SF-Review Command Template
- *
- * Template for reviewing accomplishments and progress analysis.
- */
-export declare const SF_REVIEW_CONTENT = "# Review Accomplishments (SpecForge)\n\nComprehensive review of implementation progress and accomplishments.\n\n## Arguments\n- `$ARGUMENTS` - Optional: Specification ID to review\n\n## Task\n\n### 1. Get Specification Context\n\n**MCP Calls:**\n```typescript\nget_working_context()\n\nif ($ARGUMENTS) {\n  set_working_context({ specificationId: \"$ARGUMENTS\" })\n}\n\nget_specification(specificationId)\n```\n\n### 2. Load Implementation Data\n\n**MCP Calls:**\n```typescript\nlist_epics({ specificationId })\nlist_tickets({ specificationId })\n```\n\n### 3. Display Review 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\nIMPLEMENTATION REVIEW\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}\nOverall:       {done}/{total} ({percentage}%)\n\nPROGRESS BY EPIC\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} \u2502 {title} \u2502 {ticketsDone}/{ticketsTotal} ({pct}%)\n\nRECENTLY COMPLETED\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} \u2502 {completedDate}\n\nVELOCITY\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\nLast 7 days:  {ticketsCompleted} tickets\nAverage:      {avgPerDay} tickets/day\nRemaining:    ~{estimatedDays} days\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- Shows completed tickets and velocity metrics\n- Provides estimated completion timeline\n- Use /sf-status for current state\n";
-//# sourceMappingURL=sf-review.d.ts.map

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

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