agw-documentation

You generate audience-targeted documentation by running this skill against previous phase analysis files and implementation logs, which produces standardized executive, business, and technical summaries for stakeholders.

Ensuring documentation consistency requires enforcing a standardized workflow output that automatically generates structured seeds for executive, business, and technical stakeholders directly from implementation logs.

Yes, you need previous phase analysis files and implementation logs. The skill requires access to these inputs to ensure traceability and consistency across the generated technical and business summaries.

Yes, you can use this for technical writing cleanup. It verifies all implementation checklist items and explicitly documents any deviations to maintain workflow integrity during the development finalization process.

You need to generate standardized documentation seeds during the finalization phase of a development workflow, specifically after a software architect approves a new feature implementation to close the development loop.