writer

Generate cited long-form prose from briefs and reference sources.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Flintmere/flintmere --skill writer-flintmere
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writer
Source: https://github.com/Flintmere/flintmere/tree/main/.claude/skills/writer
Command: npx skills add https://github.com/Flintmere/flintmere --skill writer-flintmere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-form content creation is slow and error-prone; teams need consistent tone, verified sources, and a structured workflow to produce publish-ready prose.

Core Features & Use Cases

  • Produces finished prose with source citations and a built-in review flow.
  • Enforces a strict drafting process: outline, draft, fact-check, copy council, and legal council passes.
  • Supports multiple content formats (blog posts, docs pages, explainers, changelogs, newsletters) with source-truth governance.

Quick Start

Supply a brief and let the writer produce a finished, cited draft.

Frequently Asked Questions about writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft long-form content with verified citations automatically?

You can generate source-backed blog posts, docs pages, explainers, changelogs, and newsletters by providing a brief and references. The workflow applies outline, draft, fact-check, copy council, and legal council passes.

How do I write a blog post using my architecture decision records?

Writing a blog post using architecture decision records requires supplying a brief and pointing to the ADRs. The system verifies facts against these references to produce finished, cited prose.

Do I need to provide references to generate source-backed prose?

Yes, providing references is required to generate source-backed prose. Sources can include BUSINESS.md, ARCHITECTURE.md, ADRs, or external URLs, which the system verifies before emitting the final draft.

What's the best way to ensure my documentation passes a legal review?

To ensure documentation passes a legal review, use a built-in legal council self-check. The system automatically runs this check on drafts to verify compliance before emitting the final content.

Can I use this workflow for newsletters that require a defined voice?

Yes, this workflow supports newsletters that require a defined voice. The system applies source-truth governance and maintains consistent tone while generating cited prose from your brief.

What are the limitations of automated fact-checking for long-form content?

Automated fact-checking for long-form content is limited to the references you provide, such as BUSINESS.md or external URLs. The system cannot verify facts absent from supplied sources during its workflow.