code-report

To generate implementation reports for plan changes automatically, use a tool that reads active planning directories and outputs structured markdown documenting files changed, new features, and testing guidance. This ensures QA-ready traceability after feature execution.

The best way to document code changes for QA handoff is to produce a standardized report file capturing the overview, modified files, and end-to-end testing guidance. This preserves context and provenance from the original planning artifacts.

Yes, you need an active planning directory containing parallel-plan.md and shared.md files. This structure allows the report generation process to extract context and produce a comprehensive report.md file with frontmatter and testing guidance.

Yes, you can align implementation reports with existing planning artifacts by leveraging the shared.md and parallel-plan.md files within your feature directory. This preserves provenance and ensures the generated report.md reflects the original execution context.

Structured documentation for feature implementation should include frontmatter, an overview, files changed, new features, additional notes, and end-to-end testing guidance. This standardized format ensures comprehensive traceability for stakeholders.