generate-working-docs

Automate development documentation generation by providing a kebab-case requirement name to create a dated directory structure. It sequentially generates requirements.md, design.md, tasklist.md, and testing.md files under docs/working, adapting the content specifically for new feature workflows.

Structuring working docs for performance improvements requires a standardized directory and file set. This automation creates a dated folder with requirements.md, design.md, tasklist.md, and testing.md, tailoring the generated content to performance improvement workflows instead of new features.

No dependencies are required to auto-generate dev docs with this workflow. The skill operates independently to orchestrate the sequential execution of its internal sub-skills, creating compliant documentation without external packages or frameworks.

Sequential documentation generation works by orchestrating sub-skills in a specific order: generate-requirements, generate-design, generate-tasklist, and generate-testing. This ensures consistent, compliant software engineering documentation without manual boilerplate.

Yes, you can use this documentation automation for both new feature work and performance improvements. It adapts the generated content within the four core files to suit either workflow, ensuring standardized structure across different project types.