manage-logging

Centralize script, work, and decision logs via the manage-log CLI.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill manage-logging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-logging
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/manage-logging
Command: npx skills add https://github.com/cuioss/plan-marshall --skill manage-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires input_validation, and includes scripts (resource) components.

What problem does it solve?

Unified logging infrastructure that captures script execution, work progress, and decision records across plan runs, providing a centralized, consistent view of plan activity.

Core Features & Use Cases

  • Script Execution Logging: records script invocations and durations to a dedicated script-execution.log.
  • Work Logging: captures semantic progress and artifacts to work.log with phase and detail metadata.
  • Decision Logging: records decisions to decision.log for traceability.
  • Plan-scoped and Global Logs: writes to plan-specific logs when a plan context exists; otherwise falls back to global daily logs, with clear retention and rotation behavior.
  • CLI & API Access: can be driven via the manage-log CLI or the plan_logging Python module for programmatic logging.

Quick Start

Run a sample work log entry with the CLI to verify the logging workflow.

Frequently Asked Questions about manage-logging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I centralize logging for script execution and work progress in a plan management system?

Centralized logging captures script invocations, semantic work progress, and decision records into dedicated plan-scoped logs, providing a consistent view of plan activity across CLI usage and runtime instrumentation.

What is the best way to record decision logs for plan execution traceability?

Decision logging records traceable entries to a dedicated decision.log file. It uses deterministic 6-character hashes and consistent formatting to maintain clear audit trails during plan execution.

How do I log script execution durations from the command line?

Script execution logging records CLI invocations and their durations directly to a script-execution.log file via the manage-log CLI, ensuring consistent runtime instrumentation across plan runs.

Can I use plan-scoped logs with a global fallback for daily logging?

Plan-scoped logging writes to plan-specific logs when a plan context exists. When no context is present, it automatically falls back to global daily logs with clear retention and rotation behavior.

How do I configure log retention and file paths for plan activity logs?

Log retention and file paths are configured through environment variables. The logging infrastructure exposes these settings to control retention behavior and storage locations for script, work, and decision logs.

Does the logging infrastructure require input validation before writing logs?

Yes, input validation is a required dependency. It ensures that write, read, and separator operations processed via the manage-log CLI and parsing helpers maintain data integrity before entering the logging pipeline.