agent-writer

To generate structured technical docs, provide a concise brief and audience definition to receive a complete, ready-to-use document draft with clear structure and consistent formatting.

Yes, you can write architecture decision records by submitting a brief input, which the system converts into a formal ADR with a consistent voice, narrative, and formatting.

To create a product spec or incident summary, you need to provide a clear brief and the target audience, and the system will output a polished, ready-to-use document draft.

Frontmatter-driven metadata enforces consistency by applying a metadata contract in SKILL.md alongside a system prompt that guides tone, style, and formatting across all generated documents.

The best way to write READMEs for engineering teams is to use a brief-driven generation process that enforces structured content and a consistent formatting voice for ready-to-use outputs.

Yes, this approach works for product specs and tech docs simultaneously by applying a unified system prompt that maintains formatting and voice across multiple supported document types.