exec-summary

Generate an executive summary by running the skill on a feature folder containing requirements.md, background.md, validation.md, and mockup-ascii.md. It outputs a 600-800 word executive-summary.md file that aligns sales, leadership, and engineering stakeholders.

The best way to create a concise feature brief is to consolidate structured feature context from existing markdown files into a single present tense narrative. This skill reads your feature folder documents and outputs a structured markdown brief for engineering and sales.

Automated feature documentation processing shapes the narrative by reading requirements, background, validation, and mockup files to construct a single structured markdown summary tailored for sales, leadership, and engineering audiences.

Yes, you need structured feature context files including requirements.md, background.md, validation.md, and supporting mockup-ascii.md in your feature folder to shape the executive summary narrative accurately.

Yes, you can use this executive summary generator without any external dependencies. It operates independently by reading local feature folder markdown files and outputting the generated summary.

The generated executive summary is a markdown file named executive-summary.md containing 600-800 words in present tense. It includes YAML frontmatter with title, feature, status, and updated date metadata.