coquill

CoQuill

CoQuill is a document assembly tool for people already working with Claude and AI. If you're comfortable chatting with Claude, there's nothing new to learn — just ask it to prepare a document with CoQuill. Claude interviews you conversationally, collects the answers, and renders completed documents from your templates. No server, no database, no scripting language to learn. The whole project is a folder you can share as a zip — or deploy as a Claude Code plugin across your organisation in minutes.

How It Works

1. Place your templates in templates/, each in its own subdirectory
2. Add {{ variable_name }} placeholders wherever you need dynamic content
3. Use {% if %} / {% else %} blocks for sections that should only appear based on user answers
4. Use {% for item in items %} blocks for repeating sections (e.g., line items, milestones)
5. Optionally add a config.yaml to customize questions, grouping, and validation
6. Ask Claude to "prepare a [document type] with CoQuill"
7. Claude walks you through a conversational interview -- skipping irrelevant sections and collecting lists naturally
8. A completed document is rendered and saved to a job folder in output/

Two template formats are supported:

• .docx -- rendered via docxtpl, produces a Word document
• .html -- rendered via jinja2, produces both an HTML file and a PDF (via weasyprint)

Installation

Prerequisites

You'll need a Claude Cowork account.

Download CoQuill

Go to the Releases page and download the latest coquill-v*.zip file. Extract it to a folder of your choice (e.g., your Documents folder).

Open in Cowork

1. Open Claude Cowork and add the extracted folder as a project
2. That's it — no terminal or coding knowledge required. Python dependencies are installed automatically the first time you use the skill.

Claude Code

From within Claude Code:

1. Add the marketplace: /plugin marketplace add houfu/coquill
2. Install the plugin: /plugin install coquill@coquill
3. Say "prepare an NDA with CoQuill" to try it out with a built-in template

Quick Start

1. Add a template

Create a subdirectory in templates/ and place your template file inside:

templates/
└── nda/
    └── nda.docx      <- contains {{ disclosing_party_name }}, {{ effective_date }}, etc.

Or for an HTML template:

templates/
└── invoice/
    └── invoice.html  <- same {{ variable }} syntax, styled with CSS

2. Prepare a document

Tell Claude:

"I need to prepare an NDA with CoQuill"

Claude will find the template, extract its variables, and interview you for the values -- grouping related fields together for a natural flow.

3. Get your document

After confirming all values, the rendered document is saved to a job folder:

output/
└── nda_acme_pte_ltd_2026-02-15/
    └── nda_acme_pte_ltd_2026-02-15.docx

For HTML templates, both the HTML and PDF are saved:

output/
└── invoice_acme_2026-02-15/
    ├── invoice_acme_2026-02-15.html
    └── invoice_acme_2026-02-15.pdf

v2 Features

Conditional Logic

Templates can include or exclude sections based on user answers. The interview automatically skips questions that aren't relevant.

{% if decisions_made %}
## Decisions
{{ decisions }}
{% endif %}

Equality conditions are also supported:

{% if meeting_type == 'workshop' %}
### Workshop Materials
{{ workshop_materials }}
{% endif %}

Loops

Templates can have repeating sections. The interview collects items one at a time with an "add another?" flow.

{% for item in action_items %}
- **{{ item.description }}** — Assigned to: {{ item.assignee }}, Due: {{ item.due_date }}
{% endfor %}

Developer Configuration (config.yaml)

Template developers can place an optional config.yaml alongside their template to customize the interview experience:

meta:
  display_name: "Meeting Notes"
  description: "Structured meeting notes with action items and optional sections"

variables:
  meeting_title:
    label: "Meeting Title"
    question: "What is the title of this meeting?"
    required: true
  meeting_type:
    type: choice
    choices: [standup, workshop, review]
    default: "standup"
  decisions_made:
    type: boolean
    question: "Were any decisions made during this meeting?"
    default: false

groups:
  - name: "Meeting Details"
    variables: [meeting_title, meeting_date, meeting_type, facilitator_name]
  - name: "Workshop Materials"
    condition: "meeting_type == 'workshop'"
    variables: [workshop_materials]
  - name: "Action Items"
    loop: action_items
    variables: [description, assignee, due_date]

validation:
  - rule: "next_meeting_date > meeting_date"
    message: "The next meeting date must be after this meeting's date"