swe-reports-guide
Dev Reports Guide for Executives
This skill defines the directory structure and writing standards for development and bug fix reports destined for company leadership and executives.
[!IMPORTANT] MANDATORY PREREQUISITE: Before writing or modifying ANY development report, status update, or executive summary, you MUST read and follow the instructions in the swe-management-talk agent skill. Do not rely on memory — always read the skill file to ensure correct tone, vocabulary, and formatting.
1. Directory Structure & File Locations
All reports for executives must be stored in the appropriate subdirectories under ./docs/dev-reports/ as Markdown (.md) files:
| Report Type | Directory Path | Example File Path |
|---|---|---|
| New Features | ./docs/dev-reports/features/ |
./docs/dev-reports/features/2026-07-06-occasion-mode.md |
| Bug Fixes | ./docs/dev-reports/fix-bugs/ |
./docs/dev-reports/fix-bugs/2026-06-26-fix-authentication.md |
Note: All filenames must be prefixed with the creation date in YYYY-MM-DD- format (e.g., 2026-07-06-redesign-attach-files.md). If the target directory does not exist, create it. If there is an existing legacy folder named fix-bug, align or migrate files to the standard ./docs/dev-reports/fix-bugs/ path as appropriate.