final-report

Generate a Korean final-change report from a plan and development logs.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dmlguq456/claude_setting --skill final-report
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: final-report
Source: https://github.com/dmlguq456/claude_setting/tree/main/skills/final-report
Command: npx skills add https://github.com/dmlguq456/claude_setting --skill final-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of a comprehensive final-change report from a plan and associated development logs, consolidating context for future reference.

Core Features & Use Cases

  • Plan integration: resolves plan variants and aggregates plan reviews (init-plan, refine-plan, execute-plan) into a single narrative.
  • Log synthesis: extracts changes from dev_logs, QA reviews, and checklist outcomes to build a traceable change story.
  • Korean plan alignment: presents the final report in Korean per plan frontmatter guidance and user-facing instructions.

Quick Start

Provide a plan file path or plan name and the logs directory to generate a comprehensive final_report.md.

Frequently Asked Questions about final-report

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

FAQPage Schema
How do I generate a final change report from development logs and a plan file?▼

To generate a final change report, provide a plan file path or name and a logs directory. The Skill synthesizes plan resolutions, dev logs, and QA findings to output a structured final_report.md in the log directory.

What is the best way to consolidate plan variants and QA findings into a single narrative?▼

Consolidating plan variants and QA findings into a single narrative is done by aggregating init-plan, refine-plan, and execute-plan reviews alongside development logs to produce a structured, traceable change report.

Can I use this automation to extract changes from dev logs for a final report?▼

Yes, you can use this automation to extract changes from dev logs. It operates across log reviews, QA findings, and checklist outcomes to build a traceable change story aligned to the plan's context.

Does the generated final report support Korean language alignment?▼

Yes, the generated final report supports Korean language alignment. It presents the final report in Korean per the plan frontmatter guidance and user-facing instructions.

What inputs are required to automate final report generation from plans and logs?▼

Automating final report generation from plans and logs requires a plan file path or name and a log directory. Autonomy level and QA level are carried from the plan frontmatter to guide the output.

When do I need to generate a comprehensive final-change report for development context?▼

You need to generate a comprehensive final-change report when consolidating context for future reference. It automates the extraction of plan resolutions, dev logs, and cross-variant changes into a structured narrative.