documenter-coauthoring
Documenter Coauthoring
Structured coauthoring workflow for large docs. Pair this with documenter
when the task needs sustained collaboration instead of a direct draft/update.
Core Workflow
- Gather context efficiently:
- ask for audience, desired outcome, constraints, deadline, and template
- invite a raw context dump; do not force the user to pre-organize it
- read linked local files and existing docs before asking avoidable questions
- Propose a structure before drafting the full doc when scope is still fuzzy or the document is large.
- Draft the sections with the most uncertainty first. Summary sections usually come last.
- Refine with surgical edits instead of reprinting the whole document on every iteration.
- Before finishing, do a reader test:
- check whether a reader without hidden context can follow the decision,
More from n-n-code/n-n-code-skills
project-vendor-boundary
Overlay for app-owned versus vendored dependency boundaries. Portable across repos that vendor third-party code. Use when work touches vendored dependencies or their integration seam.
19coding-guidance-cpp
C++ implementation and review skill. Use when writing, modifying, refactoring, or reviewing C++ code, especially modern C++17/20/23 code that needs strong ownership, type safety, and testable design. Portable across C++ repos and build systems.
18project-platform-diagnose
Overlay for environment-sensitive diagnosis — service startup, install issues, platform integration, headless/container behavior, and runtime smoke checks. Portable across repos where build, install, or runtime behavior depends on the local platform.
18documenter
Baseline overlay for substantial documentation authoring or restructuring: README, specs, ADRs, tutorials, how-to guides, reference docs, explanations, API docs, code comments, changelogs, and agent-facing docs. Use when the agent should classify doc type, ground claims in repo truth, and validate examples before finishing.
18security
Security workflow skill for repo-grounded threat modeling, exploit-focused security review, and secure-by-default implementation guidance. Use when the user explicitly asks for security work, or when security properties are the primary concern in a high-risk change. Do not trigger for ordinary code review, routine endpoint work, or general backend implementation just because a repo contains APIs, auth, or secrets.
18project-release-maintainer
Overlay for release-facing docs, install layout, workflows, licenses, and hygiene scripts. Portable across repos with a release/packaging pipeline. Use for publication-facing changes.
17