What's next?

Continue workflow (recommended)
Add to Critical Patterns
Link related issues
Add to existing skill
Create new skill
View documentation
Enable discovery
Other


## Option Handlers

### Option 1: Continue workflow
- Return to calling skill/workflow
- Documentation complete, no further action

### Option 2: Add to Critical Patterns

**When user selects:** Pattern is non-obvious but must be followed every time.

Extract pattern from the documentation
Format as WRONG vs CORRECT (use template below)
Append to .agents/lessons/patterns/critical-patterns.md
Add cross-reference back to source doc
Confirm: "Added to Critical Patterns"


**Template:**
```markdown
## N. [Pattern Name] (Required)

### WRONG ([Will cause X error])
```[language]
[code showing wrong approach]

CORRECT

[code showing correct approach]

Why: [Technical explanation] Context: [When this applies] Source: .agents/lessons/[category]/[filename].md


### Option 3: Link related issues

Prompt: "Which doc to link? (filename or describe)"
Search .agents/lessons/ for matching doc
Add cross-reference to both docs under "## Related Issues"
Confirm: "Cross-reference added to both files"


### Option 4: Add to existing skill

Prompt: "Which skill?"
Find skill in plugins/*/skills/
Determine target: resources.md, patterns.md, or examples.md
Add link and brief description
Confirm: "Added to [skill-name] in [file]"


### Option 5: Create new skill

Prompt: "Skill name?"
Create directory: plugins/majestic-engineer/skills/[name]/
Create SKILL.md with basic structure
Add solution as first example in references/
Confirm: "Created [skill-name] skill"


### Option 6: View documentation

Read and display the created file
Present decision menu again


### Option 7: Enable discovery

Make lesson discoverable by lessons-discoverer agent:

Prompt workflow phases: [planning, debugging, review, implementation]
Prompt tech stacks: [rails, python, react, node, generic]
Prompt lesson type: [antipattern, gotcha, pattern, setup, workflow]
Update YAML frontmatter with:
- workflow_phase: [selected phases]
- tech_stack: [selected stacks]
- lesson_type: [selected type]
- impact: Derive from severity
- keywords: Extract from tags + symptoms
Confirm: "Lesson discoverable during [phases] workflows"


**Impact mapping:**
- critical → blocks_work
- high → major_time_sink
- medium/low → minor_inconvenience

### Option 8: Other

Prompt for custom action and execute.

## Integration

**Invoked by:** fix-reporter (after Step 7)
**Invokes:** None (terminal options)

## Input Schema

```yaml
doc_path: string  # Path to created documentation
category: string  # Problem category from fix-reporter

fix-decision-router

fix-decision-router Skill

Decision Menu