drf-writer

Organize and validate .txt drafts in the 1 - draft/ folder.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fabioabr/rag-blueprint --skill drf-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drf-writer
Source: https://github.com/fabioabr/rag-blueprint/tree/main/src/.claude/skills/drf-writer
Command: npx skills add https://github.com/fabioabr/rag-blueprint --skill drf-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill auxilia equipes a gerenciar e estruturar rascunhos em formato .txt, mantendo a pasta de drafts organizada e consistente.

Core Features & Use Cases

  • Organização de drafts: classifica, nomeia, e mantém consistência do conteúdo de .txt dentro da pasta 1 - draft/.
  • Validação de formato: garante que cada draft siga o padrão de cabeçalho e metadados.
  • Integração com pipeline: facilita a comunicação com as etapas posteriores (docs, presentation) sem gerar .md ou .html.

Quick Start

Organize e revise os drafts .txt na pasta 1 - draft, aplicando o formato padrão e mantendo a consistência do repositório.

Frequently Asked Questions about drf-writer

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

FAQPage Schema
How do I organize .txt drafts for a documentation pipeline?

Organizing .txt drafts for a documentation pipeline involves classifying and naming files within a dedicated draft folder while enforcing front matter validity. This ensures drafts remain consistently formatted and separated from downstream docs and presentation stages.

What is the best way to validate front matter in .txt drafts?

Validating front matter in .txt drafts requires applying standardized formatting rules to ensure each file follows the correct metadata header pattern. This maintains content consistency and prepares drafts for smooth progression through the documentation pipeline.

Why should drafts remain .txt-only instead of converting to .md or .html immediately?

Drafts remain .txt-only to enforce separation of concerns within the documentation pipeline. Downstream writers handle the conversion to .md or .html later, ensuring the initial draft stage focuses strictly on content curation and metadata validity.

Does this draft curation workflow support integration with downstream docs and presentation folders?

Yes, this draft curation workflow supports integration with downstream docs and presentation folders. It structures .txt drafts in the initial pipeline stage, facilitating seamless communication and file transfer to subsequent documentation and presentation phases.

How do I standardize formatting across multiple .txt draft files?

Standardizing formatting across .txt draft files involves applying consistent header rules and metadata validation across the entire draft folder. This process enforces content curation standards and ensures every draft adheres to the required pipeline structure.

When do I need a dedicated draft folder structure for content curation?

A dedicated draft folder structure is needed when managing a multi-stage documentation pipeline. It isolates initial .txt drafts, enforces front matter validity, and maintains a clear separation of concerns before files move to downstream docs or presentation stages.