debrief

To generate technical debriefs covering code architecture and test coverage, this Skill outputs both full HTML and concise Markdown documents using template-based scripting for consistent formatting and inline styles.

A technical debrief is a comprehensive report detailing architecture, test coverage, product tours, and key design decisions. You need one to document and communicate complex project details to technical teams.

To create a product tour with step-by-step user stories, use debrief scripting that encourages storytelling to present the user experience in a conversational format alongside technical architecture walkthroughs.

Yes, you need a template file to generate project reports in HTML and Markdown, because the debrief generation process requires a template and the inlining of shared styles to ensure consistent formatting.

Yes, you can output both full HTML and concise Markdown summaries from a single code review, as the debrief generation process produces structured documents in both formats simultaneously.

The limitations of template-based scripting for technical project reporting include the strict requirement for a template file and the mandatory inlining of shared styles, which restricts formatting flexibility.