intent-report

Convert technical Intent files into Markdown and HTML stakeholder reports.

15|5|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/ArcBlock/idd --skill intent-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent-report
Source: https://github.com/ArcBlock/idd/tree/main/skills/intent-report
Command: npx skills add https://github.com/ArcBlock/idd --skill intent-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts technical Intent files into human-readable reports for stakeholders, onboarding, and documentation teams.

Core Features & Use Cases

  • Overview, Architecture, Progress, and Full reports across project modules and teams.
  • Output formats include Markdown and HTML for easy sharing and publishing.
  • Module-level and project-wide reporting with frontmatter-driven setup for consistency.

Quick Start

Run the intent-report tool against your Intent files to generate a formatted stakeholder report.

Frequently Asked Questions about intent-report

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

FAQPage Schema
How do I generate stakeholder reports from technical Intent files?

Generate stakeholder reports from technical Intent files by using a frontmatter-driven workflow to convert project modules into human-readable documentation. This produces formatted overviews, architecture details, and progress summaries for onboarding and reviews.

What is the best way to convert Intent specs into markdown documentation?

The best way to convert Intent specs into markdown documentation is through an automated conversion process that transforms technical configuration files into stakeholder-ready formats. This supports consistent project-wide reporting across multiple modules and teams.

Can I output project architecture reports in HTML for team reviews?

Yes, you can output project architecture reports in both Markdown and HTML formats. This allows for easy sharing and publishing of stakeholder documentation across project modules during team reviews and onboarding sessions.

Does intent-report support module-level documentation or only full project overviews?

Intent-report supports both module-level documentation and full project overviews. You can generate targeted architecture, progress, or comprehensive reports based on your specific stakeholder audience and review requirements.

When do I need to use frontmatter-driven workflows for stakeholder reporting?

Use frontmatter-driven workflows for stakeholder reporting when you need consistent documentation across multiple project modules and teams. This setup ensures technical Intent files are uniformly converted into human-readable reports for onboarding and reviews.

Why convert technical Intent files into human-readable reports for stakeholders?

Convert technical Intent files into human-readable reports to bridge the gap between technical architecture and stakeholder understanding. This process transforms complex module configurations into accessible documentation for project reviews and team onboarding.