@specforge/mcp 3.2.3 → 3.3.1

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

@@ -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
-`;

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

@@ -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
-`;

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

@@ -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
-`;

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

@@ -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
-`;

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

@@ -1,67 +0,0 @@
-/**
- * SF-Review Command Template
- *
- * Template for reviewing accomplishments and progress analysis.
- */
-
-export const SF_REVIEW_CONTENT = `# Review Accomplishments (SpecForge)
-
-Comprehensive review of implementation progress and accomplishments.
-
-## Arguments
-- \`$ARGUMENTS\` - Optional: Specification ID to review
-
-## Task
-
-### 1. Get Specification Context
-
-**MCP Calls:**
-\`\`\`typescript
-get_working_context()
-
-if ($ARGUMENTS) {
-  set_working_context({ specificationId: "$ARGUMENTS" })
-}
-
-get_specification(specificationId)
-\`\`\`
-
-### 2. Load Implementation Data
-
-**MCP Calls:**
-\`\`\`typescript
-list_epics({ specificationId })
-list_tickets({ specificationId })
-\`\`\`
-
-### 3. Display Review Summary
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-IMPLEMENTATION REVIEW
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Specification: {title}
-Overall:       {done}/{total} ({percentage}%)
-
-PROGRESS BY EPIC
-─────────────────────────────────────────────────────────────────
-E{n} │ {title} │ {ticketsDone}/{ticketsTotal} ({pct}%)
-
-RECENTLY COMPLETED
-─────────────────────────────────────────────────────────────────
-✓ E{n}-T{m} │ {title} │ {completedDate}
-
-VELOCITY
-─────────────────────────────────────────────────────────────────
-Last 7 days:  {ticketsCompleted} tickets
-Average:      {avgPerDay} tickets/day
-Remaining:    ~{estimatedDays} days
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-\`\`\`
-
-## Notes
-- Shows completed tickets and velocity metrics
-- Provides estimated completion timeline
-- Use /sf-status for current state
-`;

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

@@ -1,76 +0,0 @@
-/**
- * SF-Ticket-Implementation Command Template
- *
- * Template for implementing a specific ticket with streamlined workflow.
- */
-
-export const SF_TICKET_IMPLEMENTATION_CONTENT = `# Implement Ticket (SpecForge)
-
-Implement a specific ticket with full context and streamlined workflow.
-
-## Arguments
-- \`$ARGUMENTS\` - Optional: Ticket ID to implement (e.g., E1-T3)
-
-## Task
-
-### 1. Select Ticket
-
-**MCP Calls:**
-\`\`\`typescript
-// If no arguments, prompt user
-if (!$ARGUMENTS) {
-  list_tickets({
-    specificationId,
-    status: 'ready'
-  })
-  // Display selection menu
-}
-
-// Get ticket details
-get_ticket($ARGUMENTS || selectedId)
-\`\`\`
-
-### 2. Verify Dependencies
-
-**MCP Calls:**
-\`\`\`typescript
-// Check all dependencies are completed
-for (const depId of ticket.dependencies) {
-  get_ticket(depId)
-  // Verify status is 'done'
-}
-\`\`\`
-
-### 3. Set Context and Start
-
-**MCP Calls:**
-\`\`\`typescript
-set_working_context({ ticketId: ticket.id })
-update_ticket({
-  ticketId: ticket.id,
-  status: 'in_progress'
-})
-\`\`\`
-
-### 4. Display Implementation View
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-IMPLEMENTING: E{n}-T{m}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-{title}
-
-{fullDescription}
-{implementationGuidance}
-{acceptanceCriteria}
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Begin implementation
-\`\`\`
-
-## Notes
-- Verifies all dependencies are completed
-- Provides full ticket context for implementation
-- Use /sf-commit when complete
-`;

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

@@ -1,78 +0,0 @@
-/**
- * SF-Validate Command Template
- *
- * Template for validating ticket system health.
- */
-
-export const SF_VALIDATE_CONTENT = `# Validate Ticket System (SpecForge)
-
-Run comprehensive health checks on the ticket system.
-
-## Arguments
-- \`$ARGUMENTS\` - Optional: Specification ID to validate
-
-## Task
-
-### 1. Get Specification Context
-
-**MCP Calls:**
-\`\`\`typescript
-get_working_context()
-
-if ($ARGUMENTS) {
-  set_working_context({ specificationId: "$ARGUMENTS" })
-}
-
-get_specification(specificationId)
-\`\`\`
-
-### 2. Load and Validate Data
-
-**MCP Calls:**
-\`\`\`typescript
-list_epics({ specificationId })
-list_tickets({ specificationId })
-
-// Validate each ticket
-for (const ticket of tickets) {
-  get_ticket(ticket.id)
-  // Check dependencies, status, fields
-}
-\`\`\`
-
-### 3. Display Validation Results
-
-**Output:**
-\`\`\`
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-SYSTEM VALIDATION
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Specification: {title}
-
-CHECKS
-─────────────────────────────────────────────────────────────────
-✓ All epics have valid structure
-✓ All tickets have required fields
-✓ Dependency graph is acyclic
-✓ Status transitions are valid
-✓ No orphaned tickets
-
-WARNINGS
-─────────────────────────────────────────────────────────────────
-⚠ E{n}-T{m}: Missing acceptance criteria
-⚠ E{n}-T{m}: Long dependency chain (depth {n})
-
-ERRORS
-─────────────────────────────────────────────────────────────────
-✗ E{n}-T{m}: Circular dependency detected
-✗ E{n}-T{m}: Invalid dependency reference
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Status: {errors ? 'FAILED' : 'PASSED'}
-\`\`\`
-
-## Notes
-- Checks dependency graph integrity
-- Validates ticket structure and fields
-- Reports warnings and errors
-`;