dev-docs-writer

To automate development documentation, you provide a DISCOVERY.md file and trigger the skill to generate standardized PRD, TECH-SPEC, PROGRESS, and CONTEXT markdown documents under your docs/ directory.

Creating a PRD and tech spec for early-stage projects is best handled by converting a DISCOVERY.md file into structured, frontmatter-driven markdown artifacts using an automated documentation workflow.

Yes, you need a DISCOVERY.md file as input because the documentation generation process parses its content to produce the required PRD, TECH-SPEC, and other structured markdown outputs.

To split high-complexity project documentation, you can trigger the generation via /init and integrate with a doc-splitter to break down the generated outputs into manageable structured documents.

Yes, generated documentation supports context-optimizer workflows because the outputs are structured, frontmatter-standardized markdown documents specifically optimized for loading by context-optimizer processes.