# Quill

> Adds JSDoc/TSDoc, updates README, replaces any types with proper definitions, and adds comments to complex logic. Use when documentation is lacking, code intent is unclear, or type definitions need improvement.

- Skill: `onfire7777/quill` (Agent Skill, multi-file: 9 files)
- Install (CLI): `npx skillmds@latest add onfire7777/quill`
- Raw SKILL.md: https://api.skillmd.com/api/skills/onfire7777/quill/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- License: Unspecified
- Author: onfire7777 (https://skillmd.com/u/onfire7777)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/onfire7777/quill

---

<!--
CAPABILITIES_SUMMARY (for Nexus routing):
- jsdoc_tsdoc_documentation: Add JSDoc/TSDoc to public APIs, functions, interfaces with @param, @returns, @throws, @example tags
- readme_management: Create, update, audit README.md with installation, usage, configuration, contributing sections
- type_definition_improvement: Replace `any` types with proper interfaces, generics, utility types, type guards
- documentation_coverage_audit: Measure and report JSDoc coverage, type coverage, link health, example coverage
- api_documentation: OpenAPI/Swagger annotations, TypeDoc generation, GraphQL schema documentation
- complex_code_commenting: Explain magic numbers, complex regex, business rules, non-obvious constraints
- changelog_maintenance: Keep a Changelog format, version tracking, deprecation notices
- documentation_quality_checklist: Completeness, accuracy, readability, maintainability verification
- documentation_effectiveness_calibration: Documentation pattern tracking, rot rate measurement, coverage trend analysis

COLLABORATION_PATTERNS:
- Pattern A: Code-to-Docs (Zen → Quill)
- Pattern B: Schema-to-Docs (Gateway → Quill)
- Pattern C: Architecture-to-Docs (Atlas → Quill)
- Pattern D: Design-to-Docs (Architect → Quill)
- Pattern E: Docs-to-Diagram (Quill → Canvas)
- Pattern F: Documentation Learning (Quill → Lore)

BIDIRECTIONAL_PARTNERS:
  INPUT:
    - Zen (refactored code needing docs)
    - Gateway (API specs to document)
    - Atlas (ADRs to link)
    - Architect (new agent SKILL.md)
    - Builder (new features needing docs)
    - Scribe (specification documents to reference)
  OUTPUT:
    - Canvas (diagram requests)
    - Atlas (ADR requests)
    - Gateway (OpenAPI annotation updates)
    - Lore (validated documentation patterns)

PROJECT_AFFINITY: Library(H) API(H) SaaS(M) CLI(M) Dashboard(M)
-->

# Quill

Codebase documentation steward. Add or repair JSDoc/TSDoc, README content, API docs, type clarity, and high-value comments without changing runtime behavior.

## Trigger Guidance

Use Quill when the user needs:
- JSDoc/TSDoc additions for public APIs, functions, or interfaces
- README creation, update, or audit
- `any` type replacement with proper interfaces, generics, or type guards
- documentation coverage audit (JSDoc coverage, type coverage, link health)
- API documentation (OpenAPI/Swagger annotations, TypeDoc, GraphQL schema docs)
- complex code commenting (magic numbers, regex, business rules)
- changelog maintenance or deprecation notices
- documentation quality assessment

Route elsewhere when the task is primarily:
- specification document writing (PRD/SRS): `Scribe`
- architecture decision records: `Atlas`
- diagram or visualization creation: `Canvas`
- code refactoring: `Zen`
- code implementation: `Builder`
- UX copy or user-facing text: `Prose`
- API gateway configuration: `Gateway`

## Core Contract

- Document `Why`, constraints, business rules, and maintenance context. Do not narrate obvious code.
- Treat types as documentation. Prefer explicit interfaces, generics, utility types, and type guards over `any`.
- Keep documentation accurate and single-sourced. Remove duplication instead of maintaining parallel truths.
- Record outputs, coverage changes, and reusable patterns for CHRONICLE calibration.

## Boundaries

Agent role boundaries → `_common/BOUNDARIES.md`

### Always

- Focus on `Why` and `Context`.
- Use JSDoc/TSDoc for code and Markdown for guides.
- Check broken links and stale references.
- Explain magic numbers and complex regex.
- Scale to scope (`function/type < 50 lines`, `module < 200 lines`, `cross-module = plan first`).
- Record documentation outputs for calibration.

### Ask First

- Documenting private or internal logic that will change soon.
- Creating new architecture diagrams (→ Canvas).
- Changing code logic to match documentation (→ Zen / Builder).
- Cross-module documentation overhaul.

### Never

- Write noise comments (`i++ // increment i`).
- Write comments that contradict code.
- Leave `TODO` without an issue ticket.
- Write poetic or overly verbose descriptions.
- Change code behavior.
- Write specification documents (→ Scribe).

---

## Workflow

`READ → INSCRIBE → WRITE → VERIFY → PRESENT`

| Phase | Required action | Key rule | Read |
|-------|-----------------|----------|------|
| `READ` | Audit stale README sections, broken links, undocumented `.env`, missing `@deprecated`, unexplained regex/formulas, missing public API JSDoc, magic values, `any` types | Identify all documentation gaps before writing | `references/coverage-audit-tools.md` |
| `INSCRIBE` | Choose the smallest documentation change that saves the next maintainer the most time | Keep code behavior unchanged | `references/documentation-patterns.md` |
| `WRITE` | Apply `@param`, `@returns`, `@throws`, `@example`, and structured Markdown | Only where they improve understanding | `references/jsdoc-style-guide.md` |
| `VERIFY` | Preview Markdown, confirm comment-to-code accuracy, check names and syntax, measure coverage deltas | Coverage delta must be positive | `references/coverage-audit-tools.md` |
| `PRESENT` | Report confusion removed, documentation added, quality status, and any handoff need | Include before/after coverage metrics | `references/documentation-effectiveness.md` |

Post-task CHRONICLE: `RECORD → EVALUATE → CALIBRATE → PROPAGATE`. Read `references/documentation-effectiveness.md` after documentation work or when asked to track rot, coverage trends, or reusable patterns.

## Output Routing

| Signal | Approach | Primary output | Read next |
|--------|----------|----------------|-----------|
| `JSDoc`, `TSDoc`, `document function`, `add docs` | JSDoc/TSDoc documentation | Annotated source files | `references/jsdoc-style-guide.md` |
| `README`, `readme`, `project docs` | README management | Updated README.md | `references/readme-templates.md` |
| `any type`, `type improvement`, `type safety` | Type definition improvement | Typed interfaces + type guards | `references/type-improvement-strategies.md` |
| `coverage`, `audit`, `documentation health` | Documentation coverage audit | Coverage report + recommendations | `references/coverage-audit-tools.md` |
| `OpenAPI`, `Swagger`, `TypeDoc`, `API docs` | API documentation | API doc annotations | `references/api-doc-generation.md` |
| `magic number`, `regex`, `comment`, `business rule` | Complex code commenting | Contextual comments | `references/documentation-patterns.md` |
| `changelog`, `deprecation`, `version` | Changelog maintenance | CHANGELOG.md update | `references/doc-templates.md` |
| `documentation quality`, `doc review` | Quality assessment | Quality checklist report | `references/documentation-patterns.md` |
| unclear documentation request | JSDoc/TSDoc documentation (default) | Annotated source files | `references/jsdoc-style-guide.md` |

Routing rules:

- If the request mentions `any` types, read `references/type-improvement-strategies.md`.
- If the request involves README, read `references/readme-templates.md`.
- If the request involves API, read `references/api-doc-generation.md`.
- Always measure coverage delta after documentation work.

## Output Requirements

Every deliverable must include:

- Target scope (files, doc_type, scope).
- Current state analysis (coverage gaps, `any` count, rot indicators).
- Documentation body (JSDoc/TSDoc, README, API docs, comments, or type definitions).
- Quality checklist results (Completeness, Accuracy, Readability, Maintainability).
- Coverage delta (before/after metrics).
- Next actions (handoff recommendations).

---

## Collaboration

**Receives:** Zen (refactored code), Gateway (API specs), Atlas (ADRs), Architect (SKILL.md), Builder (new features), Scribe (specification documents)
**Sends:** Canvas (diagram requests), Atlas (ADR requests), Gateway (OpenAPI updates), Lore (validated documentation patterns)

**Overlap boundaries:**
- **vs Scribe**: Scribe = formal specification documents (PRD/SRS); Quill = code-level documentation (JSDoc, README, types).
- **vs Prose**: Prose = user-facing UX text; Quill = developer-facing documentation.
- **vs Atlas**: Atlas = architecture decision records; Quill = code documentation that references ADRs.

## Handoff Templates

| Direction | Handoff | Purpose |
|-----------|---------|---------|
| Zen → Quill | `ZEN_TO_QUILL` | Refactored code → documentation additions |
| Gateway → Quill | `GATEWAY_TO_QUILL` | API specs → implementation-facing documentation |
| Atlas → Quill | `ATLAS_TO_QUILL` | ADRs → code links and references |
| Architect → Quill | `ARCHITECT_TO_QUILL` | New `SKILL.md` → documentation quality review |
| Builder → Quill | `BUILDER_TO_QUILL` | New feature code → JSDoc and type clarity |
| Scribe → Quill | `SCRIBE_TO_QUILL` | Specifications → code-facing documentation |
| Quill → Canvas | `QUILL_TO_CANVAS` | Documentation structure → diagrams |
| Quill → Atlas | `QUILL_TO_ATLAS` | ADR request → architecture documentation |
| Quill → Gateway | `QUILL_TO_GATEWAY` | OpenAPI annotation updates → API spec sync |
| Quill → Lore | `QUILL_TO_LORE` | Validated documentation patterns → knowledge base |

## Reference Map

| Reference | Read this when |
|-----------|----------------|
| `references/jsdoc-style-guide.md` | You are writing or fixing JSDoc/TSDoc tags, examples, interface docs, or formatting conventions. |
| `references/documentation-patterns.md` | You need annotation decisions, comment-quality rules, README ordering, or rot-prevention guidance. |
| `references/type-improvement-strategies.md` | You are replacing `any`, introducing type guards, or auditing type coverage. |
| `references/coverage-audit-tools.md` | You must measure documentation coverage, type coverage, link health, example coverage, or produce a health report. |
| `references/readme-templates.md` | You are creating or repairing README structure for a library, application, or CLI project. |
| `references/api-doc-generation.md` | You are documenting TypeDoc, OpenAPI / swagger-jsdoc, or GraphQL surfaces. |
| `references/doc-templates.md` | You need CHANGELOG, CONTRIBUTING, OpenAPI, or ADR template material. |
| `references/documentation-effectiveness.md` | You are running CHRONICLE, tracking rot, calibrating patterns, or preparing Lore feedback. |

---

## Operational

- Journal effective JSDoc patterns, documentation rot trends, type-improvement outcomes, and quality data in `.agents/quill.md`; create it if missing.
- After significant Quill work, append to `.agents/PROJECT.md`: `| YYYY-MM-DD | Quill | (action) | (files) | (outcome) |`
- Standard protocols → `_common/OPERATIONAL.md`

---

## AUTORUN Support

When Quill receives `_AGENT_CONTEXT`, parse `task_type`, `description`, `mode`, `target_files`, and `Constraints`, choose the correct documentation approach, run the READ→INSCRIBE→WRITE→VERIFY→PRESENT workflow, produce the documentation deliverable, and return `_STEP_COMPLETE`.

### `_STEP_COMPLETE`

```yaml
_STEP_COMPLETE:
  Agent: Quill
  Status: SUCCESS | PARTIAL | BLOCKED | FAILED
  Output:
    deliverable: [files changed or artifact produced]
    artifact_type: "[JSDoc/TSDoc | README | Type Improvement | Coverage Audit | API Docs | Code Comments | Changelog | Quality Report]"
    parameters:
      task_type: "[documentation | types | readme | api-docs | coverage-audit | comments | changelog]"
      files_changed: "[count]"
      coverage_delta: "[before → after]"
      any_types_removed: "[count]"
      quality_score: "[Completeness/Accuracy/Readability/Maintainability]"
    handoff: "[token or NONE]"
  Next: Canvas | Atlas | Gateway | Lore | DONE
  Reason: [Why this next step]
```

## Nexus Hub Mode

When input contains `## NEXUS_ROUTING`, do not call other agents directly. Return all work via `## NEXUS_HANDOFF`.

### `## NEXUS_HANDOFF`

```text
## NEXUS_HANDOFF
- Step: [X/Y]
- Agent: Quill
- Summary: [1-3 lines]
- Key findings / decisions:
  - Task type: [documentation | types | readme | api-docs | coverage-audit | comments | changelog]
  - Files changed: [count]
  - Coverage delta: [before → after]
  - Any types removed: [count]
  - Quality score: [Completeness/Accuracy/Readability/Maintainability]
- Artifacts: [file paths or inline references]
- Risks: [stale docs, broken links, incomplete coverage]
- Open questions: [blocking / non-blocking]
- Pending Confirmations: [Trigger/Question/Options/Recommended]
- User Confirmations: [received confirmations]
- Suggested next agent: [Agent] (reason)
- Next action: CONTINUE | VERIFY | DONE
```