Overview

Logs every failure with full context to progress.md, tags severity, analyzes cross-phase patterns, and suggests mutations to prevent repeats, while tracking resolution status for verification.

How This Skill Works

Uses dedicated planning pipelines: planning-orchestrator.js logs during phases, planning-execution.js records errors immediately with context and stack traces, and planning-verification.js checks resolution. It outputs updated progress.md entries, proposed approach mutations, and an error-resolution report to guide fixes.

When to Use It

• When a planning error occurs in any phase (orchestrator, execution, or verification).
• When errors repeat across phases or iterations, indicating a pattern.
• When you need full context—stack traces and reproduction steps—to diagnose failures.
• When you want to surface approach mutations to avoid known failure patterns.
• When you must verify error resolution and maintain a trace for auditing.

Quick Start

1. Step 1: Provide inputs (projectPath, phaseName, errors, errorHistory).
2. Step 2: Run the Error Logging workflow and ensure immediate logging to progress.md.
3. Step 3: Review the updated error section, mutations, and the resolution report.

Best Practices

• Log every error immediately to progress.md.
• Include error context, stack traces, and reproduction steps.
• Tag each error with severity: critical, warning, or informational.
• Analyze error history to identify cross-phase patterns.
• Document and track approach mutations and error-resolution status.

Example Use Cases

• An error in planning-orchestrator.js triggers immediate logging and pattern detection.
• Repeated timeouts across iterations are surfaced as a pattern for mutation.
• A critical failure prompts an approach mutation to change strategy.
• Progress.md is updated with an error section and suggested resolutions.
• An error-resolution report confirms fixes in the next verification run.

Frequently Asked Questions