doc-coauthoring

Guide structured document creation through context gathering, iterative refinement, and reader testing.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/jgsqware/pensine --skill doc-coauthoring-jgsqware
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-coauthoring
Source: https://github.com/jgsqware/pensine/tree/main/.tessl/tiles/anthropics/skills/skills/doc-coauthoring
Command: npx skills add https://github.com/jgsqware/pensine --skill doc-coauthoring-jgsqware

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating structured documentation by guiding users through a structured workflow, ensuring efficient context transfer, iterative refinement, and reader verification.

Core Features & Use Cases

  • Structured Workflow: Offers a three-stage workflow for document creation: Context Gathering, Refinement & Structure, and Reader Testing.
  • Trigger Conditions: Activated by user mentions of writing documentation, creating proposals, drafting specs, or similar tasks.
  • Use Case: For a team working on a technical spec, this Skill helps streamline the process by ensuring all necessary context is gathered, sections are iteratively refined, and the final document is tested for clarity and effectiveness.

Quick Start

Start the doc-coauthoring workflow by initiating a conversation about your documentation needs.

Frequently Asked Questions about doc-coauthoring

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

FAQPage Schema
How do I streamline collaborative writing for technical specs and proposals?

Streamline collaborative writing by using a structured workflow that guides your team through context gathering, iterative refinement, and reader testing to ensure technical specs and proposals are clear and effective.

What is the best way to structure document creation for a team?

The best way to structure document creation is a three-stage workflow: Context Gathering, Refinement & Structure, and Reader Testing. This ensures efficient context transfer and document clarity for team proposals.

How does reader testing work during document refinement?

Reader testing during document refinement works by actively verifying the final document for clarity and effectiveness through iterative feedback loops, ensuring the structured workflow outputs a readable proposal.

Can I use this structured workflow for drafting decision docs?

Yes, you can use this structured workflow for drafting decision docs. It is specifically designed for collaborative documentation tasks, adapting the context gathering and refinement stages to fit decision documents.

Does collaborative documentation require active user participation?

Yes, collaborative documentation requires active user participation. The structured workflow relies on iterative feedback loops during context gathering and refinement to properly transfer context and refine sections.

When do I need a structured workflow for document creation?

You need a structured workflow for document creation when your team faces challenges transferring context efficiently, requiring iterative refinement and reader verification to produce structured technical specs or proposals.