report-planner

Translate a consolidated delivery-report into a render-ready HTML report plan.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/fabioabr/ia-ws --skill report-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: report-planner
Source: https://github.com/fabioabr/ia-ws/tree/main/projects/discovery-to-go/base/behavior/skills/report-planner
Command: npx skills add https://github.com/fabioabr/ia-ws --skill report-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill translates a consolidated delivery-report into a detailed visual plan that defines how each region will render in HTML, ensuring a consistent, viewer-friendly presentation and a reliable handoff to the HTML writer.

Core Features & Use Cases

  • Reads {project}/delivery/delivery-report.md to identify regions and their data boundaries.
  • Uses {project}/setup/customization/current-context/{pack}-discovery-blueprint.md and {project}/setup/customization/html-layout.md to determine mandatory regions, layout and visual constraints.
  • Outputs {project}/delivery/report-plan.md as a complete, unambiguous visual specification, and acts as the contract between the consolidator and the html-writer.
  • Supports domain-specific adjustments and previews, ensuring alignment with client requirements or overrides.
  • Serves as a single source of truth for stakeholders to review the planned presentation before rendering.

Quick Start

Run the report-planner on your project path to generate delivery/report-plan.md from the delivery-report.

Frequently Asked Questions about report-planner

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

FAQPage Schema
How do I plan a visual delivery report from a consolidated markdown file?

Visual delivery report planning translates a consolidated delivery-report.md into a precise render-ready plan defining per-region HTML visualization, ensuring consistent presentation and reliable handoff to the HTML writer.

How do I generate a report-plan document that defines per-region HTML layout?

Generating a report-plan document involves reading the delivery-report.md and blueprint to determine mandatory regions and layout constraints, outputting a complete report-plan.md specification acting as the html-writer contract.

Does the report planning process support Chart.js or is it strictly HTML and CSS?

The report planning process enforces an HTML/CSS-first approach for visual delivery reports but includes optional Chart.js fallbacks for rendering data visualizations within the HTML layout.

Can I use a discovery blueprint to customize domain-specific regions in a delivery report?

Yes, you use a pack-discovery-blueprint.md alongside html-layout.md to apply domain-specific adjustments and previews, ensuring the planned visual delivery report aligns with client requirements or overrides.

What is the purpose of a report-plan.md file in the HTML rendering workflow?

A report-plan.md file serves as the single source of truth and contract between the consolidator and the html-writer, providing an unambiguous visual specification for stakeholders to review before rendering.

When should I not use an HTML/CSS-first approach for planning report visualizations?

You should reconsider an HTML/CSS-first approach when your delivery report requires complex interactive data visualizations exceeding standard layout capabilities, though the planner provides optional Chart.js fallbacks for those scenarios.